swift-storage charm creates incorrect fstab entry as /dev/loop0 when block-device is /path/to/file.img
Bug #1510666 reported by
JuanJo Ciarlante
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
swift-storage (Juju Charms Collection) |
Fix Released
|
High
|
Jorge Niedbalski |
Bug Description
using eg. block-device: /srv/swift.img|20G, swift-storage unit
gets the following /etc/fstab entry:
/dev/loop0 /srv/node/loop0 xfs defaults 0 0
, but it should instead have:
/srv/swift.img /srv/node/loop0 xfs loop,defaults 0 0
Note that this entry effectively voids the unit from
completing boot to runlevel 2, from this failing mount.
Related branches
lp:~niedbalski/charm-helpers/fix-lp1510666
- charmers: Pending requested
-
Diff: 32 lines (+17/-0)2 files modifiedcharmhelpers/contrib/storage/linux/loopback.py (+10/-0)
tests/contrib/storage/test_linux_storage_loopback.py (+7/-0)
lp:~niedbalski/charms/trusty/swift-storage/fix-lp1510666
- Billy Olsen: Approve
- Felipe Reyes: Approve
-
Diff: 119 lines (+55/-3)3 files modifiedcharmhelpers/contrib/storage/linux/loopback.py (+10/-0)
lib/swift_storage_utils.py (+19/-2)
unit_tests/test_swift_storage_utils.py (+26/-1)
description: | updated |
Changed in swift-storage (Juju Charms Collection): | |
assignee: | nobody → Felipe Reyes (freyes) |
Changed in swift-storage (Juju Charms Collection): | |
assignee: | Felipe Reyes (freyes) → Jorge Niedbalski (niedbalski) |
importance: | Undecided → High |
tags: | added: openstack |
Changed in swift-storage (Juju Charms Collection): | |
status: | New → In Progress |
Changed in swift-storage (Juju Charms Collection): | |
status: | In Progress → Fix Committed |
milestone: | none → 16.01 |
Changed in swift-storage (Juju Charms Collection): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The linked MP fixes this issue.
With the patch, the resulting entry on the fstab, looks like:
/srv/swift.img /srv/node/loop0 xfs loop, defaults 0 0
Thanks.