Bug 2038481: Flake failed sandboxes from bug in new guard pods #26776
Conversation
more info in https://bugzilla.redhat.com/show_bug.cgi?id=2038481 essentially, two new guard pods are being started in 4.10+ and are incorrectly being restarted on a cordoned node and when the node is rebooted those pods fail to set up sandboxes right away before the underlying network config file is present. This can be reverted when the PR to fix this is merged: openshift/library-go#1287 Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
openshift-ci
bot
added
the
bugzilla/severity-high
|
@deads2k: This pull request references Bugzilla bug 2038481, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
openshift-ci
bot
added
the
bugzilla/valid-bug
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k 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 |
openshift-ci
bot
added
the
approved
|
built, tested green before. |
|
@deads2k: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with Bugzilla bug 2038481 has not been moved to the MODIFIED state. 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. |
more info in https://bugzilla.redhat.com/show_bug.cgi?id=2038481
essentially, two new guard pods are being started in 4.10+ and
are incorrectly being restarted on a cordoned node and when the
node is rebooted those pods fail to set up sandboxes right away
before the underlying network config file is present. This can
be reverted when the PR to fix this is merged:
openshift/library-go#1287
Signed-off-by: Jamo Luhrsen jluhrsen@gmail.com
#26763 with gofmt goodness