[oVirt shell (connected)]# action host 17fa99f1-a423-43d9-80d7-6940066c7496 activate --async true async : True host-id : 17fa99f1-a423-43d9-80d7-6940066c7496 job-id : 7d74db65-439a-4336-aad6-51ea6c323288 status-state: complete [oVirt shell (connected)]# action host 17fa99f1-a423-43d9-80d7-6940066c7496 deactivate --async moo async : False host-id : 17fa99f1-a423-43d9-80d7-6940066c7496 status-state: complete [oVirt shell (connected)]#
This is a behaviour of the server, not of the CLI. The CLI just sends the value to the server, and the server decides what is valid and what isn't. Changing this behavior may break backwards compatibility, as users may be already using values other than "true" and "false". We will review this as part of 3.5.
The proposed patch adds validation of boolean values in the RESTAPI, so if the CLI or SDK send an incorrect value the request will be rejected, for example: [oVirt shell (connected)]# action host node1 activate --async junk ==================================== ERROR ================================= status: 400 reason: Bad Request detail: Value "junk" isn't a valid boolean, it should be "true" or "false" ============================================================================
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA