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.
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.