As a hint on reproducing it, it may be a problem on xenial only (which we used for that deployment) for clean devices.
On a bionic VM it seems like the symlink is created but it's not clear if luksFormat returns before that symlink gets created or after - this is the important part because the automation tries to use that symlink right after `cryptsetup luksFormat <dev>` exits. tree /sys/class/block https://paste.ubuntu.com/p/vhjjzdytH7/ uname -a Linux maas-vhost6 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@maas-vhost6:~$ tree /dev/disk/by-uuid/ /dev/disk/by-uuid/ └── d26a75c9-15f7-41de-8c0e-20f795ed5729 -> ../../sda1 0 directories, 1 file ubuntu@maas-vhost6:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 64G 0 disk └─sda1 8:1 0 64G 0 part / sdb 8:16 0 8G 0 disk sdc 8:32 0 102.4M 0 disk sdd 8:48 0 102.4M 0 disk sde 8:64 0 102.4M 0 disk vda 252:0 0 102.4M 0 disk vdb 252:16 0 102.4M 0 disk nvme0n1 259:0 0 20G 0 disk nvme1n1 259:1 0 20G 0 disk ubuntu@maas-vhost6:~$ sudo cryptsetup luksFormat /dev/sdb WARNING! ======== This will overwrite data on /dev/sdb irrevocably. Are you sure? (Type uppercase yes): YES Enter passphrase for /dev/sdb: Verify passphrase: ubuntu@maas-vhost6:~$ tree /dev/disk/by-uuid/ /dev/disk/by-uuid/ ├── a82ddfe0-7de8-4c6c-aaca-a074f000b746 -> ../../sdb └── d26a75c9-15f7-41de-8c0e-20f795ed5729 -> ../../sda1 0 directories, 2 files sudo cryptsetup luksFormat /dev/sdb WARNING! ======== This will overwrite data on /dev/sdb irrevocably. Are you sure? (Type uppercase yes): YES Enter passphrase for /dev/sdb: Verify passphrase: ubuntu@maas-vhost6:~$ sudo cryptsetup luksDump /dev/sdb | grep UUID UUID: 21bacaf0-9eea-4809-9b1c-6f4d7e614f5b ubuntu@maas-vhost6:~$ tree /dev/disk/by-uuid/ /dev/disk/by-uuid/ ├── 21bacaf0-9eea-4809-9b1c-6f4d7e614f5b -> ../../sdb └── d26a75c9-15f7-41de-8c0e-20f795ed5729 -> ../../sda1 0 directories, 2 files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780332 Title: vaultlocker does not ensure that udev is triggered to create /dev/disk /by-uuid/<uuid-in-luks-header> symlink and fails To manage notifications about this bug go to: https://bugs.launchpad.net/vaultlocker/+bug/1780332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
