Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #30136

/assign isabella-janssen

@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60656 has been cloned as Jira Issue OCPBUGS-61172. Will retitle bug to link to clone.
/retitle [release-4.19] OCPBUGS-61172: OCPBUGS-60883: Fix PinnedImageSet test instability & update flow for tests using custom MCPs

In response to this:

This is an automated cherry-pick of #30136

/assign isabella-janssen

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 changed the title [release-4.19] OCPBUGS-60656: OCPBUGS-60883: Fix PinnedImageSet test instability & update flow for tests using custom MCPs [release-4.19] OCPBUGS-61172: OCPBUGS-60883: Fix PinnedImageSet test instability & update flow for tests using custom MCPs Sep 2, 2025
@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 Sep 2, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-61172, which is invalid:

  • expected dependent Jira Issue OCPBUGS-60656 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

In response to this:

This is an automated cherry-pick of #30136

/assign isabella-janssen

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.

@isabella-janssen
Copy link
Member

/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-serial periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-ipv4 periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-virtualmedia-1of2 periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-ipv6

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2025

@isabella-janssen: trigger 6 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-ipv4
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-virtualmedia-1of2
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e7e9b4f0-8836-11f0-9efd-47c3a5068dfe-0

@isabella-janssen
Copy link
Member

/jira cherrypick OCPBUGS-60883

@openshift-ci-robot
Copy link

@isabella-janssen: Jira Issue OCPBUGS-60883 has been cloned as Jira Issue OCPBUGS-61173. Will retitle bug to link to clone.
/retitle OCPBUGS-61173: [release-4.19] OCPBUGS-61172: OCPBUGS-60883: Fix PinnedImageSet test instability & update flow for tests using custom MCPs

In response to this:

/jira cherrypick OCPBUGS-60883

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 changed the title [release-4.19] OCPBUGS-61172: OCPBUGS-60883: Fix PinnedImageSet test instability & update flow for tests using custom MCPs OCPBUGS-61173: [release-4.19] OCPBUGS-61172: OCPBUGS-60883: Fix PinnedImageSet test instability & update flow for tests using custom MCPs Sep 2, 2025
@openshift-ci-robot openshift-ci-robot added the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Sep 2, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-61173, which is invalid:

  • expected dependent Jira Issue OCPBUGS-60883 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
  • expected dependent Jira Issue OCPBUGS-60883 to target a version in 4.20.0, but no target version was set

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.

In response to this:

This is an automated cherry-pick of #30136

/assign isabella-janssen

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.

@isabella-janssen
Copy link
Member

/retitle [release-4.19] OCPBUGS-61172: OCPBUGS-60883: Fix PinnedImageSet test instability & update flow for tests using custom MCPs

@openshift-ci openshift-ci bot changed the title OCPBUGS-61173: [release-4.19] OCPBUGS-61172: OCPBUGS-60883: Fix PinnedImageSet test instability & update flow for tests using custom MCPs [release-4.19] OCPBUGS-61172: OCPBUGS-60883: Fix PinnedImageSet test instability & update flow for tests using custom MCPs Sep 2, 2025
@openshift-ci-robot openshift-ci-robot removed the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Sep 2, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-61172, which is invalid:

  • expected dependent Jira Issue OCPBUGS-60656 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

In response to this:

This is an automated cherry-pick of #30136

/assign isabella-janssen

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.

@isabella-janssen
Copy link
Member

/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 Sep 4, 2025
@openshift-ci-robot
Copy link

