-
Notifications
You must be signed in to change notification settings - Fork 23.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mount module fails on nfs mounts with "as it does not exist' #65855
Mount module fails on nfs mounts with "as it does not exist' #65855
Comments
Files identified in the description: If these files are inaccurate, please update the |
Files identified in the description: If these files are inaccurate, please update the |
resolved_by_pr #65544 |
@wirerydr, Could you please check PR #65544 and let us know if it works for you ? |
Tested PR #65544 within the (otherwise) same environment that originally manifested my problem, as documented by this bug report. The following scenarios were tested:
This would seem to address the issue raised by this bug-report, at-least for me. Thank you very much for the quick turnaround. |
@wirerydr This issue is waiting for your response. Please respond or the issue will be closed. |
@wirerydr You have not responded to information requests in this issue so we will assume it no longer affects you. If you are still interested in this, please create a new issue with the requested information. |
Please reopen, the bug is still there, and has a pull request, #65869 |
Reopening as per above. Not exactly sure why the bot closed this. bot_status |
Componentslib/ansible/modules/system/mount.py Metadatawaiting_on: wirerydr |
(Speaking as the originator of this bug report) Something weird is going on - Ansibot seems to be expecting feedback from me, but I pulled the PR, tested it, and provided feedback (to this issue on this comment thread) nearly 3 months ago - Please refer to #65855 (comment). Please let me know if anything further is required from me, and I will happily provide it. WireRydr |
…ansible#61752)" This reverts part of ansible commit 72023d7. The immediate reason is that it breaks mounts where src is not a path. Examples of such mounts are network-based filesystems such as nfs, cifs, glusterfs, ceph, virtual filesystems such as tmpfs or overlayfs, and also UUID-based mounts. It is too hard to come with an exhaustive list, especially if we take non-Linux systems into account, so don't even try. Additionally, it did not really fix the issue (ansible/ansible#59183) that it intended to fix, because the mount could fail but leave a non-working fstab entry for reasons other than non-existing src path. Fixes: ansible/ansible#65855 Fixes: ansible/ansible#67588 Fixes: ansible/ansible#67966
…ansible#61752)" This reverts part of ansible commit 72023d7. The immediate reason is that it breaks mounts where src is not a path. Examples of such mounts are network-based filesystems such as nfs, cifs, glusterfs, ceph, virtual filesystems such as tmpfs or overlayfs, and also UUID-based mounts. It is too hard to come with an exhaustive list, especially if we take non-Linux systems into account, so don't even try. Additionally, it did not really fix the issue (ansible/ansible#59183) that it intended to fix, because the mount could fail but leave a non-working fstab entry for reasons other than non-existing src path. Restore fstab and remove the mount point after a failed mount Add a reminder that not only devices can be mounted Fixes: ansible/ansible#65855 Fixes: ansible/ansible#67588 Fixes: ansible/ansible#67966 Signed-off-by: Alexander E. Patrakov <patrakov@gmail.com> Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
…ansible#61752)" This reverts part of ansible commit 72023d7. The immediate reason is that it breaks mounts where src is not a path. Examples of such mounts are network-based filesystems such as nfs, cifs, glusterfs, ceph, virtual filesystems such as tmpfs or overlayfs, and also UUID-based mounts. It is too hard to come with an exhaustive list, especially if we take non-Linux systems into account, so don't even try. Additionally, it did not really fix the issue (ansible/ansible#59183) that it intended to fix, because the mount could fail but leave a non-working fstab entry for reasons other than non-existing src path. Restore fstab and remove the mount point after a failed mount Add a reminder that not only devices can be mounted Fixes: ansible/ansible#65855 Fixes: ansible/ansible#67588 Fixes: ansible/ansible#67966 Signed-off-by: Alexander E. Patrakov <patrakov@gmail.com> Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
…ansible#61752)" (#33) This reverts part of ansible commit 72023d7. The immediate reason is that it breaks mounts where src is not a path. Examples of such mounts are network-based filesystems such as nfs, cifs, glusterfs, ceph, virtual filesystems such as tmpfs or overlayfs, and also UUID-based mounts. It is too hard to come with an exhaustive list, especially if we take non-Linux systems into account, so don't even try. Additionally, it did not really fix the issue (ansible/ansible#59183) that it intended to fix, because the mount could fail but leave a non-working fstab entry for reasons other than non-existing src path. Restore fstab and remove the mount point after a failed mount Add a reminder that not only devices can be mounted Fixes: ansible/ansible#65855 Fixes: ansible/ansible#67588 Fixes: ansible/ansible#67966 Signed-off-by: Alexander E. Patrakov <patrakov@gmail.com> Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com> Co-authored-by: Alexander E. Patrakov <patrakov@gmail.com>
SUMMARY
When using the ansible 'mount' module to mount an NFS export, the play fails with an error containing "... as it does not exist".
ISSUE TYPE
COMPONENT NAME
Ansible module mount
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Output of hostnamectl:
STEPS TO REPRODUCE
It appears that commit d2f45da changed the mount module in such a way that will always fail when working with NFS remote mounts.
The commit resulted in code including the following snippet:
This would seem to always fail. Simply commenting out lines 2 and 3 in the above snippet restores successful completion.
EXPECTED RESULTS
When doing NFS mounts, Ansible should either use something like
showmount` -e <nfsservername>
to verify if the remote export exists, or skip validation entirely in the case of NFS mounts.ACTUAL RESULTS
The play fails with an error including the text "as it does not exist".
The text was updated successfully, but these errors were encountered: