Bug 678941
Summary: | Agents list should indicate known problems with agents | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | James Livingston <jlivings> |
Component: | High Availability | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | joallen, loleary |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Livingston
2011-02-21 01:14:37 UTC
Essentially, a JON administrator or manager should be able to review the state of all agents within a JON system. This would make it easy to identify if an agent is off-line or unable to communicate to the JON server for one reason or another. Some use-cases: - What JON Agents are simply not running? (this can currently be obtained by agent availability) - What JON Agents failed to auto-upgrade after the new version of JON server was installed? - What JON Agents can not communicate with the JON server due to an incorrect end-point address or network communications error? - What JON Agents are currently running and reporting to/accepting commands from the JON server? Obviously, in some instances, we will not know why a JON agent is unavailable but in some instances we do know. Like version mismatch, talk-back on initial registration, agent reported itself as going down, agent's resources have been backfilled, etc. |