-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
parted: ansible detects a change only in dry-run #183
Comments
Dear @Wohlraj Your ansible version is 2.8.5, branch 2.8 is currently accepting only critical bugfixes. Could you repeat your test in current version (2.10 prerelase from devel branch)? From what I can read in current version parted module is more consistent and returns changed=True whenever parted command (except print) is run or would be run if check mode wasn't enabled, just like script/command modules do. (Keep in mind: I'm not a project maintainer, just a contributor interested in parted module) |
Hint not related to your issue with ansible: you may use whole device for LVM physical volume without creating any partitions on it. I prefer this method, but I understand that it could be confusing because someone may not recognize that the device is already used, which may have terrible consequences. |
My previous comments were not so accurate, so I edited them. Parted module tries to detect if change in flags is needed, but it doesn't handle check mode well. I'll make a PR soon. |
SUMMARY
Once the partition initially created, subsequent run give:
The only difference there is between the two runs is the following line:
ISSUE TYPE
COMPONENT NAME
parted
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
RHEL 7.4. Using SAN storage with multipath.
STEPS TO REPRODUCE
EXPECTED RESULTS
Return "ok", which is what is returned without dry-run.
Here is the output without dry-run:
ACTUAL RESULTS
Returns "changed" only in dry-run:
The text was updated successfully, but these errors were encountered: