Bug 916380
Summary: | add dbupgrade step to fix problem when an old bundle version was deleted in previous JON version | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Charles Crouch <ccrouch> |
Component: | Provisioning | Assignee: | John Mazzitelli <mazz> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | JON 3.0.1 | CC: | bkramer, hbrock, klaus.erber, loleary, mazz, vnguyen |
Target Milestone: | ER01 | ||
Target Release: | JON 3.2.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 826995 | Environment: | |
Last Closed: | 2014-01-02 20:43:06 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: | |||
Bug Depends On: | 826995, 826998 | ||
Bug Blocks: | 828905 |
Comment 1
Charles Crouch
2013-02-27 23:49:20 UTC
git commit to master: 9759daf74bf650e13764d80ef8fc4f67d1b8d269 To test this, you first have to get the database table rhq_bundle_version in a bad state. you can either follow the directions in this issue's description (From a JON 3.0.1 install, upload a bundle version 1, then a bundle version 2, then delete bundle version 1, then upload bundle version 3) or you can just artificially mess with the ordering by executing this simple UPDATE SQL - "update rhq_bundle version set version_order=2" (you do this against your database that already has a bundle versions in the db - if you do not, then you must upload some). Note that to really test this, you need to have more than one bundle in the database. So, for example, upload 3 bundle versions for bundle "foo" and upload 3 bundle versions for bundle "bar". You then delete both bundle version #2 for each bundle (or just run that SQL UPDATE to artificially alter them that simulates the bug). (In reply to comment #2) > git commit to master: 9759daf74bf650e13764d80ef8fc4f67d1b8d269 > > To test this, you first have to get the database table rhq_bundle_version in > a bad state. you can either follow the directions in this issue's > description (From a JON 3.0.1 install, upload a bundle version 1, then a > bundle version 2, then delete bundle version 1, then upload bundle version > 3) or you can just artificially mess with the ordering by executing this > simple UPDATE SQL - "update rhq_bundle version set version_order=2" (you do > this against your database that already has a bundle versions in the db - if > you do not, then you must upload some). > > Note that to really test this, you need to have more than one bundle in the > database. So, for example, upload 3 bundle versions for bundle "foo" and > upload 3 bundle versions for bundle "bar". You then delete both bundle > version #2 for each bundle (or just run that SQL UPDATE to artificially > alter them that simulates the bug). Of course, to test the fix, after you get the bundle versions in a bad state, you must then install/upgrade to the latest version such that the db-upgrade is triggered (and thus the fix is run). So: 1) get several bundles uploaded as per instructions above 2) make sure you have the db in a bad state by making sure this SQL returns at least 1 row: select name, version_order, count(version_order) from rhq_bundle_version t1 group by name, version_order having count(version_order) > 1; 3) install the latest version which will run the db upgrade 4) once the db upgrade is run, if you look in RHQ_BUNDLE_VERSION, all the version_order column values should now be valid. You will know its fixed if this SQL returns 0 rows now: select name, version_order, count(version_order) from rhq_bundle_version group by name, version_order having count(version_order) > 1; As this is MODIFIED or ON_QA, setting milestone to ER1. |