Project

General

Profile

Actions

Bug #15626

closed

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

Added by Alexandre Barth almost 8 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
easy
Triaged:
Yes
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.

Actions #1

Updated by Dominic Cleal almost 8 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.

Actions #2

Updated by Alexandre Barth almost 8 years ago

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

Actions #3

Updated by Alik Agaev almost 6 years 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?

Actions #4

Updated by Chris Roberts over 5 years ago

  • Assignee set to Chris Roberts
Actions #5

Updated by Chris Roberts over 5 years ago

  • Bugzilla link set to 1647578
Actions #6

Updated by Chris Roberts almost 5 years ago

  • Status changed from New to Assigned
  • Difficulty set to easy
Actions #7

Updated by The Foreman Bot almost 5 years ago

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

Updated by The Foreman Bot almost 5 years ago

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

Updated by Chris Roberts almost 5 years ago

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

Updated by Marek Hulán almost 5 years ago

  • Fixed in Releases 1.23.0 added
Actions #11

Updated by Ondřej Ezr almost 5 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF