Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
This is a resubmission of ansible/ansible#65869, which became necessary after splitting off the ansible.posix collection. Please apply ansible/ansible#68223 first.
The history is:
UUID=...
sources withmounted
state ansible/ansible#67588), while still leaving cases (e.g. bad mount options) where a broken fstab entry remains on the system.Therefore, this pull request reverts the bad fix and implements a hopefully better one, by letting the doomed mount fail and then dealing with the consequences (undoing the fstab line and directory creation).
In ansible/ansible#68102 @Akasurde confirmed that the bad fix needs to be reverted. In ansible/ansible#65869 there was a promise to test the new code, but so far it didn't materialize, and cannot materialize without ansible/ansible#68223.
ISSUE TYPE
COMPONENT NAME
mount
ADDITIONAL INFORMATION
See more discussion here: ansible/ansible#68155, ansible/ansible#68102, ansible/ansible#65544, ansible/ansible#65869.
Test cases: