-
Notifications
You must be signed in to change notification settings - Fork 231
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
[WIP] OCPBUGS-45924: for PodSucceeded static pod should always be pending #1911
base: master
Are you sure you want to change the base?
Conversation
@tkashem: This pull request references Jira Issue OCPBUGS-45924, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tkashem The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
dff6593
to
24c1781
Compare
the following conditions: - a) pod.Status.Phase == PodSucceeded - b) pod.Status.Condition[type==corev1.PodReady]: status == corev1.ConditionTrue if kubelet does not update the Pod status (a and b) atomically then there is a gap between when 1) pod.Status.Phase is set to PodSucceeded and 2) the PodReady condition is updated to False if a abd b are true then we may signal that "static pod is ready" on the designated node, which may cause the installer controller to create a new installer pod on a different node if a is true, this alone can be used to say that "static pod is pending" on the designated node.
proof PR: openshift/cluster-etcd-operator#1385 |
/cc @dgrisonnet @benluddy (I am probably missing something obvious) |
@tkashem: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
the following conditions:
if kubelet does not update the Pod status (a and b) atomically then there is a gap between when 1) pod.Status.Phase is set to PodSucceeded and 2) the PodReady condition is updated to False
if a and b are true then we may signal that "static pod is ready" on the designated node, which may cause the installer controller to create a new installer pod on a different node
if a is true, this alone can be used to say that "static pod is pending" on the designated node.