Bug #3780
closed
"true" boolean value for "start" key inside --compute-attributes is not correctly interpreted
Description
When using hammer to create a host on a Libvirt provider, the --compute-attributes option accepts a "start" key to tell hammer if the new host must be immediately started.
The key is described as a boolean value, but when using "start=true" the new host is not started.
The new host is started, instead, if using "start=1".
Also "true" should be accepted, to be more user-friendly.
A different solution would be to only accept 1 and 0, but then the help output should be updated accordingly to better express this, and also any docs around, like the Success Story (http://projects.theforeman.org/issues/3297) which has an example containing "start=true".
Updated by Dominic Cleal about 8 years ago
- Related to Bug #16636: VM Autostart attribute ("compute_attributes":{"start":"1"}) requires value as a string, not boolean or number. added
Updated by Tomáš Strachota about 8 years ago
- Related to Tracker #16829: Tracker for compute resource related issues added
Updated by Tomáš Strachota over 7 years ago
- Related to Tracker #18935: Tracker for issues related to processing of nested options in host create added
Updated by Shira Maximov almost 5 years ago
- Status changed from New to Rejected
The correct way to start the vm is to do that with 1, as it mentioned n the help:
['start', _('Boolean (expressed as 0 or 1), whether to start the machine or not')]