@isabella-janssen: This pull request references Jira Issue OCPBUGS-61172, 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 (4.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-60656 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-60656 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents

Requesting review from QA contact:
/cc @sergiordlr

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.

@openshift-ci openshift-ci bot requested a review from sergiordlr September 4, 2025 16:49
@isabella-janssen
Copy link
Member

/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-serial periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-ipv4 periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-virtualmedia-1of2 periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-ipv6

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 9, 2025

@isabella-janssen: trigger 6 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-ipv4
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-virtualmedia-1of2
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/284ff2a0-8d7a-11f0-8051-aa3eacd9e77e-0

@isabella-janssen
Copy link
Member

/verified by running 4.19 serial payload rehearsals

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 12, 2025
@openshift-ci-robot
Copy link

@isabella-janssen: This PR has been marked as verified by running 4.19 serial payload rehearsals.

In response to this:

/verified by running 4.19 serial payload rehearsals

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.

@isabella-janssen
Copy link
Member

isabella-janssen commented Sep 24, 2025

/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-serial periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-ipv4 periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-virtualmedia-1of2 periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-ipv6

Running these rehearsals to made sure this still looks good since it's sat for a while.

Edit to add results: Expected runs passed, AWS issues are unrelated.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2025

@isabella-janssen: trigger 6 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-ipv4
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-virtualmedia-1of2
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ef07d760-994f-11f0-96ca-7b8c1e6f5ed8-0

@yuqi-zhang
Copy link
Contributor

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 25, 2025

@isabella-janssen: trigger 6 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-single-node-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-ipv4
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-virtualmedia-1of2
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/15338a70-9a17-11f0-88ab-45d2d89ae600-0

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

openshift-ci bot commented Sep 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, yuqi-zhang

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

The pull request process is described here

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 Sep 25, 2025
@isabella-janssen
Copy link
Member

/refresh

@isabella-janssen
Copy link
Member

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2025

@isabella-janssen: The following commands are available to trigger required jobs:

/test e2e-aws-jenkins
/test e2e-aws-ovn-edge-zones
/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-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 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
/test e2e-aws-csi
/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-etcd-scaling
/test e2e-aws-ovn-kube-apiserver-rollout
/test e2e-aws-ovn-kubevirt
/test e2e-aws-ovn-serial-ipsec
/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-ovn-virt-techpreview
/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-csi
/test e2e-gcp-disruptive
/test e2e-gcp-fips-serial
/test e2e-gcp-ovn-etcd-scaling
/test e2e-gcp-ovn-rt-upgrade
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-techpreview-serial
/test e2e-gcp-ovn-usernamespace
/test e2e-hypershift-conformance
/test e2e-metal-ipi-ovn
/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
/test e2e-metal-ipi-serial-ovn-ipv6
/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-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-release-4.19-e2e-agnostic-ovn-cmd
pull-ci-openshift-origin-release-4.19-e2e-aws-csi
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-edge-zones
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-fips
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-microshift
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-microshift-serial
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-serial-1of2
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-serial-2of2
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-single-node
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-single-node-serial
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-single-node-upgrade
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-upgrade
pull-ci-openshift-origin-release-4.19-e2e-gcp-csi
pull-ci-openshift-origin-release-4.19-e2e-gcp-ovn
pull-ci-openshift-origin-release-4.19-e2e-gcp-ovn-rt-upgrade
pull-ci-openshift-origin-release-4.19-e2e-gcp-ovn-upgrade
pull-ci-openshift-origin-release-4.19-e2e-hypershift-conformance
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-ovn
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-origin-release-4.19-e2e-metal-ipi-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-release-4.19-e2e-openstack-ovn
pull-ci-openshift-origin-release-4.19-e2e-vsphere-ovn
pull-ci-openshift-origin-release-4.19-e2e-vsphere-ovn-upi
pull-ci-openshift-origin-release-4.19-images
pull-ci-openshift-origin-release-4.19-lint
pull-ci-openshift-origin-release-4.19-okd-scos-e2e-aws-ovn
pull-ci-openshift-origin-release-4.19-okd-scos-images
pull-ci-openshift-origin-release-4.19-unit
pull-ci-openshift-origin-release-4.19-verify
pull-ci-openshift-origin-release-4.19-verify-deps

In response to this:

/test ?

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.

@isabella-janssen
Copy link
Member

/test all

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2025

@openshift-cherrypick-robot: 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-single-node-upgrade 01a066d link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-gcp-ovn-rt-upgrade 01a066d link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-gcp-csi 01a066d link false /test e2e-gcp-csi
ci/prow/e2e-aws-ovn-single-node 01a066d link false /test e2e-aws-ovn-single-node
ci/prow/e2e-openstack-ovn 01a066d link false /test e2e-openstack-ovn

Full PR test history. Your PR dashboard.

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 3137f6b and 2 for PR HEAD 01a066d in total

@openshift-merge-bot openshift-merge-bot bot merged commit eaad32d into openshift:release-4.19 Oct 1, 2025
28 of 33 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-61172
✔️ 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-61172 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

This is an automated cherry-pick of #30136

/assign isabella-janssen

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. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants