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:
Created attachment 809282 [details] Screenshot
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
( this works in JON 3.1.2 )
This may have to do with the move of portal war from / to /portal Jirka, can you please look into this?
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.
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.
Verified on Version : 3.2.0.GA Build Number : dcb8b6f:734bd56