Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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.
Bug 1610695 - Cannot use compute resource name parameter
Summary: Cannot use compute resource name parameter
Status: CLOSED DUPLICATE of bug 1584785
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Sanket Jagtap
Depends On:
TreeView+ depends on / blocked
Reported: 2018-08-01 08:40 UTC by Sanket Jagtap
Modified: 2018-08-07 15:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-08-07 15:25:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1519779 0 unspecified CLOSED puppet classes info doesn't consider puppet environments parameter 2021-02-22 00:41:40 UTC

Internal Links: 1519779

Description Sanket Jagtap 2018-08-01 08:40:21 UTC
Description of problem:

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

How reproducible:

Steps to Reproduce:
2. Create a compute resource 
3. try to provision a host using --compute-resource parameter

hammer> compute-resource list
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

Comment 2 Sanket Jagtap 2018-08-01 09:54:25 UTC
This also effects compute-profile 

Workaround is to use compute-profile-id , where we need to identify compute-profile id from satellite UI

Comment 3 Brad Buckingham 2018-08-03 15:30:47 UTC
Is this a regression from 6.3?

Comment 4 Sanket Jagtap 2018-08-06 10:16:22 UTC
Yes, this is a regression from 6.3

Comment 6 Ivan Necas 2018-08-07 15:25:33 UTC

*** This bug has been marked as a duplicate of bug 1584785 ***

Note You need to log in before you can comment on or make changes to this bug.