Project

General

Profile

Bug #3780

"true" boolean value for "start" key inside --compute-attributes is not correctly interpreted

Added by Marco De Vitis over 7 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:
yes

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


Related issues

Related to Foreman - Bug #16636: VM Autostart attribute ("compute_attributes":{"start":"1"}) requires value as a string, not boolean or number.New2016-09-21
Related to Hammer CLI - Tracker #16829: Tracker for compute resource related issuesClosed

Related to Hammer CLI - Tracker #18935: Tracker for issues related to processing of nested options in host createClosed

History

#1 Updated by Tomáš Strachota over 7 years ago

  • Assignee set to Tomáš Strachota

#2 Updated by Dominic Cleal almost 5 years ago

  • Related to Bug #16636: VM Autostart attribute ("compute_attributes":{"start":"1"}) requires value as a string, not boolean or number. added

#3 Updated by Tomáš Strachota almost 5 years ago

  • Category set to Hosts

#4 Updated by Tomáš Strachota almost 5 years ago

  • Related to Tracker #16829: Tracker for compute resource related issues added

#5 Updated by Tomáš Strachota over 4 years ago

  • Related to Tracker #18935: Tracker for issues related to processing of nested options in host create added

#6 Updated by Shira Maximov over 1 year ago

  • Assignee deleted (Tomáš Strachota)

#7 Updated by Shira Maximov over 1 year ago

  • In Kanboard set to yes

Changing the

#8 Updated by Shira Maximov over 1 year ago

  • Triaged changed from No to Yes

#9 Updated by Shira Maximov over 1 year 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')]

Also available in: Atom PDF