Skip to content

[release-5.0] OCPBUGS-113760: Allow KubeDaemonSetMisScheduled alert on external platform clusters - #31558

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-5.0from
redhat-chai-bot:cherry-pick-31556-release-5.0
Aug 26, 2026
Merged

[release-5.0] OCPBUGS-113760: Allow KubeDaemonSetMisScheduled alert on external platform clusters#31558
openshift-merge-bot[bot] merged 1 commit into
openshift:release-5.0from
redhat-chai-bot:cherry-pick-31556-release-5.0

Conversation

@redhat-chai-bot

Copy link
Copy Markdown
Contributor

Cherry-pick of #31556 to release-5.0 (manual — cherry-pick bot failed due to merge conflict).

The release-5.0 branch uses []string + append for allowedAlertNames while main uses sets.Set + Insert. This cherry-pick adapts the fix to use the release-5.0 syntax.

Changes

  • test/extended/util/framework.go: Added IsExternalPlatformCluster() helper that checks infrastructure.Status.PlatformStatus.Type == configv1.ExternalPlatformType
  • test/extended/prometheus/prometheus.go: Extended the KubeDaemonSetMisScheduled alert allowance to include External platform clusters alongside managed-service clusters

Jira


AI-generated. Review for accuracy.

@mtulio requested in Slack thread

…m clusters

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@openshift-ci openshift-ci Bot added the ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review label Aug 25, 2026
@coderabbitai

coderabbitai Bot commented Aug 25, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: a9473aa0-2704-4d3a-a014-58dd6547acb0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from deads2k and rexagod August 25, 2026 15:12
@mtulio

mtulio commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-release-main-nightly-5.0-opct-platform-external-aws

@openshift-ci

openshift-ci Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

@mtulio: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-opct-platform-external-aws

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f79bba40-a097-11f1-8e43-0938f582902d-0

@mtulio

mtulio commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

/retitle [release-5.0] OCPBUGS-113760: Allow KubeDaemonSetMisScheduled alert on external platform clusters

@openshift-ci openshift-ci Bot changed the title Bug 113760: Allow KubeDaemonSetMisScheduled alert on external platform clusters [release-5.0] OCPBUGS-113760: Allow KubeDaemonSetMisScheduled alert on external platform clusters Aug 25, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 25, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-113760, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-113760 to depend on a bug targeting a version in 5.1.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Cherry-pick of #31556 to release-5.0 (manual — cherry-pick bot failed due to merge conflict).

The release-5.0 branch uses []string + append for allowedAlertNames while main uses sets.Set + Insert. This cherry-pick adapts the fix to use the release-5.0 syntax.

Changes

  • test/extended/util/framework.go: Added IsExternalPlatformCluster() helper that checks infrastructure.Status.PlatformStatus.Type == configv1.ExternalPlatformType
  • test/extended/prometheus/prometheus.go: Extended the KubeDaemonSetMisScheduled alert allowance to include External platform clusters alongside managed-service clusters

Jira


AI-generated. Review for accuracy.

@mtulio requested in Slack thread

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.

@mtulio

mtulio commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 25, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mtulio: This pull request references Jira Issue OCPBUGS-113760, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-112283 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-112283 targets the "5.1.0" version, which is one of the valid target versions: 5.1.0
  • bug has dependents
Details

In response to this:

/jira refresh

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.

@mtulio

mtulio commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

/ok-to-test

@openshift-ci openshift-ci Bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Aug 25, 2026
@mtulio

mtulio commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@mtulio

mtulio commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Waiting for payload job.
/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 25, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@mtulio

mtulio commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-release-main-nightly-5.0-opct-platform-external-aws

@openshift-ci

openshift-ci Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

@mtulio: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-opct-platform-external-aws

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e972ab40-a0bf-11f1-8628-934571265154-0

@mtulio

mtulio commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

previous job is getting quota issues, scheduling a new one.

@mtulio

mtulio commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-release-main-nightly-5.0-opct-platform-external-aws

