Bug 1647578

Summary: Associating VMs with multiple VMWare compute resources from same vcenter server fails
Product: Red Hat Satellite Reporter: Chris Roberts <chrobert>
Component: Compute Resources - VMWareAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: chrobert, lhellebr, mhulan, mlinden, ptrivedi, suarora
Target Milestone: 6.6.0Keywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: https://projects.theforeman.org/issues/15626
Whiteboard:
Fixed In Version: foreman-1.22.0.2-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 19:47:21 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 Chris Roberts 2018-11-07 20:03:51 UTC 
Cloned from Redmine:

In my org, we run several datacenters by geo site all managed by the same vcenter.
On my foreman server, I create corresponding compute resources with the same vcenter server URL but different datacenters.

The associate vms button in foreman conpute resource seems to be linked to vcenter server, not datacenters.

If I run the associate vms button in my compute resource Datacenter_1, in hosts view the model column becomes Datacenter_1 for each host, even hosts running in other datacenters (Datacenter_2, Datacenter_3).

Then if I run the associate vms button in compute resource Datacenter_2, all hosts update their model with Datacenter_2.

I'd like to see the corresponding compute resource for each host in the hosts view.

I would like to confirm this issue at our prod. the environment with the Foreman 1.16.0.
Comment 5 Bryan Kearney 2019-05-02 10:04:29 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/15626 has been resolved.
Comment 9 Lukáš Hellebrandt 2019-07-15 14:30:01 UTC 
Verified with Sat 6.6 snap 10 using reproducer from OP.
Comment 10 Bryan Kearney 2019-10-22 19:47:21 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-2019:3172