Bug 1016649

Summary: Clicking ASSOCIATE button to associate content source to repository displays error in UI
Product: [JBoss] JBoss Operations Network Reporter: Sunil Kondkar <skondkar>
Component: ContentAssignee: Jirka Kremser <jkremser>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: high    
Version: JON 3.2CC: hrupp
Target Milestone: GA   
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: 2014-01-02 20:36:08 UTC 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 none

Description Sunil Kondkar 2013-10-08 13:24:38 UTC 
Description of problem:

Clicking on the button 'ASSOCIATE' on to associate content source to repository displays error in UI. There are no errors in logs.

Please refer the attached screenshot.

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

Version: 3.2.0.ER3
Build Number: c0742ed:cbad264

How reproducible:

Always

Steps to Reproduce:

1. Navigate to Administration->Content>Repositories
2. Click on link 'JBoss Patches'.
3. Click on the button ASSOCIATE in the section 'Content Sources Associated with This Repository'.

Actual results:

Clicking ASSOCIATE button to associate content source to repository displays error in UI

Expected results:

User should be able to associate content source to repository.

Additional info:
Comment 1 Sunil Kondkar 2013-10-08 13:25:39 UTC 
Created attachment 809282 [details]
Screenshot
Comment 2 Heiko W. Rupp 2013-10-08 16:23:21 UTC 
rhq/content/repo-plain.xhtml:336 says 
     <!-- The ability to associate/disassociate repos with content sources is not needed for JON. -->

If this is the case, we should probably disable that part
Comment 3 Heiko W. Rupp 2013-10-10 11:10:04 UTC 
( this works in JON 3.1.2 )
Comment 4 Heiko W. Rupp 2013-10-11 12:12:37 UTC 
This may have to do with the move of portal war from / to /portal

Jirka, can you please look into this?
Comment 5 Jirka Kremser 2013-10-14 14:19:30 UTC 
It was a regression caused by the '/' -> '/portal' move


branch:  release#jon3.2.x
link:    http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=c128a7fa9
time:    2013-10-14 16:16:37 +0200
commit:  c128a7fa91dcba89573a47351f903f312959dce6
author:  Jirka Kremser - jkremser
message: [BZ 1016649] - Clicking ASSOCIATE button to associate content source to
         repository displays error in UI - removing the "/portal"
         prefix, because the attribute "template" of the Facelets'
         element "composition" expects the relative path as a value.
Comment 6 Simeon Pinder 2013-12-13 16:13:51 UTC 
Moving this to ON_QA, as discussed in triage call (myarboro,loleary,spinder). This is already in the GA tag but somehow we didn't set this to ON_QA.
Comment 7 Sunil Kondkar 2013-12-16 09:59:24 UTC 
 Verified on Version : 3.2.0.GA Build Number : dcb8b6f:734bd56