@openshift-ci

openshift-ci Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

@mtulio: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-opct-platform-external-aws

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5975b660-a0fe-11f1-95b7-826c75d0605c-0

@mtulio

mtulio commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/lgtm
/approve
/assign @neisw
/hold cancel
/verified by CI payload job https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-31558-nightly-5.0-opct-platform-external-aws/2092454375208259584. The test [sig-instrumentation] Prometheus [apigroup:image.openshift.io] when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early][apigroup:config.openshift.io] [Suite:openshift/conformance/parallel] is still failing but not caused by KubeDaemonSetMisScheduled. We are going to file a bug reporting KubeDaemonSetRolloutStuck as well.

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 26, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 26, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mtulio: This PR has been marked as verified by CI payload job https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-31558-nightly-5.0-opct-platform-external-aws/2092454375208259584. The test [sig-instrumentation] Prometheus [apigroup:image.openshift.io] when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early][apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]is still failing but not caused byKubeDaemonSetMisScheduled. We are going to file a bug reporting KubeDaemonSetRolloutStuck as well..

Details

In response to this:

/lgtm
/approve
/assign @neisw
/hold cancel
/verified by CI payload job https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-31558-nightly-5.0-opct-platform-external-aws/2092454375208259584. The test [sig-instrumentation] Prometheus [apigroup:image.openshift.io] when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early][apigroup:config.openshift.io] [Suite:openshift/conformance/parallel] is still failing but not caused by KubeDaemonSetMisScheduled. We are going to file a bug reporting KubeDaemonSetRolloutStuck as well.

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.

@mtulio

mtulio commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/label backport-risk-assessed,

@openshift-ci

openshift-ci Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

@mtulio: The label(s) /label backport-risk-assessed, cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, rebase/manual, cluster-config-api-changed, run-integration-tests, verified, ready-for-human-review, reliability, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, ci/severity-critical, jira/skip-dependent-bug-check, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label backport-risk-assessed,

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.

@mtulio

mtulio commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/label backport-risk-assessed

@openshift-ci

openshift-ci Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

@mtulio: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-release-oversight, openshift-staff-engineers, openshift-sustaining-engineers

Details

In response to this:

/label backport-risk-assessed

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.

@neisw

neisw commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/approve
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 26, 2026
@openshift-ci

openshift-ci Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mtulio, neisw, redhat-chai-bot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 26, 2026
@neisw

neisw commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

/override ci/prow/e2e-aws-ovn-microshift
/override ci/prow/e2e-aws-ovn-microshift-serial

@openshift-ci

openshift-ci Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-aws-ovn-microshift, ci/prow/e2e-aws-ovn-microshift-serial

Details

In response to this:

/override ci/prow/e2e-aws-ovn-microshift
/override ci/prow/e2e-aws-ovn-microshift-serial

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.

@openshift-ci

openshift-ci Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

@redhat-chai-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-microshift 01e744d link true /test e2e-aws-ovn-microshift
ci/prow/e2e-aws-ovn-microshift-serial 01e744d link true /test e2e-aws-ovn-microshift-serial

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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 00481d0 into openshift:release-5.0 Aug 26, 2026
20 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@redhat-chai-bot: Jira Issue Verification Checks: Jira Issue OCPBUGS-113760
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-113760 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Cherry-pick of #31556 to release-5.0 (manual — cherry-pick bot failed due to merge conflict).

The release-5.0 branch uses []string + append for allowedAlertNames while main uses sets.Set + Insert. This cherry-pick adapts the fix to use the release-5.0 syntax.

Changes

  • test/extended/util/framework.go: Added IsExternalPlatformCluster() helper that checks infrastructure.Status.PlatformStatus.Type == configv1.ExternalPlatformType
  • test/extended/prometheus/prometheus.go: Extended the KubeDaemonSetMisScheduled alert allowance to include External platform clusters alongside managed-service clusters

Jira


AI-generated. Review for accuracy.

@mtulio requested in Slack thread

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.