Bug 2225165 - Pipe fail in Postgres During Upgrade
Summary: Pipe fail in Postgres During Upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: postgresql-10-container
Version: 8.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
: 8.8
Assignee: Filip Januš
QA Contact: Lukáš Zachar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-24 12:59 UTC by doconnor
Modified: 2023-07-26 08:58 UTC (History)
2 users (show)

Fixed In Version: postgresql-10-container-1-219
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-26 08:58:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-163163 0 None None None 2023-07-24 15:13:21 UTC
Red Hat Product Errata RHBA-2023:4280 0 None None None 2023-07-26 08:58:49 UTC

Description doconnor 2023-07-24 12:59:11 UTC
Description of problem:
Pipe fail needs to be moved outside of the parenthesis in order to catch all errors inside of the code block, otherwise improper error code is returned. See https://github.com/sclorg/postgresql-container/pull/521


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


How reproducible:
Reproducible


Steps to Reproduce:
See test case https://github.com/sclorg/postgresql-container/pull/523/files

Actual results:
If an upgrade fails, a zero error code should be thrown

Expected results:
If an upgrade fails, a non-zero error code should be thrown

Additional info:
PRs have been merged and this is largely for tracking purposes

Comment 6 errata-xmlrpc 2023-07-26 08:58:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Updated Application Stream container images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:4280


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