-
Notifications
You must be signed in to change notification settings - Fork 257
OCPBUGS-57354: block upgrade if a CNI migration is in progress #2760
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
base: release-4.16
Are you sure you want to change the base?
OCPBUGS-57354: block upgrade if a CNI migration is in progress #2760
Conversation
@jluhrsen: This pull request references Jira Issue OCPBUGS-57354, 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. |
/jira refresh |
@jluhrsen: This pull request references Jira Issue OCPBUGS-57354, which is invalid:
Comment 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. |
/retest |
2 similar comments
/retest |
/retest |
/jira refresh |
@jluhrsen: This pull request references Jira Issue OCPBUGS-57354, which is invalid:
Comment 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. |
@pliurh , PTAL |
/jira refresh |
@jluhrsen: This pull request references Jira Issue OCPBUGS-57354, which is invalid:
Comment 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. |
/jira refresh |
@jluhrsen: This pull request references Jira Issue OCPBUGS-57354, which is invalid:
Comment 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. |
/jira refresh |
@jluhrsen: This pull request references Jira Issue OCPBUGS-57354, which is valid. 7 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 openshift-eng/jira-lifecycle-plugin repository. |
) | ||
} | ||
|
||
if oc.Spec.DefaultNetwork.Type == operv1.NetworkTypeOpenShiftSDN && migrationInProgress { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we shall remove the check oc.Spec.DefaultNetwork.Type == operv1.NetworkTypeOpenShiftSDN
. Upgrade shall be blocked when migrationInProgress
is true.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
8421b98
to
cb8a940
Compare
thanks for the review @pliurh . I think I addressed both of your comments. PTAL |
/retest |
1 similar comment
/retest |
/retest |
/retest-required |
2 similar comments
/retest-required |
/retest-required |
@kyrtapz I think we are good here |
/retest-required |
/approve |
/verified by ci |
@jluhrsen: This PR has been marked as verified by 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. |
/approve |
/label backport-risk-assessed |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jluhrsen, pliurh 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 |
@jluhrsen: The following tests failed, say
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. |
@pliurh the windows job is in horrible state. can you the only place it runs is in CNO so I doubt anyone even knows or cares about it. |
No description provided.