Bug 620724
Summary: | [db-upgrade] 2.91 -> 2.92 fails | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Lukas Krejci <lkrejci> |
Component: | Build System | Assignee: | Charles Crouch <ccrouch> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 4.0.0 | CC: | hbrock, hrupp |
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: | 2012-03-02 15:46:18 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: | |||
Bug Depends On: | |||
Bug Blocks: | 625146 |
Description
Lukas Krejci
2010-08-03 10:26:26 UTC
Git history shows Joe as the one who committed db.upgrade rev2.92 Root cause is: ERROR: duplicate key value violates unique constraint "rhq_permission_pk" Any idea how you might have hit that? was there a time when we introduced the new privs in release-3.0.0 and then removed them again? maybe that's how the privs got in in db version < 2.92? which would mean this is a non-issue. did you work in two different branches - release and master - and switch back and forth between them? if so, there's a possibility that schemaSpec X was schemaSpec X+offset in the other branch, which would cause upgrade issues like you're seeing. |