Bug 1391145

Summary: django-psql-example quick start fails pod readiness
Product: OpenShift Container Platform Reporter: Siva Reddy <schituku>
Component: TemplatesAssignee: Ben Parees <bparees>
Status: CLOSED ERRATA QA Contact: XiuJuan Wang <xiuwang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: aos-bugs, haowang, jokerman, mmccomas, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Python image was overly restrictive about allowing host connections by default Consequence: Readiness probes would fail because they could not connect from localhost. Fix: Change the defaults to allow connections from any host, including localhost. Result: Readiness probe will be able to connect from localhost and the readiness probe will succeed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 12:48:59 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:
Attachments:
Description Flags
The logs for pod showing the readiness probe fail none

Description Siva Reddy 2016-11-02 16:04:35 UTC
Created attachment 1216615 [details]
The logs for pod showing the readiness probe fail

Description of problem:
   The django psql quick start template app doesn't install and fails the readiness probe

Version-Release number of selected component (if applicable):
openshift v3.4.0.18+ada983f
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0

How reproducible:
always

Steps to Reproduce:
1. Create a new project and a new app in it using quick start template
    oc new-project django
    oc new-app --template=django-psql-example
2. Wait for the pods to come up and note the state of the django app pod

Actual results:
    The pod goes into crashloopBackoff after failing the readiness probe

Expected results:
    the pod should come up and should be in running state

Additional info:
    The logs for the pod are attached. It looks like the pod_ip:8080/health is failing.

Comment 1 Ben Parees 2016-11-02 18:21:03 UTC
fix: https://github.com/openshift/origin/pull/11738

Comment 2 Ben Parees 2016-11-02 19:35:54 UTC
new fix PR: https://github.com/openshift/django-ex/pull/66

Comment 3 Wang Haoran 2016-11-03 10:09:25 UTC
verified with:
openshift v3.4.0.19+346a31d
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0

Comment 5 errata-xmlrpc 2017-01-18 12:48:59 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://access.redhat.com/errata/RHBA-2017:0066