OSDOCS-18179-bug-batch-monitoring-4-22 RNs#112583
Merged
mburke5678 merged 1 commit intoJun 2, 2026
Merged
Conversation
|
🤖 Mon Jun 01 20:55:48 - Prow CI generated the docs preview: |
Contributor
Author
|
/label merge-review-needed |
mburke5678
reviewed
Jun 1, 2026
| [id="rn-ocp-release-note-monitoring-fixed-issues_{context}"] | ||
| == Monitoring | ||
|
|
||
| * Before this update, a regression introduced in version {product-title} 4.15 impacted the `AlertingRule` logic, leading to inaccurate processing of alert definitions. This regression caused the system to generate duplicate alerts for the same event, causing it to misinterpret alert definitions and cluttered monitoring dashboards. With this release, the underlying regression has been resolved, restoring the intended behavior and logic to the `AlertingRule` component. (link:https://issues.redhat.com/browse/OCPBUGS-61262[OCPBUGS-61262]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * Before this update, a regression introduced in version {product-title} 4.15 impacted the `AlertingRule` logic, leading to inaccurate processing of alert definitions. This regression caused the system to generate duplicate alerts for the same event, causing it to misinterpret alert definitions and cluttered monitoring dashboards. With this release, the underlying regression has been resolved, restoring the intended behavior and logic to the `AlertingRule` component. (link:https://issues.redhat.com/browse/OCPBUGS-61262[OCPBUGS-61262]) | |
| * Before this update, a regression introduced in {product-title} version 4.15 impacted the `AlertingRule` logic, leading to inaccurate processing of alert definitions. This regression caused the system to generate duplicate alerts for the same event, causing it to misinterpret alert definitions and cluttered monitoring dashboards. With this release, the underlying regression has been resolved, restoring the intended behavior and logic to the `AlertingRule` component. (link:https://issues.redhat.com/browse/OCPBUGS-61262[OCPBUGS-61262]) |
739801f to
96391d2
Compare
mburke5678
reviewed
Jun 1, 2026
|
|
||
| * Before this update, the user workload Prometheus Operator did not validate the `webhookURL` secret reference in the MSTeams receiver configuration of the `AlertmanagerConfig` custom resource. As a consequence, an invalid or missing `webhookURL` secret could be accepted, causing the user workload `Alertmanager` to crash at runtime. With this release, the user workload Prometheus Operator validates the `webhookURL` secret for MSTeams receivers, rejecting invalid configurations before they can affect the `Alertmanager`. (link:https://issues.redhat.com/browse/OCPBUGS-67303[OCPBUGS-67303]) | ||
|
|
||
| * Before this update, the `StatefulSet` controller didn't automatically repair pods when the `StatefulSet` definition got reverted to a valid configuration after a roll-out brought the pods into a broken state. With this release, the Prometheus Operator has been configured to evict unready pods when it detects that there's a more recent revision of the `StatefulSet`. (link:https://issues.redhat.com/browse/OCPBUGS-78976[OCPBUGS-78976]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * Before this update, the `StatefulSet` controller didn't automatically repair pods when the `StatefulSet` definition got reverted to a valid configuration after a roll-out brought the pods into a broken state. With this release, the Prometheus Operator has been configured to evict unready pods when it detects that there's a more recent revision of the `StatefulSet`. (link:https://issues.redhat.com/browse/OCPBUGS-78976[OCPBUGS-78976]) | |
| * Before this update, the `StatefulSet` controller did not automatically repair pods when the `StatefulSet` definition got reverted to a valid configuration after a roll-out brought the pods into a broken state. With this release, the Prometheus Operator has been configured to evict unready pods when it detects that there is a more recent revision of the `StatefulSet` controller. (link:https://issues.redhat.com/browse/OCPBUGS-78976[OCPBUGS-78976]) |
Contributor
|
@wgabor0427 A few comments. Otherwise LGTM. |
96391d2 to
586b5d3
Compare
|
@wgabor0427: 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-sigs/prow repository. I understand the commands that are listed here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version(s):
4.22
Issue:
https://redhat.atlassian.net/browse/OSDOCS-18179
Link to docs preview:
https://112583--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-22-release-notes.html#rn-ocp-release-note-monitoring-fixed-issues_release-notes
QE review:
Additional information: