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 - Command line discover finds zero servers

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.4.0.2, 4.5, 4.6, 4.x Sprint 27
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    Hyperic server 4.6.0-EE-242 on CentOS 5.4 x64 with external MySQL DB
    Hyperic agent 4.6.0-EE-242 on Windows 2008
     - vCenter Server 4.0 running on agent platform
  • Case Links:
    none
  • Regression:
    No

Description

vSphere plugin - Command line discover finds zero servers

Running local command 'C:\sw\hyperic\4.6.0-EE-244\hyperic-hqee-agent-4.6.0.BUILD-SNAPSHOT\bundles\agent-4.6.0.BUILD-SNAPSHOT\pdk\lib>java -jar hq-pdk-4.6.0.BUILD-SNAPSHOT.jar -Dplugins.include=vsphere -m discover -Dlog=debug' results with: 0 servers detected

See attached 'vsphere-discover-cli.log' for full output.

Even specifying -Durl, -Duser and -Dpass (as with remote agents):

java -jar hq-pdk-4.6.0.BUILD-SNAPSHOT.jar -Dplugins.include=vsphere -m discover -Durl=https://[IP]/sdk -Duser=[username] -Dpass=[password] -Dlog=debug

The results have the same output: 0 servers detected.

Expected Result:
Command line discover for vSphere functions correctly and discovers servers

Actual Result:
Command line discover for vSphere result shows 0 servers detected

Steps to Reproduce:

  1. Run command line discover on vSphere server
  2. Note result: 0 servers discovered

Additional Information:
This does not work with 4.5 nor 4.4.0.2 (there is a bug in 4.4.0.2 which requires workaround for CLI to function)

Issue Links

Activity

Hide
Frederic Calindas added a comment -

Not regression.... same result for 4.5 and 4.4.0.2

Show
Frederic Calindas added a comment - Not regression.... same result for 4.5 and 4.4.0.2
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:
    40 weeks, 3 days ago