cloud-init doesn't support NFS in mounts
Bug #1870370 reported by
Andrew Beresford
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_
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.
Changed in cloud-init: | |
status: | New → In Progress |
assignee: | nobody → Andrew Beresford (beezly) |
To post a comment you must log in.
PR is at https:/ /github. com/canonical/ cloud-init/ pull/300