Bug 1507800
Summary: | Node service cannot automatically start after node reboot while enabling system containers | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
Component: | Installer | Assignee: | Michael Gugino <mgugino> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Qin Ping <piqin> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.7.0 | CC: | aos-bugs, jokerman, mmccomas, vlaad |
Target Milestone: | --- | ||
Target Release: | 3.9.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-09-10 16:29:58 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
Qin Ping
2017-10-31 08:09:57 UTC
I'm not sure how this bug is possible. This was solved quite some time ago: https://github.com/openshift/openshift-ansible/pull/4131 This problem still existed on OCP version: v3.9.0-0.23.0 I have figured out what the root of this issue is. 1) We install the origin-node.service / atomic-openshift-node.service unit file before installing the system container. 2) System container for node is installed, this causes atomic to overwrite the service unit we created. 3) Service starts correctly after installing the system container, but since the 'docker' target is not available on crio, the unit is never linked to a 'target.wants' Need to consult with syscontainer team to figure out best way forward. Should we not install node as a system container so we can create our own unit file? Even if we fix the ordering in asnible, it is likely that if the user were to update the container, the unit file would be overwritten again. Perhaps there is a way to instruct atomic to not create the unit file? Looks like we can indeed template the service unit files. I have submitted a PR against origin here: https://github.com/openshift/origin/pull/18314 Should be fixed in v3.9.0-0.38.0 verified in v3.9.0-0.38.0 |