initrd script needs to handle reading of a UUID file for encrypted volumes.

[Oliver Grawert]

when a disk is encrypted it will only have a UUID but not a label. the snappy initrd relies on mounting the writable partition by label...

after decrypting the volume in case there was no label created before encrypting, the boot will not work.

to find the partition the UUID needs to be written somewhere at encryption time (i.e. into a file in the system-boot partition) where the initrd can consume it to find the to-be-decrypted partition.

[Oliver Grawert (ogra)]

adding ricmm to the subscribers here

[Steve Langasek (vorlon)]

There is no bug here. The disk in question doesn't have a label because it wasn't set up with a label.

To set a label on an ext3/4 filesystem, use the -L option to mkfs.ext[34]. You can add a label to an existing filesystem with tune2fs -L.

[John Lenton (chipaca)]

AIUI the problem is that the filesystem isn't available until the volume is decrypted, and snappy will fail to boot such a system. As the expectation is for snappy systems to boot, this is indeed a bug.

[Oliver Grawert (ogra)]

re-worked the title and description for the UUID bit.