Comment 4 for bug 1870370

@Andrew

During verification[1] for this bug I observed on the official Ubuntu cloud images that the error message you mention:

Ignorming nonexistant named mount fs-10e8d4ab:/

is present, it does not prevent cloud-init from injecting the mount entry into /etc/fstab.

Finally, the Ubuntu Cloud images do not contain an nfs client by default, so in this scenario, you will see the 'mount -a' command fail, and mention that you might need a mount.<filesystem> client.

For Ubuntu, adding the 'nfs-common' package is sufficient to enable NFS mounts.

Do you have any more details around the original failure (/var/log/cloud-init.log, /etc/fstab) and can you confirm if you're using Ubuntu images or something else?

1. https://github.com/cloud-init/ubuntu-sru/pull/135