Skip to content

OCPBUGS-57206: Backport pr 29834 to release-4.19 #29903

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: release-4.19
Choose a base branch
from
Open

OCPBUGS-57206: Backport pr 29834 to release-4.19 #29903

wants to merge 1 commit into from

Conversation

wangke19
Copy link
Contributor

Backport pr 29834 to release-4.19 manually.

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jun 10, 2025
@openshift-ci-robot
Copy link

@wangke19: This pull request references Jira Issue OCPBUGS-57206, 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.

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:

Backport pr 29834 to release-4.19 manually.

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jun 10, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 10, 2025

@wangke19: 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-serial c699ab6 link true /test e2e-aws-ovn-microshift-serial
ci/prow/e2e-aws-ovn-single-node-upgrade c699ab6 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/okd-scos-e2e-aws-ovn c699ab6 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-ovn c699ab6 link true /test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-ovn c699ab6 link false /test e2e-metal-ipi-ovn
ci/prow/e2e-vsphere-ovn-upi c699ab6 link true /test e2e-vsphere-ovn-upi
ci/prow/e2e-aws-ovn-fips c699ab6 link true /test e2e-aws-ovn-fips
ci/prow/e2e-hypershift-conformance c699ab6 link false /test e2e-hypershift-conformance
ci/prow/e2e-aws-ovn-image-registry c699ab6 link true /test e2e-aws-ovn-image-registry
ci/prow/e2e-aws-ovn-microshift c699ab6 link true /test e2e-aws-ovn-microshift
ci/prow/e2e-aws-ovn-single-node c699ab6 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-openstack-ovn c699ab6 link false /test e2e-openstack-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview c699ab6 link false /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
ci/prow/e2e-aws-ovn-cgroupsv2 c699ab6 link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-edge-zones c699ab6 link true /test e2e-aws-ovn-edge-zones
ci/prow/e2e-metal-ipi-ovn-ipv6 c699ab6 link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-kube-apiserver-rollout c699ab6 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-vsphere-ovn c699ab6 link true /test e2e-vsphere-ovn
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout c699ab6 link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-serial c699ab6 link false /test e2e-aws-ovn-single-node-serial

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.

@wangke19
Copy link
Contributor Author

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

@wangke19: This pull request references Jira Issue OCPBUGS-57206, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-35855 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-35855 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 @gangwgr

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 gangwgr June 16, 2025 06:56
@wangke19
Copy link
Contributor Author

/assign @ardaguclu

@ardaguclu
Copy link
Member

/lgtm

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

openshift-ci bot commented Jun 16, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ardaguclu, wangke19
Once this PR has been reviewed and has the lgtm label, please assign flavianmissi, jwmatthews for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@wangke19
Copy link
Contributor Author

/assign @p0lyn0mial

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

@flavianmissi flavianmissi Awaiting requested review from flavianmissi

@LalatenduMohanty LalatenduMohanty Awaiting requested review from LalatenduMohanty

@gangwgr gangwgr Awaiting requested review from gangwgr

Assignees

@ardaguclu ardaguclu

@p0lyn0mial p0lyn0mial

Labels
jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@wangke19 @openshift-ci-robot @ardaguclu @p0lyn0mial