-
Notifications
You must be signed in to change notification settings - Fork 213
install/0000_90_cluster-version-operator_02_servicemonitor: Add ClusterReleaseNotAccepted #906
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
install/0000_90_cluster-version-operator_02_servicemonitor: Add ClusterReleaseNotAccepted #906
Conversation
…erReleaseNotAccepted We grew a ReleaseAccepted condition in 7221c93 (pkg/cvo: Separate payload load from payload apply, 2021-10-28, openshift#683), which landed in 4.11 [1] and was backported to 4.10.8 [2]. However, in order to notice a ReleaseAccepted!=True condition, users would need to be checking 'oc adm upgrade' [3] or watching the web-console interface [4]. With this change, we add an alert, so admins can have push-notification to supplement those polling approaches. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1822752#c49 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2064991#c7 [3]: https://bugzilla.redhat.com/show_bug.cgi?id=2065507 [4]: https://issues.redhat.com//browse/OCPBUGS-3069
sounds like a build-cluster thing to me. /retest |
|
/retest |
|
@wking: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
petr-muller
left a comment
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.
LGTM
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: petr-muller, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…om ${{
Fixing a ClusterOperatorDown typo from bbcc33d (pkg/cvo/metrics:
Add 'reason' to cluster_operator_up, 2022-11-21, openshift#868) that I'd
carried forward into ClusterReleaseNotAccepted in 734b9c5
(install/0000_90_cluster-version-operator_02_servicemonitor: Add
ClusterReleaseNotAccepted, 2023-02-23, openshift#906) [1].
[1]: https://issues.redhat.com/browse/OCPBUGS-8079
…om ${{
Fixing a ClusterOperatorDown typo from bbcc33d (pkg/cvo/metrics:
Add 'reason' to cluster_operator_up, 2022-11-21, openshift#868) that I'd
carried forward into ClusterReleaseNotAccepted in 734b9c5
(install/0000_90_cluster-version-operator_02_servicemonitor: Add
ClusterReleaseNotAccepted, 2023-02-23, openshift#906) [1].
[1]: https://issues.redhat.com/browse/OCPBUGS-8079
We grew a
ReleaseAcceptedcondition in 7221c93 (#683), which landed in 4.11 and was backported to 4.10.8. However, in order to notice aReleaseAccepted!=Truecondition, users would need to be checkingoc adm upgradeor watching the web-console interface. With this change, we add an alert, so admins can have push-notification to supplement those polling approaches.