-
Notifications
You must be signed in to change notification settings - Fork 216
Bug 1741661: pkg/cvo/metrics: Report cluster-version conditions with reasons #237
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 1741661: pkg/cvo/metrics: Report cluster-version conditions with reasons #237
Conversation
This will allow us to discover upgrade and other failure reasons without having to resort to a must-gather or similar [1]. And also to look at any other version conditions in Telemetry. Stick this in cluster_operator_conditions, since we already have a 'reason' slot there. And ClusterVersion.Status.Conditions is pretty much the same thing as ClusterOperator.Status.Conditions; we'll want to see all of those. I don't see a reason to add a new metric to separate cluster-version operator failures from second-level operator failures; the name should be sufficient for that. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1741645
|
@openshift-cherrypick-robot: This pull request references an invalid Bugzilla bug:
Comment DetailsIn 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-cherrypick-robot: This pull request references an invalid Bugzilla bug:
Comment DetailsIn 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. |
|
/bugzilla refresh |
|
@wking: This pull request references an invalid Bugzilla bug:
Comment DetailsIn 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. |
|
/bugzilla refresh |
|
@wking: This pull request references an invalid Bugzilla bug:
Comment DetailsIn 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. |
|
4.2 bug verified, which should unblock this backport. /bugzilla refresh |
|
@wking: This pull request references Bugzilla bug 1741661, 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. DetailsIn 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, openshift-cherrypick-robot 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 |
|
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged. Bugzilla bug 1741661 has been moved to the MODIFIED state. DetailsIn 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. |
This is an automated cherry-pick of #236
/assign wking