Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

vSphere plugin - Error setting availability for deleted VM not found reported in agent.log

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.5
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ-server 4.5.0-EE-144 running on CentOS 5.4
    HQ-agent 4.5.0-EE-143 running on Windows 2008
     - VMware vCenter Server 4.0 running with HQ-agent
  • Case Links:
    none
  • Regression:
    No

Description

vSphere plugin - Error setting availability for deleted VM not found reported in agent.log.

After moving an ESX host from the vCenter server and deleting it from the vCenter server, the agent.log reports:

2010-10-25 17:59:23,492 ERROR [pool-1-thread-9] [VSphereHostCollector] Error setting availability for FC-TemplateTest-VM1: VirtualMachine/4206ed55-040d-1c00-780d-9703aaf8a2e4: not found
2010-10-25 17:59:23,492 DEBUG [pool-1-thread-9] [VSphereHostCollector] org.hyperic.hq.plugin.vsphere.ManagedEntityNotFoundException: VirtualMachine/4206ed55-040d-1c00-780d-9703aaf8a2e4: not found
org.hyperic.hq.plugin.vsphere.ManagedEntityNotFoundException: VirtualMachine/4206ed55-040d-1c00-780d-9703aaf8a2e4: not found
at org.hyperic.hq.plugin.vsphere.VSphereUtil.findByUuid(VSphereUtil.java:204)
at org.hyperic.hq.plugin.vsphere.VSphereCollector.getManagedEntity(VSphereCollector.java:109)
at org.hyperic.hq.plugin.vsphere.VSphereHostCollector.collect(VSphereHostCollector.java:164)
at org.hyperic.hq.plugin.vsphere.VSphereCollector.collect(VSphereCollector.java:148)
at org.hyperic.hq.product.Collector.run(Collector.java:563)
at edu.emory.mathcs.backport.java.util.conTempcurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:619)

If the host and all associated VMs are removed, then all scheduled collections for those VMs should be removed.

Expected Result:
Collections are removed for deleted vSphere Hosts and VMs.

Actual Result:
Collections still occur for deleted vSphere Hosts and VMs.

Steps to Reproduce:
1. Register a second ESX host to existing HQ monitored vCenter Server
2. Ensure associated VMs are created for second ESX host
3. Allow second ESX host and VMs to be auto-discovered and metrics to collect
4. Restart hq-agent (to avoid waiting for timed auto-discover)
5. Ensure second ESX host and VMs show in HQ vSphere inventory tree
6. Delete second ESX host from vCenter
7. Restart hq-agent (to avoid waiting for timed auto-discovery)
8. Look at HQ vSphere inventory tree and note host and VMs are no longer displayed
9. Examine the agent.log and not reported Error setting availability for removed VMs

Activity

Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks, 4 days ago