cloud-init

cloud-init doesn't support NFS in mounts

Bug #1870370 reported by Andrew Beresford
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Undecided
Andrew Beresford

Bug Description

When trying to mount filesystems that use NFS or EFS (AWS Elastic File System - Amazon's implementation of NFSv4.1), cloud-init will not allow valid NFS mountpoints to added to the fstab.

In the event that you try, you'll see

mounts configuration is [['fs-10e8d4db:/', '/opt/jenkins_workspace', 'efs', 'defaults,_netdev', 0, 0]]

followed by

"Attempting to determine the real name of fs-10e8d4ab:/" followed by "Ignorming nonexistant named mount fs-10e8d4ab:/"

The problem is that sanitize_devname doesn't understand network mount points.

I have a PR in progress to fix the problem.

Revision history for this message
Andrew Beresford (beezly) wrote :

PR is at https://github.com/canonical/cloud-init/pull/300

Dan Watkins (oddbloke)
Changed in cloud-init:
status: New → In Progress
assignee: nobody → Andrew Beresford (beezly)
Revision history for this message
Chad Smith (chad.smith) wrote :

Merged into cloud-init upstream at https://github.com/canonical/cloud-init/commit/723e2bc1ad14687a8d6846b9ca73620e4e4090b1

Changed in cloud-init:
status: In Progress → Fix Committed
Revision history for this message
Chad Smith (chad.smith) wrote : Fixed in cloud-init version 20.2.

This bug is believed to be fixed in cloud-init in version 20.2. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
Revision history for this message
Ryan Harper (raharper) wrote :

@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

Revision history for this message
Andrew Beresford (beezly) wrote :

Hi Ryan,

From memory this was on Debian 8. However, I no longer have any access to those systems as I'm no longer working for that client.

Sadly, I don't have anything more than that.

Andrew

Revision history for this message
C de-Avillez (hggdh2) wrote :

Moving bug to Private, in preparation for log upload.

information type: Public → Private
Revision history for this message
C de-Avillez (hggdh2) wrote :

dammit. Wrong bug. I apologise. Moving back to Public.

information type: Private → Public
Revision history for this message
James Falcon (falcojr) wrote :

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3642

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.