You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If using check mode in a playbook that uses module ome_identity_pool, the entire task is skipped, rather than evaluate if changes would be made without actually changing them.
Component Name
ome_identity_pool
Ansible Version
ansible 2.10.11
iDRAC or OpenManage Enterprise version
OME-M version 1.30.10
Steps to Reproduce
Add task to playbook that calls ome_identity_pool and attempt to run with check mode enabled
Playbook used
Expected Results
Changes would be evaluated but not actually made
Actual Results
Task is skipped entirely, not giving any feedback if changes would be made
Community Note
Please vote on this issue by adding a 👍 reaction
to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions,
they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Summary
If using check mode in a playbook that uses module ome_identity_pool, the entire task is skipped, rather than evaluate if changes would be made without actually changing them.
Component Name
ome_identity_pool
Ansible Version
iDRAC or OpenManage Enterprise version
OME-M version 1.30.10
Steps to Reproduce
Add task to playbook that calls ome_identity_pool and attempt to run with check mode enabled
Playbook used
Expected Results
Changes would be evaluated but not actually made
Actual Results
Task is skipped entirely, not giving any feedback if changes would be made
Community Note
to the original issue to help the community and maintainers prioritize this request
they generate extra noise for issue followers and do not help prioritize the request
The text was updated successfully, but these errors were encountered: