Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sandbox container should have IP address when manually docker restart sandbox container #69723

Closed
mysunshine92 opened this issue Oct 12, 2018 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@mysunshine92
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

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:
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 12, 2018
@Pingan2017
Copy link
Member

Pingan2017 commented Oct 12, 2018

/sig node
@kubernetes/sig-node-bugs
kubelet should stop sandbox when it lost ip.
@yujuhong @vishh

@k8s-ci-robot 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
@k8s-ci-robot
Copy link
Contributor

@Pingan2017: Reiterating the mentions to trigger a notification:
@kubernetes/sig-node-bugs

In response to this:

/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.

@warmchang
Copy link
Contributor

Hi @mysunshine92 , Do you mind if I close this issue? It is repeated with #69925, and we can track this in #69925. Thanks!

@mysunshine92
Copy link
Contributor Author

@warmchang OK,I close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

4 participants