Menu

#4187 [HHQ-4058] Agent Connection not updated when ESX host moved

Bug
open
None
3
2012-10-09
2010-06-10
No

http://jira.hyperic.com/browse/HHQ-4058
Agent Connection not updated when ESX host moved from one vCenter server to another vCenter server. After the ESX host is reflected in the HQ vSphere UI under the new vCenter server, the Host and VMs display Agent Connection within Type & Network Properties with the old value that points to the old vCenter server



Expected Result:


When an ESX host is moved from one vCenter server to another vCenter server, the Host and VMs should update the Agent Connection value to reflect the new vCenter server.



Actual Result:


The Agent Connection for both Host and VMs still reference the old value which points to the old vCenter server.



Steps to reproduce:


1. Log into a vSphere client where an existing ESX host is managed by another vCenter server


2. Register a ESX host to the new vCenter server


3. Restart the hq-agent on the new vCenter server (to avoid waiting for auto-discovery collection)


4. Log into HQ Server and go to HQ vSphere UI


5. Expand tree and select a VM under the moved ESX host


6. Click the resource link to the VM


7, Go to the Inventory tab


8. Note the Agent Connection value within the Type & Network Properties section



Work around:


Manually edit the Type & Network properties to reflect the udpated vCenter server agent connection



Additional Notes:


The metrics are still collecting but may not be correctly reference the correct host

Discussion

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.