Bug 1576868

Summary:	Updating from Candlepin 2.2.3 DB to 2.3.6 using Liquibase results in checksum errors
Product:	[Community] Candlepin	Reporter:	William Poteat <wpoteat>
Component:	candlepin	Assignee:	candlepin-bugs
Status:	CLOSED CURRENTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	2.3	CC:	candlepin-bugs, katello-qa-list, khowell, redakkan, skallesh, sriley, wpoteat
Target Milestone:	---	Keywords:	Triaged
Target Release:	2.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	candlepin-2.3.8-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1572669	Environment:
Last Closed:	2018-05-29 17:55:26 UTC	Type:	Bug
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:	1572669, 1576870
Bug Blocks:

Description William Poteat 2018-05-10 15:17:47 UTC

+++ This bug was initially created as a clone of Bug #1572669 +++

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):
2.3.6


How reproducible:
Always


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