Bug 641202 - No availability indicator for groups
No availability indicator for groups
Status: CLOSED WORKSFORME
Product: RHQ Project
Classification: Other
Component: Core UI (Show other bugs)
4.0.0
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Corey Welton
:
Depends On:
Blocks: gwt-groups
  Show dependency treegraph
 
Reported: 2010-10-07 22:00 EDT by Corey Welton
Modified: 2010-10-29 08:21 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-29 08:21:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Corey Welton 2010-10-07 22:00:55 EDT
Description of problem:
In the group view, there is no availability icon in the associated column for any of the groups, compat or mixed.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Create/populate a few mixed and compatible groups
2.  Navigate to Inventory > Groups
3.  Navigate to Inventory > Groups > Compatible Groups
4.  Navigate to Inventory > Groups > Mixed Groups
  
Actual results:
 Should be an indicator in the availability column for each of these.

Expected results:
 No indicator

Additional info:
FWIW, parity with older releases appears to be two separate indicators -- child resources and their descendants.  Not sure what the plan is going forward, just noting this as food for thought
Comment 1 Corey Welton 2010-10-07 22:01:36 EDT
errrr...

Expected results:
 No indicator

should be

Expected results:
Relevant indicator per up/down/unknown
Comment 2 Sudhir D 2010-10-29 08:21:46 EDT
Tested with the latest build of rhq-server-4.0.0-SNAPSHOT. I can see the availability column correctly populated as expected. I can see up/down

Closing this bug for now. Please reopen if issue regress.

Note You need to log in before you can comment on or make changes to this bug.