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.
Description of problem:
Version-Release number of selected component (if applicable):
Satellite 6.4.0 snap14
How reproducible:
Always
Steps to Reproduce:
2. Create a compute resource
3. try to provision a host using --compute-resource parameter
hammer> compute-resource list
---|---------|---------
ID | NAME | PROVIDER
---|---------|---------
1 | rhv | RHV
2 | vmware1 | VMware
---|---------|---------
Actual results:
hammer> host create --name test-host-cp --hostgroup rhel7_hstgrp --compute-resource "vmware1" --compute-profile 2-Medium --location "Default Location" --organization-id 1
Could not create the host:
Error: Found more than one compute_resource.
Expected results:
There is just one compute resource with that specify name , so it should select it.
Additional info:
Workaround is to use --compute-resource-id instead of --compute-resource