Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
hammer host create command does not power on the VM on compute resource unless --compute-attributes start=1 is used in Red Hat Satellite 6

Version-Release number of selected component (if applicable):


How reproducible:

While using a hostgroup the below command creates the host but it does not start the vm

# hammer host create --name myhost --hostgroup hg --location GSS --organization RedHat


We need to add --compute-attributes start=1 to start it on the compute resource. So the command becomes:

# hammer -d host create --name myhost --hostgroup hg --location GSS --organization RedHat --compute-attributes start=1

We do not need this while using web ui probably because its hard coded.

Hi,
this is expected behavior, confirmed with our QAs,
I suggest closing the BZ as not a bug.
Thanks you

Sure. closing this.