Project

General

Profile

Bug #15626

Associating VMs/hosts with multiple VMWare compute resources from same vcenter server

Added by Alexandre Barth over 3 years ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
easy
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

In my org we run several datacenters by geo site all managed by 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 correponding compute resource for each host in hosts view.

Associated revisions

Revision 21367aae (diff)
Added by Ondřej Ezr 6 months ago

Fixes #15626 - filters vmware vms by datacenter (#6722)

History

#1 Updated by Dominic Cleal over 3 years ago

  • Subject changed from Model problem with different VMWare compute resources from same vcenter server to Associating VMs/hosts with multiple VMWare compute resources from same vcenter server
  • Category set to Compute resources - VMware

If you view the VMs for a single datacenter compute resource (under the compute resource, VMs tab), does it show VMs across all datacenters? It might be the association isn't confined to one datacenter, so it reassigns hosts for all VMs it can see.

#2 Updated by Alexandre Barth over 3 years ago

Under the compute resource VMS tabs it is ok, i can only see vms running in this particular datacenter.

#3 Updated by Alik Agaev about 1 year ago

  • Triaged set to No

I would like to confirm this issue at our prod. environment with the Foreman 1.16.0.
Is there anything planned to be fixed?

#4 Updated by Chris Roberts 12 months ago

  • Assignee set to Chris Roberts

#5 Updated by Chris Roberts 11 months ago

  • Bugzilla link set to 1647578

#6 Updated by Chris Roberts 6 months ago

  • Difficulty set to easy
  • Status changed from New to Assigned

#7 Updated by The Foreman Bot 6 months ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6717 added

#8 Updated by The Foreman Bot 6 months ago

  • Pull request https://github.com/theforeman/foreman/pull/6722 added

#9 Updated by Chris Roberts 6 months ago

  • Triaged changed from No to Yes
  • Target version set to 1.23.0
  • Found in Releases 1.22.0 added
  • Found in Releases deleted (1.12.0)
  • Pull request deleted (https://github.com/theforeman/foreman/pull/6717)

#10 Updated by Marek Hulán 6 months ago

  • Fixed in Releases 1.23.0 added

#11 Updated by Ondřej Ezr 6 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF