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
--
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/1870370
Title:
cloud-init doesn't support NFS in mounts
Status in cloud-init:
Fix Released
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1870370/+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
