@Sean you're right... the cloud-init fix was to handle the case there is *no* /etc/fstab ... so any other place that expects /etc/fstab to exist must also handle missing file.
Looking at overlayroot, it expects to be able to update/modify the baked-in fstab, but it's not there. https://git.launchpad.net/cloud-initramfs-tools/tree/overlayroot/scripts /init-bottom/overlayroot#n313 ** Also affects: cloud-initramfs-tools Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1890803 Title: Groovy amd64 / arm64 / PowerPC deployment seems not working Status in cloud-init: Invalid Status in cloud-initramfs-tools: New Status in MAAS: Triaged Status in ubuntu-kernel-tests: New Bug description: All bare-metal deployment tasks have failed on our bare-metal maas server and the PowerMAAS / HyperMAAS (image synced on maas server). Deployment failed with: Installation was aborted. Need to further investigate this. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1890803/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
