Skip to content
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

ucsmsdk.mometa.bios.BiosVProfile property reboot_on_update inconsistent behavior #123

Open
gve-vse-tim opened this issue Nov 29, 2019 · 0 comments

Comments

@gve-vse-tim
Copy link

When leveraging ucs_managed_objects to create a bios policy, the reboot_on_update property for the BiosVProfile class has 4 valid values: yes, no, true, false (according to https://github.com/CiscoUcs/ucsmsdk/blob/master/ucsmsdk/mometa/bios/BiosVProfile.py).

However, using true or false will result in Ansible always indicating a "changed" state despite setting the value properly in UCS.

I suspect the UCS is always storing it as yes/no so that, when queried, Ansible does not see true/false as a match and proceeds to set the value. UCS seems to understand true/false because it sets it appropriately in the policy.

The workaround is easy - use yes/no.

Doubt there is an easy fix but thought I'd post the issue in case there is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant