Skip to content

Conversation

@machine424
Copy link
Contributor

@machine424 machine424 commented Jul 8, 2025

@openshift-ci openshift-ci bot requested review from deads2k and p0lyn0mial July 8, 2025 21:14
@machine424 machine424 changed the title register CMO tests extension WIP: : register CMO tests extension Jul 8, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 8, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

@machine424: This PR was included in a payload test run from openshift/cluster-monitoring-operator#2616
trigger 11 job(s) of type blocking for the nightly release of OCP 4.20

  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips
  • periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.20-fips-payload-scan
  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-master-nightly-4.20-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8fd87fe0-5c43-11f0-8b54-23d24fc88994-0

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

@machine424: This PR was included in a payload test run from openshift/cluster-monitoring-operator#2616
trigger 4 job(s) of type blocking for the ci release of OCP 4.20

  • periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/940efda0-5c43-11f0-9436-fd13a7987086-0

@machine424
Copy link
Contributor Author

/testwith openshift/origin/main/e2e-aws-ovn-microshift openshift/cluster-monitoring-operator#2616

@machine424
Copy link
Contributor Author

/testwith openshift/origin/main/e2e-metal-ipi-ovn openshift/cluster-monitoring-operator#2616
/testwith openshift/origin/main/e2e-gcp-ovn openshift/cluster-monitoring-operator#2616
/testwith openshift/origin/main/e2e-azure openshift/cluster-monitoring-operator#2616

@machine424
Copy link
Contributor Author

/skip

@machine424
Copy link
Contributor Author

machine424 commented Jul 10, 2025

/retitle MON-4288: register CMO tests extension

@openshift-ci openshift-ci bot changed the title WIP: : register CMO tests extension MON-4288: register CMO tests extension Jul 10, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 10, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 10, 2025

@machine424: This pull request references MON-4288 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

CMO side setup: openshift/cluster-monitoring-operator#2616

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.

@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 10, 2025
@machine424
Copy link
Contributor Author

/skip
/hold
openshift/cluster-monitoring-operator#2616 should go in first

@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 Jul 10, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 11, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 16, 2025
@machine424
Copy link
Contributor Author

@smg247
Copy link
Member

smg247 commented Jul 16, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 16, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: machine424, smg247

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 Jul 16, 2025
@machine424
Copy link
Contributor Author

/skip ci/prow/e2e-agnostic-ovn-cmd
/skip ci/prow/e2e-aws
/skip ci/prow/e2e-aws-disruptive
/skip ci/prow/e2e-aws-ovn
/skip ci/prow/e2e-aws-ovn-cgroupsv2
/skip ci/prow/e2e-aws-ovn-edge-zones
/skip ci/prow/e2e-aws-ovn-etcd-scaling
/skip ci/prow/e2e-aws-ovn-fips
/skip ci/prow/e2e-aws-ovn-kube-apiserver-rollout
/skip ci/prow/e2e-aws-ovn-microshift
/skip ci/prow/e2e-aws-ovn-microshift-serial
/skip ci/prow/e2e-aws-ovn-serial-2of2
/skip ci/prow/e2e-aws-ovn-serial-publicnet-1of2
/skip ci/prow/e2e-aws-ovn-serial-publicnet-2of2
/skip ci/prow/e2e-aws-ovn-single-node
/skip ci/prow/e2e-aws-ovn-single-node-serial
/skip ci/prow/e2e-aws-ovn-single-node-upgrade
/skip ci/prow/e2e-aws-proxy
/skip ci/prow/e2e-azure
/skip ci/prow/e2e-azure-ovn-etcd-scaling
/skip ci/prow/e2e-azure-ovn-upgrade
/skip ci/prow/e2e-gcp-csi
/skip ci/prow/e2e-gcp-disruptive
/skip ci/prow/e2e-gcp-fips-serial-1of2
/skip ci/prow/e2e-gcp-fips-serial-2of2
/skip ci/prow/e2e-gcp-ovn
/skip ci/prow/e2e-gcp-ovn-etcd-scaling
/skip ci/prow/e2e-hypershift-conformance
/skip ci/prow/e2e-metal-ipi-ovn
/skip ci/prow/e2e-metal-ipi-ovn-dualstack
/skip ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway
/skip ci/prow/e2e-metal-ipi-ovn-ipv6
/skip ci/prow/e2e-metal-ipi-serial-2of2
/skip ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2
/skip ci/prow/e2e-metal-ipi-virtualmedia
/skip ci/prow/e2e-openstack-ovn
/skip ci/prow/e2e-openstack-serial
/skip ci/prow/e2e-vsphere-ovn
/skip ci/prow/e2e-vsphere-ovn-dualstack-primaryv6
/skip ci/prow/e2e-vsphere-ovn-etcd-scaling
/skip ci/prow/e2e-vsphere-ovn-upi
/skip ci/prow/okd-e2e-gcp
/skip ci/prow/okd-scos-e2e-aws-ovn

@machine424
Copy link
Contributor Author

/unhold

@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 Jul 17, 2025
@machine424
Copy link
Contributor Author

/skip

1 similar comment
@machine424
Copy link
Contributor Author

/skip

@machine424
Copy link
Contributor Author

/skip ci/prow/e2e-aws-ovn-serial-2of2

@smg247
Copy link
Member

smg247 commented Jul 17, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD aecf7c8 and 2 for PR HEAD 2c23c04 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 17, 2025

@machine424: 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-serial-publicnet-1of2 2c23c04 link false /test e2e-aws-ovn-serial-publicnet-1of2
ci/prow/e2e-hypershift-conformance 2c23c04 link false /test e2e-hypershift-conformance
ci/prow/e2e-gcp-fips-serial-1of2 2c23c04 link false /test e2e-gcp-fips-serial-1of2
ci/prow/e2e-agnostic-ovn-cmd 2c23c04 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-gcp-disruptive 2c23c04 link false /test e2e-gcp-disruptive
ci/prow/e2e-aws-ovn-single-node-upgrade 2c23c04 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-ovn-dualstack 2c23c04 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-ovn 2c23c04 link false /test e2e-aws-ovn
ci/prow/e2e-metal-ipi-ovn 2c23c04 link false /test e2e-metal-ipi-ovn
ci/prow/e2e-gcp-fips-serial-2of2 2c23c04 link false /test e2e-gcp-fips-serial-2of2
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway 2c23c04 link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-aws-ovn-etcd-scaling 2c23c04 link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-metal-ipi-serial-2of2 2c23c04 link false /test e2e-metal-ipi-serial-2of2
ci/prow/e2e-gcp-csi 2c23c04 link false /test e2e-gcp-csi
ci/prow/e2e-openstack-serial 2c23c04 link false /test e2e-openstack-serial
ci/prow/e2e-aws-ovn-single-node-serial 2c23c04 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-azure-ovn-etcd-scaling 2c23c04 link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws 2c23c04 link false /test e2e-aws
ci/prow/e2e-azure-ovn-upgrade 2c23c04 link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 2c23c04 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-vsphere-ovn-etcd-scaling 2c23c04 link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2 2c23c04 link false /test e2e-metal-ipi-serial-ovn-ipv6-2of2
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 2c23c04 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-metal-ipi-virtualmedia 2c23c04 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-aws-ovn-cgroupsv2 2c23c04 link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-single-node 2c23c04 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-openstack-ovn 2c23c04 link false /test e2e-openstack-ovn
ci/prow/okd-scos-e2e-aws-ovn 2c23c04 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-azure 2c23c04 link false /test e2e-azure
ci/prow/e2e-aws-ovn-serial-publicnet-2of2 2c23c04 link false /test e2e-aws-ovn-serial-publicnet-2of2
ci/prow/e2e-aws-proxy 2c23c04 link false /test e2e-aws-proxy
ci/prow/e2e-aws-disruptive 2c23c04 link false /test e2e-aws-disruptive
ci/prow/e2e-gcp-ovn-etcd-scaling 2c23c04 link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/okd-e2e-gcp 2c23c04 link false /test okd-e2e-gcp
ci/prow/e2e-metal-ipi-ovn-ipv6 2c23c04 link true /test e2e-metal-ipi-ovn-ipv6

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-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8bbfae8 and 2 for PR HEAD 2c23c04 in total

@smg247
Copy link
Member

smg247 commented Jul 17, 2025

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 17, 2025

@smg247: Overrode contexts on behalf of smg247: 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.

@smg247
Copy link
Member

smg247 commented Jul 17, 2025

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 17, 2025

@smg247: Overrode contexts on behalf of smg247: ci/prow/e2e-aws-ovn-microshift

Details

In response to this:

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

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-trt
Copy link

openshift-trt bot commented Jul 17, 2025

Job Failure Risk Analysis for sha: 2c23c04

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-disruptive IncompleteTests
Tests for this run (106) are below the historical average (960): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-gcp-csi IncompleteTests
Tests for this run (26) are below the historical average (1768): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-gcp-disruptive IncompleteTests
Tests for this run (107) are below the historical average (1057): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn IncompleteTests
Tests for this run (104) are below the historical average (2331): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 2c23c04

  • "[Jira:Monitoring][sig-instrumentation] sanity test should always pass [Suite:openshift/cluster-monitoring-operator/conformance/parallel]" [Total: 29, Pass: 29, Fail: 0, Flake: 0]

@openshift-merge-bot openshift-merge-bot bot merged commit e76764b into openshift:main Jul 17, 2025
57 of 58 checks passed
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. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants