Bug 1503179 - Liquibase migration fails when activation keys referencing missing products exist
Summary: Liquibase migration fails when activation keys referencing missing products e...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 2.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.1
Assignee: candlepin-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 1503176
Blocks: 1503177
TreeView+ depends on / blocked
 
Reported: 2017-10-17 14:00 UTC by Barnaby Court
Modified: 2021-12-10 15:20 UTC (History)
6 users (show)

Fixed In Version: candlepin-2.1.7-1
Clone Of: 1503176
Environment:
Last Closed: 2017-10-19 18:07:00 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github candlepin candlepin pull 1757 0 None None None 2017-10-19 14:17:22 UTC

Description Barnaby Court 2017-10-17 14:00:32 UTC 
+++ This bug was initially created as a clone of Bug #1503176 +++

Description of problem:

When migrating from 0.9.54 to 2.x, if a database has activation keys that are referencing products that have been deleted, the migration will fail.  The failure occurs in PerOrgsProductsMigrationTask due to the presence of the records in cp_activationkey_product that reference the missing products.

Version-Release number of selected component (if applicable): 2.x series

How reproducible: Always

Steps to Reproduce:
1. Starting with 0.9.54, create an activation key using a productId that does not exist.
2. Attempt to migrate to candlepin 2.0.

liquibase --driver=org.postgresql.Driver --classpath=/usr/share/java/postgresql-jdbc.jar:/var/lib/tomcat/webapps/candlepin/WEB-INF/classes/ --changeLogFile=db/changelog/changelog-update.xml --url=jdbc:postgresql:candlepin --username=candlepin  --password=<PASSWORD> migrate -Dcommunity=False

Actual results:

Liquibase update Failed: Migration failed for change set db/changelog/20150210094558-perorgproducts-phase-1.xml::20150210094558-35::crog:
     Reason: liquibase.exception.UnexpectedLiquibaseException: liquibase.exception.CustomChangeException: liquibase.exception.DatabaseException: One or more orgs failed data validation

Expected results:

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