Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Ram Nayan Singh,
could you please share debug output of the command? It should help us to see what was returned from the server during the command execution?
Regards,
Martin
Ram Singh,
thanks for the logs it helped.
I can see two problems here. The first problem seems to be --compute-profile libvirt where libvirt is not a existing compute profile name but rather compute resource probably. From the logs I can see the valid profile names would be profile1, profile2 and 3-Large.
The other problem is a bug in hammer that prevents hammer from finding the correct profile by name.
The cause is that building of the search arguments is unintentionally modified by Katello plugin for hammer.
Updating the component.
VERIFIED
on sat6.5.0-19
the host can be successfully created by providing a compute-profile name
# hammer host create --build true --managed true --location MFZSePFwoR --organization MrWZyXcBJP --provision-method build --name test1 --ip 192.168.100.57 --hostgroup IOXDzanmfm --compute-profile 1-Small --mac de:ad:be:ea:ae:aa
Host created.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:1222