You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
manually docker restart sandbox container, then sandbox container doesn't have IP address, but using "kubectl get pod" find that the pod have IP address 100.100.0.3
[root@node-29:~]$ kubectl get pod --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
k8s-test pod-nginx-pod-0-1-7ccqx 1/1 Running 9 1d 100.100.0.3 10.200.138.226
[root@node-32:~]$ nsenter --net=/proc/50906/ns/net ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
What you expected to happen:
manually docker restart sandbox container, sanbox container should have IP address and pod have IP address
How to reproduce it (as minimally and precisely as possible):
manually docker restart sandbox container,then using "nsenter --net=/proc/<sanndbox_Pid>/ns/net ip addr" check sandbox IP address, using "kubectl get pod" check pod IP address
Anything else we need to know?:
Kubernetes version: v1.10.6
Environment:
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
The text was updated successfully, but these errors were encountered:
/sig node
@kubernetes/sig-node-bugs
kubelet should stop sandbox when it lost ip. @yujuhong@vishh
k8s-ci-robot
added
sig/node
Categorizes an issue or PR as relevant to SIG Node.
and removed
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
labels
Oct 12, 2018
/sig node
@kubernetes/sig-node-bugs kubelet should stop sandbox when it lost ip. @yujuhong@vishh
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
manually docker restart sandbox container, then sandbox container doesn't have IP address, but using "kubectl get pod" find that the pod have IP address 100.100.0.3
[root@node-29:~]$ kubectl get pod --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
k8s-test pod-nginx-pod-0-1-7ccqx 1/1 Running 9 1d 100.100.0.3 10.200.138.226
[root@node-32:~]$ nsenter --net=/proc/50906/ns/net ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
What you expected to happen:
manually docker restart sandbox container, sanbox container should have IP address and pod have IP address
How to reproduce it (as minimally and precisely as possible):
manually docker restart sandbox container,then using "nsenter --net=/proc/<sanndbox_Pid>/ns/net ip addr" check sandbox IP address, using "kubectl get pod" check pod IP address
Anything else we need to know?:
Kubernetes version: v1.10.6
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: