Skip to content

Conversation

@jcaamano
Copy link
Contributor

@jcaamano jcaamano commented Oct 13, 2025

Cherry-picks from master for upstream fix ovn-kubernetes/ovn-kubernetes#5626 and ovn-kubernetes/ovn-kubernetes#5658

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2025
@jcaamano jcaamano changed the title Ocpbugs real 56783 4.20 kubevirt: fix bad release of IPs of live migratable pods Oct 13, 2025
@jcaamano
Copy link
Contributor Author

/jira cherrypick OCPBUGS-56783

@openshift-ci-robot
Copy link
Contributor

@jcaamano: Jira Issue OCPBUGS-56783 has been cloned as Jira Issue OCPBUGS-63007. Will retitle bug to link to clone.
/retitle OCPBUGS-63007: kubevirt: fix bad release of IPs of live migratable pods

Details

In response to this:

/jira cherrypick OCPBUGS-56783

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 kubevirt: fix bad release of IPs of live migratable pods OCPBUGS-63007: kubevirt: fix bad release of IPs of live migratable pods Oct 13, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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 Oct 13, 2025
@openshift-ci-robot
Copy link
Contributor

@jcaamano: This pull request references Jira Issue OCPBUGS-63007, 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 dependent Jira Issue OCPBUGS-56783 to target a version in 4.21.0, but it targets "4.21" 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.

Details

In response to this:

Cherry-picks from master for upstream fix ovn-kubernetes/ovn-kubernetes#5626.
Extra commit cherry-picked "Fix naming of "Secondary" to be "User-Defined" to avoid conflicts.

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.

@jcaamano
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 Oct 13, 2025
@openshift-ci-robot
Copy link
Contributor

@jcaamano: This pull request references Jira Issue OCPBUGS-63007, 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.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state New, 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-56783 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-56783 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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.

@jcaamano
Copy link
Contributor Author

/retest

@martinkennelly
Copy link
Contributor

martinkennelly commented Oct 14, 2025

/payload 4.20 ci blocking
/payload 4.20 nightly blocking

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2025

@martinkennelly: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2025

@martinkennelly: trigger 5 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-aks
  • periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/efc04de0-a8e5-11f0-8974-124b476eb6ac-0

trigger 13 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-1of2
  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial-2of2
  • 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-1of3
  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial-2of3
  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview-serial-3of3
  • 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/efc04de0-a8e5-11f0-8974-124b476eb6ac-1

@jcaamano
Copy link
Contributor Author

/override ci/prow/lint

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/lint

Details

In response to this:

/override ci/prow/lint

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.

@martinkennelly
Copy link
Contributor

payloads that passed and got infra up look fine.

@martinkennelly
Copy link
Contributor

martinkennelly commented Oct 14, 2025

qe-perfscale-payload-control-plane-6nodes - cannot trust the job numbers unfortunately. Discussion last fri to remove this as required job until its stable and results comprehensible : https://redhat-internal.slack.com/archives/CU9HKBZKJ/p1759941599018259

@martinkennelly
Copy link
Contributor

For job e2e-metal-ipi-ovn-dualstack-bgp-local-gw unrelated failure.

Looks like it got killed prematurely but unsure. I also see an error for loggin in.

ERRO[2025-10-14T13:55:59Z] Some steps failed:                           
ERRO[2025-10-14T13:55:59Z] 
  * could not run steps: execution cancelled 
INFO[2025-10-14T13:55:59Z] Reporting job state 'failed' with reason 'executing_graph:interrupted' 
error: build error: Failed to push image: trying to reuse blob sha256:25c75c34b2e2b68ba9245d9cddeb6b8a0887371ed30744064f85241a75704d87 at destination: unable to retrieve auth token: invalid username/password: authentication required

@martinkennelly
Copy link
Contributor

for job e2e-gcp-ovn
Seems unrelated.. :

: [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] removes definition from spec when one version gets changed to not be served [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] expand_less	28s
{  fail [k8s.io/kubernetes/test/e2e/apimachinery/crd_publish_openapi.go:475]: failed to wait for definition "com.example.crd-publish-openapi-test-multi-to-single-ver.v5.e2e-test-crd-publish-openapi-4112-crd" to be served with the right OpenAPI schema: failed to wait for OpenAPI spec validating condition: Get "https://api.ci-op-nh7bd963-04dd4.XXXXXXXXXXXXXXXXXXXXXX:6443/openapi/v2": EOF; lastMsg:}

@martinkennelly
Copy link
Contributor

for job 4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade i see some extra disruption when talking to api server but unknown if its related or flaking. Ill let the retry decide i guess.

/lgtm

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

/hold

I think I might have introduced an issue. Will keep you updated @martinkennelly

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: martinkennelly, pperiyasamy

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

@jcaamano
Copy link
Contributor Author

/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 Oct 28, 2025
@anuragthehatter
Copy link

/verified by @anuragthehatter

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

@anuragthehatter: This PR has been marked as verified by @anuragthehatter.

Details

In response to this:

/verified by @anuragthehatter

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

/retest-required

Remaining retests: 0 against base HEAD 962c36b and 2 for PR HEAD d644e2a in total

@jcaamano
Copy link
Contributor Author

jcaamano commented Nov 3, 2025

/override ci/prow/lint
/override ci/prow/security

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 3, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/lint, ci/prow/security

Details

In response to this:

/override ci/prow/lint
/override ci/prow/security

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.

@jcaamano
Copy link
Contributor Author

jcaamano commented Nov 3, 2025

/retest

2 similar comments
@jcaamano
Copy link
Contributor Author

jcaamano commented Nov 3, 2025

/retest

@jcaamano
Copy link
Contributor Author

jcaamano commented Nov 4, 2025

/retest

@jcaamano
Copy link
Contributor Author

jcaamano commented Nov 4, 2025

/override ci/prow/lint

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 4, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/lint

Details

In response to this:

/override ci/prow/lint

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

openshift-ci bot commented Nov 4, 2025

@jcaamano: 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/lint d644e2a link unknown /test lint

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 8a02fda into openshift:release-4.20 Nov 4, 2025
30 checks passed
@openshift-ci-robot
Copy link
Contributor

@jcaamano: Jira Issue Verification Checks: Jira Issue OCPBUGS-63007
✔️ 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-63007 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-picks from master for upstream fix ovn-kubernetes/ovn-kubernetes#5626 and ovn-kubernetes/ovn-kubernetes#5658.
Extra commit cherry-picked "Fix naming of "Secondary" to be "User-Defined" to avoid conflicts.
No conflicts

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.

@jcaamano
Copy link
Contributor Author

jcaamano commented Nov 4, 2025

/cherry-pick release-4.19

@openshift-cherrypick-robot

@jcaamano: new pull request created: #2842

Details

In response to this:

/cherry-pick release-4.19

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

@jcaamano: Jira Issue OCPBUGS-63007 is in an unrecognized state (Closed) and will not be moved to the MODIFIED state.

Details

In response to this:

Cherry-picks from master for upstream fix ovn-kubernetes/ovn-kubernetes#5626 and ovn-kubernetes/ovn-kubernetes#5658 from #2847

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

@jcaamano: Jira Issue OCPBUGS-63007 is in an unrecognized state (Closed) and will not be moved to the MODIFIED state.

Details

In response to this:

Cherry-picks from master for upstream fix ovn-kubernetes/ovn-kubernetes#5626 and ovn-kubernetes/ovn-kubernetes#5658

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/severity-important Referenced Jira bug's severity is important 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.