-
Notifications
You must be signed in to change notification settings - Fork 154
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 boot: false doesn't work on Linux, NetBSD and OpenBSD systems #364
Comments
copyrights
changed the title
mount boot: false doesn't work on Linux, FreeBSD, NetBSD and OpenBSD systems
mount boot: false doesn't work on Linux, NetBSD and OpenBSD systems
May 23, 2022
I guess the reason for the exception on
|
copyrights
changed the title
mount boot: false doesn't work on Linux, NetBSD and OpenBSD systems
mount boot: false doesn't work on Linux systems
May 23, 2022
copyrights
changed the title
mount boot: false doesn't work on Linux systems
mount boot: false doesn't work on Linux, NetBSD and OpenBSD systems
May 23, 2022
softwarefactory-project-zuul bot
added a commit
that referenced
this issue
Oct 4, 2024
mount: remove boot exception if defaults in opts SUMMARY There is no need for an exception on defaults option when adding noauto. Mount is implemented as last win. from mount(8): If you want to override mount options from /etc/fstab, you have to use the -o option: mount device|dir -o options and then the mount options from the command line will be appended to the list of options from /etc/fstab. This default behaviour can be changed using the --options-mode command-line option. The usual behavior is that the last option wins if there are conflicting ones. Fixes #364 ISSUE TYPE Bugfix Pull Request COMPONENT NAME ansible.posix.mount ADDITIONAL INFORMATION Reviewed-by: Hideki Saito <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
If
boot
option of mount module is set tofalse
it shall add noauto mount option on Linux, NetBSD and OpenBSD systems.But there are exceptions. E.g. if
defaults
inopts
ansible.posix/plugins/modules/mount.py
Line 746 in 2d3f55c
But this is always the case if
opts
is not set or not on Solaris.ansible.posix/plugins/modules/mount.py
Line 707 in 2d3f55c
Side note: Documentation is misleading as it says
opts
has no default value. In fact the default value is either "default" or "-".ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
no relevant
STEPS TO REPRODUCE
EXPECTED RESULTS
Device is mounted, but will not be mounted on next boot.
ACTUAL RESULTS
Device is mounted and will be mounted on next boot
The text was updated successfully, but these errors were encountered: