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

XenServer plugin: not all CPUs shown as available for Xen Host CPU Autogroup

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.3
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ-server 4.3.0-EE-1433 running on CentOS 5.4
    HQ-agent 4.3.0-EE-1433 running on RHEL 5.4 connected remotely to XenServer 5.5
  • Case Links:
    none
  • Regression:
    No

Description

XenServer plugin: not all CPUs shown as available for Xen Host CPU auto group. On a server that has 4 CPUs, only two display as available; the other two are marked as Gray (No availability was collected in the specified time frame). The agent has been running through the weekend and still, the availability for the two CPUs are not collected. After restarting the remote hq-agent, the status shows as Red (0% availability).

Expected Result:
All CPUs should be marked as available and indicate correct status

Actual Result:
Two of the four CPUs are not available

Steps to reproduce:
1. Connect remote hq-agent to XenServer as described in documentation
2. Ensure hq-agent is running and XenServer is configured
3. Log into the HQ Server Dashboard
4. Browse and select the added Xen Server platform
5. Select the Xen Host CPU Autogroup from under the Platform Services Health section
6. Note two of the four CPUs show as available and the other two show as No Availability

Work around:
None

Additional Notes:

  • No specific error messages posted in remote agent.log
  • Restarting remote hq-agent does not help

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:
    42 weeks ago