(I can’t seem to sign into the bugtracker to raise this there, although the UI suggests you should be able to use this account)
Using Rocky-8-GenericCloud-Base-8.7-20221130.0.x86_64.qcow2
, if I boot an instance on OpenStack with attached volumes /etc/fstab looks like this:
UUID=08d8ba03-a737-4caa-80fe-bdcf160bb8e9 / xfs defaults 0 0
UUID=3a94b570-1121-4bbd-8c1e-beb2b73d0c03 /boot xfs defaults 0 0
UUID=0607-95FB /boot/efi vfat defaults,uid=0,gid=0,umask=077,shortname=winnt 0 2
LABEL=state /var/lib/state auto defaults,nofail,x-systemd.requires=cloud-init.service,_netdev,comment=cloudconfig 0 2
LABEL=home /exports/home auto x-systemd.required-by=nfs-server.service,x-systemd.before=nfs-server.service,comment=cloudconfig 0 2
If I then reboot the instance it goes into emergency mode. The console log shows a load of problems like
A start job is running for���abel-state.device (38s / 1min 30s)[K[ [0;31m*[0;1;31m*[0m[0;31m*[0m] (2 of 2) A start job is running for���abel-state.device (38s / 1min 30s)[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (1 of 2) A start job is running for���label-home.device (39s / 1min 30s)
then eventually shows
[[0;1;33mDEPEND[0m] Dependency failed for /exports/home.
[[0;1;33mDEPEND[0m] Dependency failed for Local File Systems.
[[0;1;33mDEPEND[0m] Dependency failed for Mark the need to relabel after reboot.
[[0;1;33mDEPEND[0m] Dependency failed for File System Check on /dev/disk/by-label/home
Note an instance using Rocky-8-GenericCloud-8.6.20220702.0.x86_64.qcow2
with the same (well, different but identical) volumes attached survives reboot.