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

Nagios plugin - Nagios Server 3.2.3 not auto-discovered

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.6
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    Hyperic Server 4.6.0-EE-RC1 (8/2/11) on CentOS 5.4 x64 with embedded PostreSQL DB
    Hyperic Agent 4.6.0-EE-RC1 (8/2/11) on Fedora Core 15 x64 with Nagios 3.2.3
  • Case Links:
    none
  • Regression:
    No

Description

Nagios plugin - Nagios Server 3.2.3 not auto-discovered

After installing Hyperic agent on platform running Nagios 3.2.3, the platform is auto-discovered; however, the Nagios server is not auto-discovered to be monitored.

It is not auto-discovered for command line as well.

See attached nagios-cli-discover.log.

Expected Result:
Nagios server is auto-discovered

Actual Result:
Nagios server is not auto-discovered

Steps to Reproduce:

  1. Install and start Hyperic agent on platform running Nagios server
  2. Note platform running Nagios server is auto-discovered in AIQ
  3. Add platform running Nagios server to inventory from AIQ
  4. Note Nagios server is not auto-discovered
  5. Run command line auto-discover command
  6. Note Nagios server is not auto-discovered

Issue Links

Activity

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