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

Plugin Manager restarts agents while new resources are being added

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.6.5
  • Fix Version/s: None
  • Component/s: Plugins
  • Case Links:
  • Regression:
    No

Description

Symptoms:

Unconfigured resources in UI with error messages about not being about to connect to agent due to Connection Refused.

Steps to Reproduce:

1.) Add new agent to inventory
2.) Almost immediately afterwards upload new plugin via plugin manager

Actual Results:

Resources appear with grey availability in the UI. Upon viewing the resources the configuration error appears.

This resource is turned off or has not been configured properly.
The problem is: Invalid configuration: Error sending argument: Unable to connect to 192.168.69.105:2144: Connection refused, retried 5 times, cmd=rtm:getMeasurements
Please turn on the server, or fix its Configuration Properties.

Expected Results:

Auto discovered/manually added resources successfully added regardless of what plugin manager is doing

Activity

Hide
Wes Schlichter added a comment -

This isn't a new issue per-say. It's always been an issue when an agent was down/restarted after being added to auto inventory but in a multi-admin environment or an environment with automation this will become more and more prevailing. There needs to be special handling for "connection refused" agents to requeue and attempt once we hear from that agent again. I found this in my own plugin development environment (thanks to plugin dumper being broke HHQ-5532 I have to fully deploy the plugin to test)

Show
Wes Schlichter added a comment - This isn't a new issue per-say. It's always been an issue when an agent was down/restarted after being added to auto inventory but in a multi-admin environment or an environment with automation this will become more and more prevailing. There needs to be special handling for "connection refused" agents to requeue and attempt once we hear from that agent again. I found this in my own plugin development environment (thanks to plugin dumper being broke HHQ-5532 I have to fully deploy the plugin to test)
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:
    40 weeks, 4 days ago