Bug 848066 - Compatible group configuration is not listing
Summary: Compatible group configuration is not listing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHQ 4.5.0
Assignee: Lukas Krejci
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 844989
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-14 13:50 UTC by Lukas Krejci
Modified: 2013-09-01 09:58 UTC (History)
2 users (show)

Fixed In Version:
Clone Of: 844989
Environment:
Last Closed: 2013-09-01 09:58:47 UTC
Embargoed:


Attachments (Terms of Use)

Description Lukas Krejci 2012-08-14 13:50:08 UTC
+++ This bug was initially created as a clone of Bug #844989 +++

Created attachment 601727 [details]
Compatible Group screen shot

Description of problem:
Compatible groups current configuration is not listing on GUI 

Version-Release number of selected component (if applicable):
RHQ
Version: 4.5.0-SNAPSHOT
Build Number: b49d9d3
GWT Version: 2.4.0
SmartGWT Version: 3.0

How reproducible:
100%

Steps to Reproduce:
1.Logon to RHQ GUI as a 'rhqadmin'
2.Navigate to 'Inventory--> Compatible Groups-->New'
3.Create a group with the resource 'RHQ Agent'
4.Navigate to 'Inventory--> Compatible Groups--><groupname-on-step-2>'
5.Navigate to 'Configuration-->Current'
Actual results:
Not showing any of the configuration

Expected results:
Should list available configurations

Additional info:
Screenshot is attached
Note: This issue was detected by overnight GUI automation.
I do not see any error messages on server log files.

Comment 1 Charles Crouch 2012-08-15 13:05:44 UTC
We already have a version of this bug targeting jon311 (844989), so setting the fix version to RHQ4.5 to make sure we get this fixed.

Comment 2 Lukas Krejci 2012-12-20 13:19:45 UTC
Could not reproduce this in RHQ 4.6.0-SNAPSHOT

Comment 3 Heiko W. Rupp 2013-09-01 09:58:47 UTC
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.


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