Bug 1572669 - Updating from Candlepin 2.2.3 DB to 2.3.6 using Liquibase results in checksum errors
Summary: Updating from Candlepin 2.2.3 DB to 2.3.6 using Liquibase results in checksum...
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 2.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: candlepin-bugs
QA Contact: Katello QA List
Depends On:
Blocks: 1576868 1576870
TreeView+ depends on / blocked
Reported: 2018-04-27 14:46 UTC by Shayne Riley
Modified: 2018-06-06 20:39 UTC (History)
4 users (show)

Fixed In Version: candlepin-2.5.3-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1576868 1576870 (view as bug list)
Last Closed: 2018-06-06 20:39:50 UTC

Attachments (Terms of Use)

Description Shayne Riley 2018-04-27 14:46:53 UTC
Description of problem:

Attempting to update a Candlepin DB from version 2.2.3 to 2.3.6 resulted in the following two errors:

db/changelog/20161109145238-add-owner-environment-content-access.xml::20161109145238-1::wpoteat was: 7:fcdf027933b5bdb5510975ba6fc119a1 but is now: 7:86907a72bb6a6107049aefc2e71c6fac

db/changelog/20170718095058-purge-orphaned-pools.xml::20170718095058-1::vrjain, crog was: 7:fd4c7e972e284a241ab0427648064af1 but is now: 7:8850f008ea669aded02fe31c9538c134

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

How reproducible:

Steps to Reproduce:
1. From the 2.2.3 DB, run liquibase to update to 2.3.6 DB

Actual results:
Migration fails, two updates have different MD5SUMs.

Expected results:
Migration succeeds.

Additional info:
The workaround for now is to comment out those two files from the update script.

I looked in PROD's DATABSECHANGELOG for these two entries, and I see we will hit this issue there too as the MD5SUMs match the same old values listed earlier: 7:fcdf027933b5bdb5510975ba6fc119a1 and 7:fd4c7e972e284a241ab0427648064af1

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