OCPBUGS-115111: skip Watchdog invariant for External topology - #31633
vsolanki12 wants to merge 1 commit into
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
Skipping CI for Draft Pull Request. |
|
@vsolanki12: This pull request references Jira Issue OCPBUGS-115111, which is valid. 3 validation(s) were run on this bug
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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vsolanki12 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 3 remain after this review. Walkthrough
ChangesWatchdog invariant handling
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The Watchdog invariant now permits missing intervals for external-topology jobs while preserving the HA requirement, with tests covering both behaviors. The change is mergeable. 🚥 Pre-merge checks | ✅ 14 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Scheduling tests matching the |
In HyperShift External topology, the monitoring stack runs on the management cluster. Watchdog alert intervals are not captured from the guest cluster's perspective, causing the invariant check to fail with "Watchdog alert not found". Skip this check when topology is External since the alert absence is expected, not a Prometheus outage. Signed-off-by: Vimal Solanki <vsolanki@redhat.com> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3195db2 to
d8a0e42
Compare
|
@coderabbitai resume |
|
|
@coderabbitai resume |
|
|
@coderabbitai full review |
✅ Action performedFull review finished. |
|
/test verify |
|
@vsolanki12: The following test failed, say
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. |
Summary
The
[bz-monitoring][invariant] alert/Watchdog must have no gaps or changesinvariant fails with "Watchdog alert not found" on HyperShift External topology clusters. In External topology, the monitoring stack runs on the management cluster, so Watchdog alert intervals are not captured from the guest cluster's perspective.Skip the Watchdog invariant check when
jobType.Topology == "external"since the alert absence is expected, not a Prometheus outage.Evidence
Conformance test run against HyperShift External topology cluster (4.18.12, aws, External, OVN):
Note: KubePodNotReady alerts all PASSED — the previous implementation fixing KubePodNotReady grace periods was addressing the wrong failure.
Test plan
go test -run TestWatchdogInvariantCheck ./pkg/monitortestlibrary/allowedalerts/)/jira OCPBUGS-115111
Summary by CodeRabbit
Bug Fixes
Tests