Bug 582992 - db-upgrade 2.78.8 broken
Summary: db-upgrade 2.78.8 broken
Keywords:
Status: CLOSED DUPLICATE of bug 582991
Alias: None
Product: RHQ Project
Classification: Other
Component: Database
Version: 3.0.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-16 11:18 UTC by Lukas Krejci
Modified: 2010-04-27 19:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-27 19:12:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Lukas Krejci 2010-04-16 11:18:33 UTC
Description of problem:

When trying to upgrade the database from RHQ 1.3.1 to the current master, the
script fails when trying to apply the changes for schema version 2.78.8
complaining about a non-existent relation.

How reproducible:

always

Steps to Reproduce:
1. Update settings.xml to point to an rhq 1.3.1  database (or modify the below
mvn execution to define the overrides of the db connection properties)
2. run mvn -Ddbsetup-upgrade from modules/core/dbutils
3. Wait a bit for the error message

Actual results:

Upgrade fails

Expected results:

Upgrade shouldn't fail.

Additional info:

I think this is caused by the fact the the upgrade is trying to update RHQ_BUNDLE_DEPLOY_HISTORY table but such table doesn't exist. The closest one to the name is RHQ_BUNDLE_DEPLOY_HIST.

Comment 1 Charles Crouch 2010-04-27 19:12:30 UTC
Track previous problems with dbupgrade under 582991, should now be fixed

*** This bug has been marked as a duplicate of bug 582991 ***


Note You need to log in before you can comment on or make changes to this bug.