Bug 1785683 - Does not load datacenter when multiple compute resources are created for same VCenter
Summary: Does not load datacenter when multiple compute resources are created for same...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.6.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: 6.8.0
Assignee: Ondřej Ezr
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-20 16:43 UTC by Surjeet Salvi
Modified: 2023-09-07 21:19 UTC (History)
4 users (show)

Fixed In Version: foreman-2.1.0-0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:59:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 29265 0 Normal Closed Does not load datacenter when multiple compute resources are created for same VCenter 2020-10-28 17:22:10 UTC
Github theforeman foreman pull 7489 0 None closed Fixes #29265 - do not cache datacenters list 2020-10-28 17:22:10 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:00:06 UTC

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


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