Red Hat Bugzilla – Bug 1281671
[rhscl/postgresql-94-rhel7] Postgresql pod is CrashLoopBackOff if using persistent storage
Last modified: 2015-12-09 10:17:31 EST
Is this something we have a fix for or there is no fix yet?
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.
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?
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?
So this is waiting for the image to be updated?
Note also that there were some permission issues resolved by fixing NFS settings here:
which should be applicable to any verification attempt.
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.