kube-apiserver restarting on bootstrap node

[abhinavdahiya]

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 😇

[sttts]

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

[mfojtik]

@abhinavdahiya or just tag @openshift/sig-master :-)

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.