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 1867895

Summary:	API Create vmware ComputeResource fails with "Datacenter can't be blank"
Product:	Red Hat Satellite	Reporter:	Tomer Brisker <tbrisker>
Component:	Compute Resources - VMWare	Assignee:	Shira Maximov <mshira>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	high	Docs Contact:
Priority:	high
Version:	Nightly	CC:	chrobert, inecas, jpathan, mawerner, mhulan, pcreech, sshtein
Target Milestone:	6.8.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-2.1.2	Doc Type:	Known Issue
Doc Text:	API Create vmware ComputeResource fails with "Datacenter can't be blank"	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:05:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomer Brisker 2020-08-11 07:16:24 UTC

When trying to create a new compute-resource via API (e.g. foreman-ansible-modules or hammer), the request fails with @Datacenter can't be blank@

<pre>
$ hammer compute-resource create --provider="VMWare" --name "vCenter" --description "Test vCenter" --user "administrator" --server "vsphere.example.com" --password 'secret' --datacenter "DEV"
Could not create the compute resource:
  Datacenter can't be blank
</pre>

I suspect the change from #30372 to be the reason for this, because it removes the @datacenter@-option from the compute-resource create instruction.

Comment 1 Tomer Brisker 2020-08-11 07:16:30 UTC

Created from redmine issue https://projects.theforeman.org/issues/30620

Comment 2 Tomer Brisker 2020-08-11 07:16:31 UTC

Upstream bug assigned to None

Comment 4 Tomer Brisker 2020-08-11 07:25:20 UTC

*** Bug 1867893 has been marked as a duplicate of this bug. ***

Comment 5 Bryan Kearney 2020-08-11 12:05:18 UTC

Upstream bug assigned to mshira

Comment 6 Bryan Kearney 2020-08-11 12:05:22 UTC

Upstream bug assigned to mshira

Comment 8 Bryan Kearney 2020-08-12 08:04:59 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30620 has been resolved.

Comment 9 Tomer Brisker 2020-08-24 08:35:45 UTC

*** Bug 1871711 has been marked as a duplicate of this bug. ***

Comment 10 Lukáš Hellebrandt 2020-09-07 14:56:09 UTC

Verified with Sat 6.8.

I've been able to add a CR through Hammer (which uses API). The CR is added with correct Datacenter specified (checked through WebUI) and Hosts can be created on it.
Also checked that this didn't break RHEV - it didn't, I still can add a RHEV CR and create hosts in it.

Comment 13 errata-xmlrpc 2020-10-27 13:05:24 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 (Important: Satellite 6.8 release), 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-2020:4366

Comment 14 errata-xmlrpc 2020-10-27 13:08:23 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 (Important: Satellite 6.8 release), 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-2020:4366