Bug 1103138
Summary: | openshift-node-web-proxy died after oo-install | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> | |
Component: | Containers | Assignee: | Jason DeTiberus <jdetiber> | |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 2.1.0 | CC: | adellape, bleanhar, erich, jdetiber, jokerman, libra-onpremise-devel, mmccomas | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openshift-origin-node-proxy-1.22.3.3-1.el6op | Doc Type: | Bug Fix | |
Doc Text: |
Starting the openshift-node-web-proxy service under certain conditions, in particular when using the oo-install installation utility, caused the service to be immediately killed when the user ended their session. This bug fix corrects this issue and the service now starts normally, including when using the installation utility.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1105324 (view as bug list) | Environment: | ||
Last Closed: | 2014-06-23 07:41:18 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: | 1105324 | |||
Bug Blocks: |
Description
Anping Li
2014-05-30 11:12:56 UTC
I know Jason had observed this and thought he had fixed it. Jason, comments? A solution was still not found at this point... The problem is that when running openshift.sh from oo-install, it is being run over ssh with a pty, which causes the supervisor process that is spawned from the openshift-node-web-proxy init script to be killed after the pty is closed. I suppose one workaround would be to go ahead and restart the service using an ssh connection without pty after the openshift.sh configure step is run, however, we should probably solve this upstrem with openshift-node-web-proxy. Upstream PR: https://github.com/openshift/origin-server/pull/5482 Enterprise PR: https://github.com/openshift/enterprise-server/pull/293 Can't start openshift-node-web-proxy after oo-install. However 'ssh root.15.XX service openshift-node-web-proxy restart' works. 1) oo-install failed to start service =system_u:object_r:locale_t:s0 tclass=file OpenShift: oo-diagnostics output - OpenShift: oo-diagnostics output - Note that SELinux violations are not always logged in the audit log. OpenShift: oo-diagnostics output - OpenShift: oo-diagnostics output - FAIL: test_services_enabled OpenShift: oo-diagnostics output - The following service(s) are not currently started: OpenShift: oo-diagnostics output - openshift-node-web-proxy OpenShift: oo-diagnostics output - These services are required for OpenShift functionality. 2) service can be started by ssh command. [hanli1@broker ~]$ sh test.sh ssh root.15.89 service openshift-node-web-proxy restart [ OK ] node-web-proxy: [FAILED] Starting node-web-proxy: [ OK ] ssh root.15.89 service openshift-node-web-proxy status web-proxy (pid 2110) is running... ssh root.15.89 service openshift-node-web-proxy restart [ OK ] node-web-proxy: [ OK ] Starting node-web-proxy: [ OK ] ssh root.15.89 service openshift-node-web-proxy status web-proxy (pid 2172) is running.. Remote ssh root@host oo_install_configure_10.66.XX.XX.sh worked。 only oo-installcan't start that service. https://github.com/openshift/enterprise-server/pull/301 Waiting for upstream PR to be merged. Just added the [merge] tag so moving to modified. Verified and pass on puddle-2-1-2014-06-18. 1)After oo-install, service openshift-node-web-proxy started 2)After 'sh -t root@XXX'sudo bash -c "service openshift-node-web-proxy restart; sleep 2;"', service openshift-node-web-proxy started 3)'ssh -t root.78.219 service openshift-node-web-proxy restart' works 3)service openshift-node-web-proxy start/restart works in local 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. http://rhn.redhat.com/errata/RHBA-2014-0781.html |