Bug 554712 - database migrations scripts failing on PostgreSQL
Summary: database migrations scripts failing on PostgreSQL
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Database
Version: 1.4.0.B01
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: rhq_triage
TreeView+ depends on / blocked
 
Reported: 2010-01-12 13:23 UTC by Sanne Grinovero
Modified: 2010-09-30 14:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-30 14:15:08 UTC
Embargoed:

Attachments (Terms of Use)

Description Sanne Grinovero 2010-01-12 13:23:59 UTC 
Description of problem:

Upgrading from JOPR 2.3.0 to RHQ 1.4.0.B01 is giving many errors while importing the database schema migrations, using PostgreSQL 8.4.2:

schema upgrade from version 2.58 to 2.61 is having some issues:
* two wrong insert statement for RHQ_DISTRIBUTION_TYPE_TABLE,
having more values than selected columns (missing the description column)
* attempt to rename a constraint, which is not implemented by PostreSQL
(this rename is not needed because the same constraint is created in same schemaSpec)

Version-Release number of selected component (if applicable):


How reproducible:
easy:

Steps to Reproduce:
1. install JOPR version 2.3.0 on PostgreSQL
2. upgrade to RHQ 1.4.0.B01

  
Actual results:
error messages on the "Welcome to RHQ!" web page

Expected results:
no errors

Additional info:
Comment 1 wes hayutin 2010-02-16 16:56:12 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 2 wes hayutin 2010-02-16 17:01:23 UTC 
making sure we're not missing any bugs in rhq_triage
Comment 3 Corey Welton 2010-09-30 14:15:08 UTC 
closing - fixed in latest release, no upgrade path to 1.4.0 B01 is ever going to be done..
Note You need to log in before you can comment on or make changes to this bug.