-
Notifications
You must be signed in to change notification settings - Fork 14
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
Onyx modules appear to not be idempotent #6
Comments
I see the same issue with the Example task
Result
Switch logs
|
This collection is currently unmaintained, so nobody will work on your issue. See ansible-community/community-topics#136 for more information. If you're interested in mainting this collection yourself, please read the maintainer guidelines and let us know if you want to take over on Matrix: #community:ansible.com or on |
SUMMARY
I'm opening this as a documentation report because I don't know if this is a documentation issue, or if it is truly a defect with the Onyx modules.
It appears that several Onyx modules do not behave in an idempotent way. The active configuration is changed even if there are no changes that need to be made.
I am currently experiencing this behavior with the
onyx_config
andonyx_pfc_interface
modules. Looking at theonyx_config
documentation, it is possible that I am not understanding how the options available can be used to make the module behave in an idempotent way, and if that's true, I would appreciate it if some more examples could be added. However, theonyx_pfc_interface
module appears to not have any way of behaving in an idempotent manner.Examples:
With
dcb priority-flow-control enable force
already appearing in the active running configuration:Result:
With
interface ethernet 1/1-1/32 dcb priority-flow-control mode on force
already appearing in the active running configuration:Result:
Additionally, I can confirm that the active running configuration is actually changing, as I can see the
Generated at
timestamp changing.I can query the active running config myself and make changes only when I determine they are necessary, but it would be a lot simpler if the module could do it for me. Also, determining if a change needs to be made from a playbook perspective is a bit complicated, as config lines are often consolidated into a range with neighboring ports, neighboring VLAN ID's, etc (as can be seen in the above PFC example)
ISSUE TYPE
COMPONENT NAME
onyx_config.py
onyx_pfc_interface.py
ANSIBLE VERSION
The text was updated successfully, but these errors were encountered: