Bug 1397497 - Liquibase changed default blob type for PostgreSQL, causing the deploy to fail during liquibase update.
Summary: Liquibase changed default blob type for PostgreSQL, causing the deploy to fai...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 2.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Alex Wood
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-22 16:08 UTC by David Šarman
Modified: 2019-09-24 17:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-24 17:13:51 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Šarman 2016-11-22 16:08:41 UTC 
Description of problem:
In Liquibase 3.5.2, the default blob type for PostgreSQL was changed from bytea to oid (see http://www.liquibase.org/2016/09/liquibase-3-5-2-released.html).
This causes the deploy(more specifically the liquibase update part) to fail.


How reproducible:
Always

Steps to Reproduce:
1.Update liquibase to version 3.5.2
2.Run deploy

Actual results:
Liquibase update fails with following exception:
Unexpected error running Liquibase: liquibase.exception.CustomChangeException: org.postgresql.util.PSQLException: ERROR: column "cert" is of type oid but expression is of type bytea
  Hint: You will need to rewrite or cast the expression.
  Position: 131

Expected results:
Liquibase update succeeds.
Comment 1 Barnaby Court 2016-11-28 16:00:47 UTC 
We currently pin the version at 3.1.0, is there a particular feature you are looking for from 3.5.2?
Comment 2 Alex Wood 2016-11-29 14:43:03 UTC 
Barnaby,

The Liquibase version now available in Fedora is now 3.5.2 so that's what bin/deploy is using.

David,

I've addressed that issue with 6f07576b11a65546efc44a83de9785b9f206f798 which is in master.  If you're working on a specific branch, you can cherry-pick that commit; it should apply cleanly.
Note You need to log in before you can comment on or make changes to this bug.