Bug 824439

Summary: Links in 'Group: Operations' and 'Group: alerts' portlet are not working in 'Summary->Activity page of autogroup
Product: [JBoss] JBoss Operations Network Reporter: Sunil Kondkar <skondkar>
Component: UIAssignee: Jirka Kremser <jkremser>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.1.0CC: imaleev, jkremser
Target Milestone: ER01   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot_Links
none
Screenshot_WarningMessage
none
Screenshot_Link-ViewGroupDefinition none

Description Sunil Kondkar 2012-05-23 13:13:20 UTC 
Description of problem:

After executing an operation and firing an alert on autogroups, clicking on the link for operation name in 'Group: Operations' portlet and the link 'Creation Time' for the alert in 'Group: alerts' portlet display a warning message "Group with id [10021] does not exist or is not accessible" in UI.

Please refer the attached screenshots

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

Version: 3.1.0.ER4
Build Number: 1783b86:2b8d25d

Browser: Firefox 10.0.2

How reproducible:

Always

Steps to Reproduce:

1. Login as rhqadmin and navigate to operations->Schedules tab of an autogroup (Ex: autogroup 'Apache HTTP Servers')
2. Click on 'New' button
3. Select operation 'Check Configuration File Syntax' from 'Operation' dropdown.
4. Click on 'Schedule' button.
5. After the above operation, it navigates to the 'Summary->Activity page of autogroup
6. Click on the operation name link in 'Group: Operations' portlet.
7. UI displays a warning message "Group with id [10021] does not exist or is not accessible"

8. Define and fire an alert on autogroup (Defined and fired alert for operation execution on autogroup 'Apache HTTP Servers')
9. Navigate to 'Summary->Activity page of autogroup.
10.Click on the 'Creation Time' link for the alert in 'Group: alerts' portlet.
11. UI displays a warning message "Group with id [10021] does not exist or is not accessible"
  
Actual results:

UI displays a warning message "Group with id [10021] does not exist or is not accessible"
  

Expected results:
The links should work

Additional info:
Comment 1 Sunil Kondkar 2012-05-23 13:14:00 UTC 
Created attachment 586347 [details]
Screenshot_Links
Comment 2 Sunil Kondkar 2012-05-23 13:14:55 UTC 
Created attachment 586348 [details]
Screenshot_WarningMessage
Comment 3 Sunil Kondkar 2012-05-24 12:11:30 UTC 
Additional Info:

One more place related to autogroups where the same warning occurs:

1. Login as rhqadmin and define an alert on an autogroup. (Defined alert for operation execution on autogroup 'Apache HTTP Servers')
2. Navigate to 'Alerts->Definitions' tab of a member resource in the autogroup (Ex: apache resource)
3. Click on the link 'View Group Definition'.
4. UI displays a warning message "Group with id [10021] does not exist or is not accessible" 

Please refer attached screenshot for the link.
Comment 4 Sunil Kondkar 2012-05-24 12:12:24 UTC 
Created attachment 586613 [details]
Screenshot_Link-ViewGroupDefinition
Comment 5 Mike Foley 2012-05-29 14:41:06 UTC 
per BZ Triage 5/29/2012 (ccrouch, loleary, asantos, mfoley, myarborough) moving these to JON 3.1.1 or later
Comment 6 mark yarborough 2012-11-06 20:05:06 UTC 
Per 3.1.2 triage with loleary, mfoley, ccrouch, asantos: Okay to move to JON 3.2.
Comment 7 Jirka Kremser 2013-04-11 19:50:33 UTC 
fixed in master

commits:
9ab3c227a
a2b61b08b
de18f7546

https://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=9ab3c227a
https://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=a2b61b08b
https://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=de18f7546
Comment 8 Heiko W. Rupp 2013-06-19 09:52:01 UTC 
*** Bug 928787 has been marked as a duplicate of this bug. ***
Comment 9 Larry O'Leary 2013-09-06 14:31:56 UTC 
As this is MODIFIED or ON_QA, setting milestone to ER1.
Comment 10 Sunil Kondkar 2013-09-23 11:43:26 UTC 
Verified on JBoss ON Version: 3.2.0.ER1- Build Number: 54dd29c:464a643