Please generate version 4 block device UUIDs, not version 1

Bug #1785356 reported by Tom Reynolds on 2018-08-04
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Medium
Unassigned
subiquity
Undecided
Unassigned

Bug Description

Using the 18.04.1 server-live installer with manual partitioning, the installed system ends up with an fstab like this:

UUID=d94e7ea3-9785-11e8-b625-080027681a6b / ext4 defaults 0 0
UUID=d94e7ea2-9785-11e8-b625-080027681a6b /boot ext4 defaults 0 0
/swap.img none swap sw 0 0

The block device UUIDs generated here are very similar, which may abet user errors. The classic Ubuntu server installer generates version 4 UUIDs which provide much more variance.

This may be visualized by using, for example, the bulk UUID generators version 1 and 4 at https://www.uuidonline.net/

https://tools.ietf.org/html/rfc4122#section-4.1.3
https://en.wikipedia.org/wiki/Universally_unique_identifier#Versions

Related branches

Tom Reynolds (tomreyn) on 2018-08-04
summary: - Please generate version 4 UUIDs, not version 1
+ Please generate version 4 block device UUIDs, not version 1
description: updated
Tom Reynolds (tomreyn) on 2018-08-04
description: updated
Michael Hudson-Doyle (mwhudson) wrote :

This will need to be addressed in curtin.

Ryan Harper (raharper) on 2018-08-06
Changed in curtin:
importance: Undecided → Medium
status: New → Confirmed
Ryan Harper (raharper) wrote :

We'll switch curtin to UUID4 values as fallback when a UUID value is not provided.

Subiquity can generate UUID4 values, and pass that into the storage config, and those values will be used instead of curtin (currently) generating uuid1 values.

http://curtin.readthedocs.io/en/latest/topics/storage.html#format-command

Ryan Harper (raharper) on 2018-08-06
Changed in curtin:
status: Confirmed → In Progress

This bug is fixed with commit 1845c22a to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=1845c22a

Changed in curtin:
status: In Progress → Fix Committed

This bug is believed to be fixed in curtin in version 18.2. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
Changed in subiquity:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers