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):
Steps to Reproduce:
1. From the 2.2.3 DB, run liquibase to update to 2.3.6 DB
Migration fails, two updates have different MD5SUMs.
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