Skip to content

OSDOCS-18179-bug-batch-monitoring-4-22 RNs#112583

Merged
mburke5678 merged 1 commit into
openshift:enterprise-4.22from
wgabor0427:OSDOCS-18179-bug-batch-monitoring-4-22
Jun 2, 2026
Merged

OSDOCS-18179-bug-batch-monitoring-4-22 RNs#112583
mburke5678 merged 1 commit into
openshift:enterprise-4.22from
wgabor0427:OSDOCS-18179-bug-batch-monitoring-4-22

Conversation

@wgabor0427
Copy link
Copy Markdown
Contributor

@wgabor0427 wgabor0427 commented Jun 1, 2026

@openshift-ci openshift-ci Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 1, 2026
@ocpdocs-previewbot
Copy link
Copy Markdown

ocpdocs-previewbot commented Jun 1, 2026

🤖 Mon Jun 01 20:55:48 - Prow CI generated the docs preview:

https://112583--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-22-release-notes.html

@wgabor0427
Copy link
Copy Markdown
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci Bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Jun 1, 2026
@mburke5678 mburke5678 added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label 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])
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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])

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@wgabor0427 wgabor0427 force-pushed the OSDOCS-18179-bug-batch-monitoring-4-22 branch from 739801f to 96391d2 Compare June 1, 2026 20:36

* 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])
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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])

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@mburke5678
Copy link
Copy Markdown
Contributor

@wgabor0427 A few comments. Otherwise LGTM.

@wgabor0427 wgabor0427 force-pushed the OSDOCS-18179-bug-batch-monitoring-4-22 branch from 96391d2 to 586b5d3 Compare June 1, 2026 20:45
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Jun 1, 2026

@wgabor0427: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@mburke5678 mburke5678 merged commit 04995d4 into openshift:enterprise-4.22 Jun 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants