Symlink network namespace failed
Bug #1712273 reported by
Pengfei Ni
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
stackube |
Fix Released
|
High
|
Pengfei Ni |
Bug Description
When restarting a pod, sometimes the pod failed to start because of failure symlink network namespace, e.g.
Error while adding to cni network: error of symlink "/var/run/
In this case, the original netns has already been removed by container runtime, but the symlink hasn't been removed. There are two problems here:
1. cni plugin should clean up the symlink on cases of failed operations in cmdAdd
2. the podName is used in symlink, but it may be conflict in different kubernetes namespaces, we should concat kubernetes namespace with podName.
tags: | added: cni |
tags: | added: networking |
Changed in stackube: | |
importance: | Undecided → High |
assignee: | nobody → Pengfei Ni (feiskyer) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/496173
Review: https:/