Bug 1281671

Summary: [rhscl/postgresql-94-rhel7] Postgresql pod is CrashLoopBackOff if using persistent storage
Product: Red Hat Software Collections Reporter: wewang <wewang>
Component: rh-postgresql94-containerAssignee: Pavel Raiskup <praiskup>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: low Docs Contact:
Priority: medium    
Version: rh-postgresql94CC: aos-bugs, bparees, eparis, hhorak, jokerman, kanderso, mmccomas, mnagy, praiskup, wewang, wzheng, xtian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rh-postgresql94-docker-9.4-3 Doc Type: Bug Fix
Doc Text:
A slave container failed to start because of incorrectly located templates for configuration files. The location of these templates has been fixed, and the slave container now starts as expected.
Story Points: ---
Clone Of: 1276326
: 1282733 (view as bug list) Environment:
Last Closed: 2015-12-09 15:17:31 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: 1276326    
Bug Blocks: 1281665, 1282733    

Comment 9 Honza Horak 2015-11-20 10:24:40 UTC
Is this something we have a fix for or there is no fix yet?

Comment 12 Ben Parees 2015-11-20 14:47:51 UTC
Pavel, it's not so simple as that.  Openshift does things with volume permissions when it provides a persistent volume, so just testing with a standard docker volume is not sufficient to reproduce this.

Comment 13 Pavel Raiskup 2015-11-20 16:01:21 UTC
Well, I don't understand this.  Once you have failed container, you probably
see what are the permissions of data directory so you you can really easily
reproduce that without openshift, or?

Comment 15 Martin Nagy 2015-11-25 08:43:35 UTC
This looks like the image in question is missing this update: https://github.com/openshift/postgresql/pull/82
Can someone responsible for the images confirm?

Comment 16 Pavel Raiskup 2015-11-25 09:04:13 UTC
Confirmed.

Comment 17 Ben Parees 2015-11-26 04:48:55 UTC
So this is waiting for the image to be updated?

Note also that there were some permission issues resolved by fixing NFS settings here:
https://bugzilla.redhat.com/show_bug.cgi?id=1282733#c48

which should be applicable to any verification attempt.

Comment 24 errata-xmlrpc 2015-12-09 15:17:31 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, 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://rhn.redhat.com/errata/RHBA-2015-2606.html