Skip to content

Conversation

@rexagod
Copy link
Member

@rexagod rexagod commented Dec 25, 2025

Adds tests corresponding to the changes done in openshift/cluster-monitoring-operator#2694, needs that PR to go in first.

@openshift-ci-robot
Copy link

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 25, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 25, 2025

@rexagod: This pull request references MON-4389 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.22.0" version, but no target version was set.

Details

In response to this:

Adds tests corresponding to the changes done in openshift/cluster-monitoring-operator#2694

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.

@rexagod rexagod marked this pull request as draft December 25, 2025 22:40
@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 Dec 25, 2025
@rexagod rexagod marked this pull request as ready for review December 25, 2025 22:41
@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 Dec 25, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rexagod

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 Dec 25, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 25, 2025

@rexagod: This pull request references MON-4389 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.22.0" version, but no target version was set.

Details

In response to this:

Adds tests corresponding to the changes done in openshift/cluster-monitoring-operator#2694, needs that PR to go in first.

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.

Adds tests corresponding to the changes done in openshift/cluster-monitoring-operator#2694

Signed-off-by: Pranshu Srivastava <rexagod@gmail.com>
@rexagod rexagod force-pushed the telemetry-collection-profile branch from 9db9e21 to 0e1dd25 Compare December 26, 2025 15:30
Comment on lines -66 to -68
if !exutil.IsTechPreviewNoUpgrade(tctx, oc.AdminConfigClient()) {
g.Skip("skipping, this feature is only supported on TechPreviewNoUpgrade clusters")
}
Copy link
Member Author

Choose a reason for hiding this comment

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

@rexagod: The following test 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/okd-scos-images 0e1dd25 link true /test okd-scos-images

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.

@rexagod
Copy link
Member Author

rexagod commented Dec 26, 2025

/test openshift/origin/main/e2e-aws-ovn-single-node-serial openshift/cluster-monitoring-operator#2694

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

@rexagod: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-aws-csi
/test e2e-aws-jenkins
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-image-registry
/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-builds
/test e2e-gcp-ovn-image-ecosystem
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi
/test go-verify-deps
/test images
/test lint
/test okd-scos-images
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd
/test e2e-aws-disruptive
/test e2e-aws-etcd-certrotation
/test e2e-aws-etcd-recovery
/test e2e-aws-ovn
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-edge-zones
/test e2e-aws-ovn-etcd-scaling
/test e2e-aws-ovn-kube-apiserver-rollout
/test e2e-aws-ovn-kubevirt
/test e2e-aws-ovn-serial-fast
/test e2e-aws-ovn-serial-ipsec
/test e2e-aws-ovn-serial-publicnet-1of2
/test e2e-aws-ovn-serial-publicnet-2of2
/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-single-node-serial
/test e2e-aws-ovn-single-node-techpreview
/test e2e-aws-ovn-single-node-techpreview-serial
/test e2e-aws-ovn-single-node-upgrade
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-rollback
/test e2e-aws-ovn-upi
/test e2e-aws-proxy
/test e2e-azure
/test e2e-azure-ovn-etcd-scaling
/test e2e-azure-ovn-upgrade
/test e2e-baremetalds-kubevirt
/test e2e-external-aws
/test e2e-external-aws-ccm
/test e2e-external-vsphere-ccm
/test e2e-gcp-disruptive
/test e2e-gcp-fips-serial-1of2
/test e2e-gcp-fips-serial-2of2
/test e2e-gcp-ovn-etcd-scaling
/test e2e-gcp-ovn-kube-apiserver-rollout
/test e2e-gcp-ovn-rt-upgrade
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-techpreview-serial-1of2
/test e2e-gcp-ovn-techpreview-serial-2of2
/test e2e-gcp-ovn-usernamespace
/test e2e-hypershift-conformance
/test e2e-metal-ipi-ovn
/test e2e-metal-ipi-ovn-bgp-virt-dualstack
/test e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-dualstack-bgp
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/test e2e-metal-ipi-ovn-dualstack-local-gateway
/test e2e-metal-ipi-ovn-kube-apiserver-rollout
/test e2e-metal-ipi-serial-1of2
/test e2e-metal-ipi-serial-2of2
/test e2e-metal-ipi-serial-ovn-ipv6-1of2
/test e2e-metal-ipi-serial-ovn-ipv6-2of2
/test e2e-metal-ipi-virtualmedia
/test e2e-metal-ovn-single-node-live-iso
/test e2e-metal-ovn-single-node-with-worker-live-iso
/test e2e-metal-ovn-two-node-arbiter
/test e2e-metal-ovn-two-node-fencing
/test e2e-openstack-ovn
/test e2e-openstack-serial
/test e2e-vsphere-ovn-dualstack-primaryv6
/test e2e-vsphere-ovn-etcd-scaling
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-origin-main-go-verify-deps
pull-ci-openshift-origin-main-images
pull-ci-openshift-origin-main-lint
pull-ci-openshift-origin-main-okd-scos-images
pull-ci-openshift-origin-main-unit
pull-ci-openshift-origin-main-verify
pull-ci-openshift-origin-main-verify-deps
Details

In response to this:

/test openshift/origin/main/e2e-aws-ovn-single-node-serial openshift/cluster-monitoring-operator#2694

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.

@rexagod
Copy link
Member Author

rexagod commented Dec 26, 2025

/testwith openshift/origin/main/e2e-aws-ovn-single-node-serial openshift/cluster-monitoring-operator#2694

@rexagod
Copy link
Member Author

rexagod commented Dec 26, 2025

/testwith openshift/origin/main/e2e-aws-ovn-serial-1of2 openshift/cluster-monitoring-operator#2694
/testwith openshift/origin/main/e2e-aws-ovn-serial-2of2 openshift/cluster-monitoring-operator#2694

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

@rexagod, testwith: could not generate prow job. ERROR:

BUG: test 'e2e-aws-ovn-serial-1of2' not found in injected config

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

@rexagod, testwith: could not generate prow job. ERROR:

BUG: test 'e2e-aws-ovn-serial-2of2' not found in injected config

@rexagod
Copy link
Member Author

rexagod commented Dec 26, 2025

/payload-job-with-prs pull-ci-openshift-router-master-e2e-aws-serial-1of2 openshift/cluster-monitoring-operator#2694
/payload-job-with-prs pull-ci-openshift-router-master-e2e-aws-serial-2of2 openshift/cluster-monitoring-operator#2694

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

@rexagod: given command is invalid: at least one of the commands given is only supported on a one-command-per-comment basis, please separate out commands as multiple comments

@rexagod
Copy link
Member Author

rexagod commented Dec 26, 2025

/payload-job-with-prs pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 openshift/cluster-monitoring-operator#2694

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

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

@rexagod
Copy link
Member Author

rexagod commented Dec 26, 2025

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-serial-1of2 openshift/cluster-monitoring-operator#2694

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-serial-1of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c20b6940-e2ae-11f0-8ea5-16a9a10b06e5-0

@rexagod
Copy link
Member Author

rexagod commented Dec 26, 2025

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-serial-2of2 openshift/cluster-monitoring-operator#2694

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-serial-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d67b5840-e2ae-11f0-903c-6c0ebc3e7cfd-0

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants