-
Notifications
You must be signed in to change notification settings - Fork 213
Bug 1926310: install/0000_90_cluster-version-operator_02_servicemonitor.yaml: adjust "CannotRetrieveUpdates" to "warning" #509
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
Conversation
…st "CannotRetrieveUpdates" to "warning"
|
/assign @wking |
|
If CVO can't reach OSUS this would only impair cluster upgrades. Similar to other alerts - like /approve |
|
CVO not able to reach OpenShift update service does not effect cluster availability. Also we do not need to wake up someone middle of the night to fix this. Hence I am in favor of making this a |
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
/hold For giving @wking sometime to put his views
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LalatenduMohanty, RiRa12621, vrutkovs 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 |
|
@RiRa12621 Which branch are you looking to have this backported to? |
|
4.6 would be good. |
|
/hold cancel |
|
/retitle Bug 1926310: install/0000_90_cluster-version-operator_02_servicemonitor.yaml: adjust "CannotRetrieveUpdates" to "warning" |
|
@RiRa12621: This pull request references Bugzilla bug 1926310, which is invalid:
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 |
|
@sdodson: This pull request references Bugzilla bug 1926310, 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
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. |
|
/refresh |
|
/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. |
|
@RiRa12621: All pull requests linked via external trackers have merged: Bugzilla bug 1926310 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. |
|
/cherry-pick release-4.7 |
|
@sdodson: new pull request created: #516 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. |
SRE-P has commited to feed findings and changes in regards to alerts back to upstream, this change is a follow up to https://issues.redhat.com/browse/OSD-6327
We are obeying the following standards for alert levels and recommend every component team to do so to:
reference
This therefore is a
warninglevel alert. No one should be paged for it in the middle of the night but we still want cluster owners to eventually fix this./cc @jewzaam @wking @cblecker