Bug 582992

Summary:	db-upgrade 2.78.8 broken
Product:	[Other] RHQ Project	Reporter:	Lukas Krejci <lkrejci>
Component:	Database	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Corey Welton <cwelton>
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.0.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-04-27 19:12:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***