btrfs resize fails if root is a subvolume and mounted as ro
Bug #1734787 reported by
Robert Schweikert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Undecided
|
Robert Schweikert |
Bug Description
If root, i.e. / in a btrfs filessystem is setup as a subvolume and this is set to read only resize fails. However, as other subvolumes will benefit from the resize operation resizing the filesystem should still be allowed and the operation should succeed.
Related branches
~chad.smith/cloud-init:ubuntu/devel
- Server Team CI bot: Approve (continuous-integration)
- Scott Moser: Pending requested
-
Diff: 1537 lines (+767/-173)23 files modified.gitignore (+1/-0)
cloudinit/config/cc_resizefs.py (+11/-1)
cloudinit/config/cc_rsyslog.py (+5/-5)
cloudinit/net/__init__.py (+2/-2)
cloudinit/net/dhcp.py (+42/-1)
cloudinit/net/network_state.py (+12/-0)
cloudinit/sources/DataSourceAzure.py (+129/-9)
cloudinit/sources/DataSourceEc2.py (+7/-16)
cloudinit/sources/DataSourceOpenNebula.py (+59/-53)
cloudinit/sources/__init__.py (+1/-1)
cloudinit/sources/helpers/azure.py (+14/-8)
cloudinit/temp_utils.py (+8/-3)
cloudinit/tests/test_util.py (+46/-0)
cloudinit/url_helper.py (+20/-9)
cloudinit/util.py (+17/-6)
debian/changelog (+13/-0)
doc/rtd/topics/network-config-format-v1.rst (+1/-1)
tests/unittests/test_datasource/test_azure.py (+151/-6)
tests/unittests/test_datasource/test_ec2.py (+1/-1)
tests/unittests/test_datasource/test_opennebula.py (+177/-46)
tests/unittests/test_handler/test_handler_resizefs.py (+21/-1)
tests/unittests/test_net.py (+15/-3)
tools/read-version (+14/-1)
~rjschwei/cloud-init:btrfsResize
- Scott Moser: Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 176 lines (+95/-8)4 files modifiedcloudinit/config/cc_resizefs.py (+11/-1)
cloudinit/tests/test_util.py (+46/-0)
cloudinit/util.py (+17/-6)
tests/unittests/test_handler/test_handler_resizefs.py (+21/-1)
Changed in cloud-init: | |
assignee: | nobody → Robert Schweikert (rjschwei) |
Changed in cloud-init: | |
status: | New → Fix Committed |
To post a comment you must log in.
This bug is believed to be fixed in cloud-init in 18.1. If this is still a problem for you, please make a comment and set the state back to New
Thank you.