Bug 1507257
Summary: | Messages flooded with messages like StopPodSandbox $SHA from runtime service failed: rpc error: code = 2 desc = NetworkPlugin cni failed to teardown pod <pod-name> network: CNI failed to retrieve network namespace path: Error: No such container: $SHA | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Alexis Solanas <asolanas> |
Component: | Networking | Assignee: | Rajat Chopra <rchopra> |
Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.6.1 | CC: | ansverma, aos-bugs, bbennett, eparis, javier.ramirez, jokerman, mmccomas, rchopra, stwalter |
Target Milestone: | --- | ||
Target Release: | 3.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Network namespace path is nil when using hostnetwork.
Consequence:
The teardown in such a case gives out error messages.
Fix:
Upstream fix - do not let CNI manage containers with hostnetwork=true.
Result:
No error messages
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-28 22:20:01 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
Alexis Solanas
2017-10-28 23:56:29 UTC
https://github.com/openshift/origin/pull/17097 This should fix the issue, or we need a chain of backports from upstream. (In reply to Rajat Chopra from comment #1) > https://github.com/openshift/origin/pull/17097 > This should fix the issue, or we need a chain of backports from upstream. Thanks Rajat, any idea if there is a workaround we could apply now? Javier, unfortunately no workaround there. Tested on OCP build v3.7.0-0.190.0 Issue has been fixed. There will be no error messages in the atomic-openshift-node log when deleting the docker container which is created as hostnetwork enabled pod. With the same steps, the error messages appear in the node log as below on build prior 3.7.0-0.190.0. Nov 03 03:51:14 qe-bmeng.interna atomic-openshift-node[23194]: W1103 03:51:14.541341 23194 cni.go:258] CNI failed to retrieve network namespace path: Error: No such container: c5e769d5f72ef91c44e50f9eb6a73a74ce92372e5a705a3edf941a38bec60454 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 |