Bug 1610695

Summary: Cannot use compute resource name parameter
Product: Red Hat Satellite Reporter: Sanket Jagtap <sjagtap>
Component: HostsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Sanket Jagtap <sjagtap>
Severity: medium Docs Contact:
Priority: low    
Version: 6.4CC: inecas, mhulan, oprazak, sjagtap
Target Milestone: UnspecifiedKeywords: Regression
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-07 15:25:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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:
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
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 ***