swift-storage charm creates incorrect fstab entry as /dev/loop0 when block-device is /path/to/file.img

Bug #1510666 reported by JuanJo Ciarlante
8
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

JuanJo Ciarlante (jjo)
description: updated
Felipe Reyes (freyes)
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
Felipe Reyes (freyes)
tags: added: openstack
Changed in swift-storage (Juju Charms Collection):
status: New → In Progress
Revision history for this message
Jorge Niedbalski (niedbalski) wrote :

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.

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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.