Bug 1466636
| Summary: | node can not be started for Unit kubepods-burstable.slice already exists | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> |
| Component: | Node | Assignee: | Ryan Phillips <rphillips> |
| Node sub component: | Kubelet | QA Contact: | Sunil Choudhary <schoudha> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | unspecified | CC: | aos-bugs, decarr, eparis, jokerman, mmccomas, sdodson, wking, xtian |
| Version: | 3.6.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-11-28 21:59:33 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
Anping Li
2017-06-30 06:26:43 UTC
As mentioned in https://github.com/kubernetes/kubernetes/issues/43856. the issue can be solved by stopping kubepod service for i in $(systemctl list-unit-files --no-legend --no-pager -l | grep --color=never -o .*.slice | grep kubepod);do systemctl status $i; systemctl stop $i;done Derek, Can I get your assessment on how we should fix this if this needs to be addressed by the installer? we need to bump runc to get https://github.com/opencontainers/runc/pull/1124 runc PR: https://github.com/opencontainers/runc/pull/1124 kube issue: https://github.com/kubernetes/kubernetes/issues/43856 kube master fix (bump runc): https://github.com/kubernetes/kubernetes/pull/44940 kube 1.6 fix (bump runc): https://github.com/kubernetes/kubernetes/pull/48117 I'll prepare a PR to bump runc for origin. No such issue when upgrade to atomic-openshift-3.6.132. 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/RHSA-2017:3188 Similar symptoms are back in 4.8. I've opened bug 1965545 to track (mentioning here to route folks who happen to stumble across this bug while searching for the already-exists log message). |