Bug 1647578 - Associating VMs with multiple VMWare compute resources from same vcenter server fails
Summary: Associating VMs with multiple VMWare compute resources from same vcenter serv...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: 6.6.0
Assignee: Chris Roberts
QA Contact: Lukáš Hellebrandt
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-07 20:03 UTC by Chris Roberts
Modified: 2023-12-15 16:12 UTC (History)
6 users (show)

Fixed In Version: foreman-1.22.0.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:47:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15626 0 Normal Closed Associating VMs/hosts with multiple VMWare compute resources from same vcenter server 2020-07-20 13:13:27 UTC
Github theforeman foreman pull 6722 0 None closed Fixes #15626 - filters vmware vms by datacenter 2020-07-20 13:13:27 UTC

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


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