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.

Bug 1396028

Summary: Compute resource create for vmware and ovirt should accept option datacenter
Product: Red Hat Satellite Reporter: Ranjan Kumar <rankumar>
Component: APIAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Swapnil Abnave <sabnave>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.2CC: bbuckingham, dhlavacd, inecas, jcallaha, mhulan, sabnave, tstrachota
Target Milestone: UnspecifiedKeywords: Triaged
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-02-21 16:51:07 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 Ranjan Kumar 2016-11-17 09:41:29 UTC
Description of problem: 

Creating vmware compute resource throws error "Datacenter can't be blank"

hammer compute-resource create --provider="VMWare" --name "vCenter" --description "Test vCenter" --user "Administrator" --url "vmware.example.com" --password ComplexPassword
Could not create the compute resource:
Datacenter can't be blank


Creating vmware compute resource do not accept option datacenter

hammer compute-resource create --provider="VMWare" --name "vCenter" --description "Test vCenter" --user "Administrator" --url "vmware.example.com" --password ComplexPassword --datacenter Datacenter
Could not create the compute resource:
Error: Unrecognised option '--datacenter'

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


How reproducible: Always


Steps to Reproduce:
1.
2.
3.

Actual results: should accept option datacenter


Expected results:


Additional info:

Comment 1 Bryan Kearney 2016-11-17 11:20:33 UTC
Upstream bug component is API

Comment 2 Bryan Kearney 2016-11-17 11:20:36 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17200 has been resolved.

Comment 4 Swapnil Abnave 2017-08-03 15:07:05 UTC
Verified Satellite 6.3 SNAP 9

* satellite-6.3.0-16.0.beta.el7sat.noarch
* foreman-1.15.2-1.el7sat.noarch
* katello-3.4.2-1.el7sat.noarch

# hammer compute-resource create --provider="VMWare" --name "vCenter" --description "Test vCenter" --user "Administrator" --url "bkr-hv03-guest14.dsal.lab.eng.bos.redhat.com" --password ComplexPassword --datacenter Datacenter
Compute resource created
# hammer compute-resource list
---|---------|---------
ID | NAME    | PROVIDER
---|---------|---------
1  | vCenter | VMware  
---|---------|---------

Comment 5 Satellite Program 2018-02-21 16:51:07 UTC
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-2018:0336