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

Kubelet should keep the original PodStatus.Host when posting the status #6124

Closed
yujuhong opened this issue Mar 27, 2015 · 4 comments
Closed
Labels
area/kubelet priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@yujuhong
Copy link
Contributor

I am seeing pod status update failures due to empty Host field. This prevents the pod status from being updated in some cases. Kubelet should always keep the original host.

@yujuhong yujuhong added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/kubelet sig/node Categorizes an issue or PR as relevant to SIG Node. labels Mar 27, 2015
@yujuhong
Copy link
Contributor Author

In the case I saw, all containers of that pod has exited with 1, and the restart policy was never. There seems to be two issues.

  1. kubelet queried docker and couldn't find the containers: "No pod infra container exists for this pod"
  2. kubelet decided to return a pending status with no host set

(2) triggered a status update which attempted to clear the host field. This should not be allowed.

@yujuhong
Copy link
Contributor Author

#6127 is a quick fix for 2. There is a broader question about whether "pending" is the best status to return in this case.

Whey kubelet won't report failed (1) still needs more investigation.

@bgrant0607
Copy link
Member

I'd be happy if PodStatus.Host were eliminated from v1beta3 and just populated from PodSpec in v1beta1/2.

@yujuhong
Copy link
Contributor Author

@bgrant0607, yes, I thought someone was working on that. Filed a issue just in case #6165.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubelet priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

2 participants