Bug 1156613

Summary: routing-daemon.conf has NGINX_PLUS settings on by default, they should commented out
Product: OpenShift Container Platform Reporter: chris alfonso <calfonso>
Component: NodeAssignee: chris alfonso <calfonso>
Status: CLOSED ERRATA QA Contact: libra bugs <libra-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.2.0CC: bleanhar, hbrock, jokerman, libra-onpremise-devel, mmccomas, pruan, xiama
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-openshift-origin-routing-daemon-0.17.1.3-1.el6op Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-03 19:55:47 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:

Description chris alfonso 2014-10-24 19:07:09 UTC 
Description of problem:
The /etc/openshift/routing-daemon.conf has the NGINX_PLUS and related health checking settings on by default, they should be commented out because this is not the typical installation setup. The typical installation setup will be NGINX from the Software Collections Library.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 5 Ma xiaoqiang 2014-10-27 02:07:51 UTC 
Check on puddle [2.2/2014-10-25.1]

Install the package, check the configuration
#vim /etc/openshift/routing-daemon.conf
<--snip-->
NGINX_CONFDIR=/opt/rh/nginx14/root/etc/nginx/conf.d
NGINX_SERVICE=nginx14-nginx
#NGINX_PLUS=true
#NGINX_PLUS_HEALTH_CHECK_INTERVAL=2s
#NGINX_PLUS_HEALTH_CHECK_FAILS=1
#NGINX_PLUS_HEALTH_CHECK_PASSES=5
#NGINX_PLUS_HEALTH_CHECK_URI=/
#NGINX_PLUS_HEALTH_CHECK_MATCH_STATUS=200
#NGINX_PLUS_HEALTH_CHECK_SHARED_MEMORY=64k
Comment 7 errata-xmlrpc 2014-11-03 19:55:47 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/RHSA-2014-1796.html