NOTE: This issue is only for tracking the workaround for 2.3.1. The true fix for 3.0.0 will be tracked using Bug 566235.
The following workarounds have been implemented: 1) Change type to fileystem for CSP content sources w/ no password set. RHQ SVN, 1.3.1.GA_CP branch, r5290 (updated db-upgrade.xml) 2) Change default type to filesystem in dbsetup data.xml. JON SVN, 2.3.1.GA_CP branch, r10561 (updated jon-data.xml) TEST CASES FOR 1) ================= #1) a) Install JON 2.3.0.GA. b) Do *not* set a username or password on the pre-populated "JBoss Patch Content Source" content source. If a username and password are already set, unset them. Make sure the content source's download mode is set to DATABASE (the default). c) Upgrade to JON 2.3.1.GA. d) Go to the "JBoss Patch Content Source" content source. Verify that the download mode has been changed to FILESYSTEM. #2) a) Install JON 2.3.0.GA. b) Set a username and password on the pre-populated "JBoss Patch Content Source" content source. Make sure the content source's download mode is set to DATABASE (the default). c) Upgrade to JON 2.3.1.GA. d) Go to the "JBoss Patch Content Source" content source. Verify that the download mode is still set to DATABASE. TEST CASE FOR 2) ================ a) Install JON 2.3.1.GA (fresh install - not upgrade). b) Go to the pre-populated "JBoss Patch Content Source" content source. Verify that its download mode is set to FILESYSTEM.
Scenario 1.2 Verified.
Given scenario 1.2 - do we have a doco note indicating that users who have their download mode to DATABASE may want to consider changing it to FILESYSTEM?
Scenario 2.1 Fails QA. After installing new against a fresh db -- one named rhq_567413 to assure that it had never been used before -- Administration > Content > Content Sources > JBoss Patch Content Source, I get the following results: Type: JBossASPatchSource Name: JBoss Patch Content Source Description: All patches provided by the JBoss Subscription Sync Schedule: 0 0 3 * * ? Lazy Load: true Download Mode: DATABASE Creation Date: 1/14/70, 6:16:48 PM, EST Last Modified Date: 1/14/70, 6:16:48 PM, EST Last Download Error: None
Created attachment 395844 [details] Scenario 2.1 -- still reads "DATABASE" on fresh install.
Back to ASSIGNED
Scenario 1.1 also fails QA. Without populating the u/p fields, and then performing an upgrade results in "DATABASE" remaining as the download mode.
There was actually one other workaround added: 3) Change default mode to FILESYSTEM when user is creating a new JBoss CSP content source. TEST CASE FOR 3) ================ Create a new content source of type "JBoss AS Patch Content Source". Verify that the Download Mode field is set to FILESYSTEM by default on the create form.
RHQ SVN, 1.3.1.GA_CP branch, r5295 fixes a couple mistakes in the original fix (r5290) for workaround 1).
#1a verified on 2.3.1GA (rev5295)
Sorry, #1.1, not #1a
Test case 1.2 verified Test case 2 fails -- installing a fresh build against a new db results in a "Download Mode:" of "DATABASE".
Test #3 fails on oracle (2.3.1GA build), default is still DATABASE.
Third Time's the Charm...? Test 1.1 passes Test 1.2 passes
[15:10] <@cswiii> jweiss: did 2 pass, i take it? [15:10] <@jweiss> cswiii: yep Note: Test 3 (Comment #8) is not applicable for this bz, after further examination, due to other underlying issue(s). QA Verified.
Mass-closure of verified bugs against JON.