-
Notifications
You must be signed in to change notification settings - Fork 549
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
Bug 1907792: Change the OperatorUpgradeable condition to Upgradeable #1911
Bug 1907792: Change the OperatorUpgradeable condition to Upgradeable #1911
Conversation
@dinhxuanvu: This pull request references Bugzilla bug 1907792, 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. 3 validation(s) were run on this bug
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. |
/hold |
@dinhxuanvu: 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/test-infra repository. I understand the commands that are listed here. |
7fb25b7
to
83c9ca9
Compare
/hold cancel |
By("This test proves that an operator can upgrade successfully when" + | ||
"OperatorUpgrade condition is set in OperatorCondition CR. Plus, an operator" + | ||
"Upgrade condition rype is set in OperatorCondition CR. Plus, an operator" + |
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.
"Upgrade condition rype is set in OperatorCondition CR. Plus, an operator" + | |
"Upgrade condition type is set in OperatorCondition CR. Plus, an operator" + |
83c9ca9
to
1dc799e
Compare
/lgtm |
The original design intends to use the name "Upgradeable for operator condition. Signed-off-by: Vu Dinh <[email protected]>
1dc799e
to
d6d7fb5
Compare
/retest |
@dinhxuanvu: This pull request references Bugzilla bug 1907792, which is valid. 3 validation(s) were run on this bug
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. |
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 got lucky that we didn't cut a release -- in both upstream and OCP -- when this was an option. If we had and we were being strict about it, I think we would have needed to continue support for "OperatorUpgradeable" until we could formally deprecate it.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dinhxuanvu, njhale 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 |
/lgtm |
@dinhxuanvu: All pull requests linked via external trackers have merged: Bugzilla bug 1907792 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. |
The original design intends to use the name
Upgradeable
only.Signed-off-by: Vu Dinh [email protected]
Description of the change:
Gate operator upgrade on the "Upgradeable" OperatorCondition status type instead of "OperatorUpgradeable".
Motivation for the change:
The OperatorConditions enhancement indicates that OLM gates upgrades on a status condition type of "Upgradeable", not "OperatorUpgradeable".
Reviewer Checklist
/docs