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

Adding 16th agent does not show in HQ Health Agents

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.5
  • Fix Version/s: None
  • Component/s: Agent / PDK
  • Environment:
    HQ-server 4.5.0-EE-135 running on RHEL 5.4
    HQ-agent 4.5.0-EE-135 running on CentOS 5.4
  • Case Links:
    none
  • Regression:
    No

Description

Adding 16th agent does not show in HQ Health Agents.

After installing an agent on a CentOS server, the platform was correctly auto-discovered by Hyperic and was manually added to inventory.

The agent added was setup as uni-directional and used for remote agent connection for Gemfire Distributed Platform.

Looking at HQ Health Agents, the newly added agent does not display in the list.

Previously to adding this agent, 15 agents were already displayed in HQ Health Agents. This agent should have been displayed as the first item on the next page (15 per page).

Adding a 17th agent correctly showed in HQ Health Agents as the first item on the second page in HQ Health Agents.

Running a SQL query on the agents, the missing agent (from HQ Health Agents) is returned in the results.

There is no errors reported in the server.log. See attached 'Server log for added Agent.log' for when agent was added to inventory.

Unfortunately, the agent.log has rolled and I was unable to capture any information.

Expected Result:
All added agents display in HQ Health Agents

Actual Result:
Added agent is missing from HQ Health Agents

Steps to Reproduce (this is what was done when this issue occurred):
1. Existing Hyperic Server has 15 agents displayed in HQ Health Agents
2. Add new agent and setup with uni-directional
3. Add new agent (step 2) into inventory from auto-discovery
4. Create Gemfire Distributed System platform using new agent (step 2)
5. Examine HQ Health Agents
6. Note the newly added agent (step 2) is not displayed in the list
7. Note the pagination goes to a blank page
8. Add another new agent
9. Add second agent (step 8) into inventory from auto-discovery
10. Examine HQ Health Agents
11. Note second agent (step 8) is displayed as first item on the second page

Additional Note:
The Current Platform Count under HQ License Information does not match the License Count if adding up the agents listed in HQ Health Agents.

Activity

Hide
Frederic Calindas added a comment -

This issue is reproducible. The 16th item in HQ Health Agents is not displayed.

After deleting servers that were on the list prior to the 16th agent being added, the missing server was displayed as the 15th item in the list in HQ Health Agents.

Adding a new 16th agent did not show up in the HQ Health Agents list. The pagination was there but the list was empty.

It does not matter if a uni-directional or bi-directional agent is added.

Show
Frederic Calindas added a comment - This issue is reproducible. The 16th item in HQ Health Agents is not displayed. After deleting servers that were on the list prior to the 16th agent being added, the missing server was displayed as the 15th item in the list in HQ Health Agents. Adding a new 16th agent did not show up in the HQ Health Agents list. The pagination was there but the list was empty. It does not matter if a uni-directional or bi-directional agent is added.
Hide
Kashyap Parikh added a comment -

This is dojo table issue similar to HHQ-2001

Show
Kashyap Parikh added a comment - This is dojo table issue similar to HHQ-2001
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