> Nevertheless, there's a trivial work-around in our case: just add an override > for > "RequiresMountFor=/boot/firmware" to our systemd config for cloud-init-local
Yes, this is the correct configuration that's needed, and it's related to your configuration change and where you're putting your seed. > should we not also configure cloud-init in such a way that we guarantee the device containing its seed is definitely mounted prior to it running? This is how cloud-init is configured by default which has: RequiresMountsFor=/var/lib/cloud Which is the default location for the NoCloud on-disk seed. So I don't think this is a bug, however, let's take this bug as an opportunity to add to our documentation around using NoCloud's 'seedfrom' configuration https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860046 Title: Race to mount seed device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1860046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
