Bug 1760103: Adjust SDN setup so AlreadySetUp check will fail on a half-set-up node #52
Conversation
|
@danwinship: This pull request references Bugzilla bug 1760103, which is valid. The bug has been moved to the POST state. 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 kubernetes/test-infra repository. |
openshift-ci-robot
added
bugzilla/valid-bug
|
/cc @squeed |
danwinship
force-pushed
the
sdn-setup-ordering
branch
from
25ee4e2
to
fcfb8f7
Compare
openshift-ci-robot
added
size/M
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, dcbw 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 |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@danwinship: All pull requests linked via external trackers have merged. Bugzilla bug 1760103 has 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. |
|
/cherrypick release-4.2 |
|
@juanluisvaladas: new pull request created: #87 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. |
See details at https://bugzilla.redhat.com/show_bug.cgi?id=1760103#c12, but the basic idea is that if SDN gets killed partway through SDN setup, we want to make sure the next SDN pod retries setup from the top rather than mistakenly accepting the half-set-up network.