juju storage should use UUIDs in fstab, and possibly set mount option "nofail"

Bug #1877380 reported by Junien Fridrick on 2020-05-07
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ian Booth

Bug Description


Juju 2.6.10 (I think). It would appear that juju storage creates entries in fstab that 1. use device names (/dev/vdb1 for example) and 2. don't set the "nofail" mount option.

This means that if for whatever reason the device name changes (and it happens frequently in cloud environments), the machine will not find the device, and because the "nofail" mount option is not specified, it will actually not boot at all.

(nofail is defined at https://www.freedesktop.org/software/systemd/man/systemd.mount.html#fstab)

Please consider using device labels or UUIDs in fstab, and please consider setting the "nofail" option as well. I think operators will much prefer having a machine with a missing mount that they can SSH to, vs having a blocked boot.

Thanks !

Pete Vander Giessen (petevg) wrote :

I agree that uuids would be a better and safer way of mounting storage. Marking as triaged and assigning importance as "high".

Changed in juju:
importance: Undecided → High
status: New → Triaged
Pete Vander Giessen (petevg) wrote :

Per discussion on IRC: the change here is probably just a few lines of code (plus the associated testing, of course!)

Ian Booth (wallyworld) on 2020-05-14
Changed in juju:
milestone: none → 2.8.1
Ian Booth (wallyworld) on 2020-07-03
Changed in juju:
milestone: 2.8.1 → 2.8.2
Ian Booth (wallyworld) on 2020-07-15
Changed in juju:
assignee: nobody → Ian Booth (wallyworld)
status: Triaged → In Progress
Ian Booth (wallyworld) on 2020-07-17
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers