-
Notifications
You must be signed in to change notification settings - Fork 157
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
kube-apiserver restarting on bootstrap node #175
Comments
@abhinavdahiya cc'ing me and @mfojtik would make sense as we mostly did the bootstrapping work of the control plane ;-) Out of curiosity: how do you know that the upper CI run is another example of the issue described in openshift/installer#964. Background: we often struggle to analyse bootstrap issues in CI because there are no logs of the static pods. I opened openshift/release#2064 ages ago, but didn't get much review attention. |
@abhinavdahiya or just tag @openshift/sig-master :-) |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. 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 kubernetes/test-infra repository. |
kube-apiserver seems to be restarting on the bootstrap node causing the installer to fail.
one example is openshift/installer#964
another https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/251/pull-ci-openshift-machine-config-operator-master-e2e-aws/770/
This causes the master nodes to never come up.
/cc @deads2k
^^ not sure who else to cc 😇
The text was updated successfully, but these errors were encountered: