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 1785683

Summary: Does not load datacenter when multiple compute resources are created for same VCenter
Product: Red Hat Satellite Reporter: Surjeet Salvi <susalvi>
Component: Compute Resources - VMWareAssignee: Ondřej Ezr <oezr>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.6.0CC: chrobert, egolov, mhulan, oezr
Target Milestone: 6.8.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: foreman-2.1.0-0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:59:52 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 Surjeet Salvi 2019-12-20 16:43:19 UTC
Description of problem: Does not load datacenter when multiple compute resources are created for same VCenter


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

How reproducible:


Steps to Reproduce:
1. Create a Compute resource for the Vcenter having multiple Datacenter
2. Click test connection and connection will be successful and will load the Datacenter. 
3. Again try to create new computer resources for the same Vcenter.
4. once clicked on the Test connection, it is successful but not able to load the Datacenter list 

Actual results:
Test connection successful but data centers are not listed when multiple compute resource are created for same VCenter

Expected results:
It should load dataceters list after test connection is successful.

Additional info:

Comment 3 Surjeet Salvi 2020-01-21 16:34:02 UTC
Hello Team,

Could you please provide an update on Bugzilla.

Regards
Surjeet

Comment 5 Ondřej Ezr 2020-03-04 16:35:39 UTC
Created redmine issue https://projects.theforeman.org/issues/29265 from this bug

Comment 7 Bryan Kearney 2020-03-04 17:01:57 UTC
Upstream bug assigned to oezr

Comment 8 Bryan Kearney 2020-03-04 17:01:59 UTC
Upstream bug assigned to oezr

Comment 9 Bryan Kearney 2020-03-08 10:02:15 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29265 has been resolved.

Comment 11 Lukáš Hellebrandt 2020-07-08 14:55:01 UTC
Verified with Sat 6.8 snap 7.0 using a reproducer from OP. A VMWare instance can now be added as a CR multiple times, with correctly loaded datacenters.

Comment 14 errata-xmlrpc 2020-10-27 12:59:52 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