Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #29879

/assign kyrtapz

The static MTU can be incorrect in some clusters, instead
rely on the fact that when the MTU is left unset OVN-Kubernetes
will use a default equal to the clusterNetworkMTU.
https://github.com/ovn-kubernetes/ovn-kubernetes/blob/1df91ecad2dc2e283dd4106e2e5069aff9eb1eb5/go-controller/pkg/config/cni.go#L103

Signed-off-by: Patryk Diak <[email protected]>
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56967 has been cloned as Jira Issue OCPBUGS-57081. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-57081: Do not set the MTU when using NetworkAttachementDefinition

Details

In response to this:

This is an automated cherry-pick of #29879

/assign kyrtapz

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.18] OCPBUGS-56967: Do not set the MTU when using NetworkAttachementDefinition [release-4.18] OCPBUGS-57081: Do not set the MTU when using NetworkAttachementDefinition Jun 4, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical 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 Jun 4, 2025
@openshift-ci-robot
Copy link

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

  • expected dependent Jira Issue OCPBUGS-56967 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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:

This is an automated cherry-pick of #29879

/assign kyrtapz

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 review from knobunc and trozet June 4, 2025 16:16
@sdodson
Copy link
Member

sdodson commented Jun 9, 2025

/test e2e-aws-ovn-edge-zones
Checking to see if this job now fails on all release-4.18 PRs or just #29871

Copy link
Contributor

@tssurya tssurya left a comment

Choose a reason for hiding this comment

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

/lgtm

@tssurya
Copy link
Contributor

tssurya commented Jul 2, 2025

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

@tssurya: This pull request references Jira Issue OCPBUGS-57081, 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.18.z) matches configured target version for branch (4.18.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-56967 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-56967 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • 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.

@openshift-ci openshift-ci bot requested a review from anuragthehatter July 2, 2025 17:28
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2025
@sdodson sdodson added approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Jul 2, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

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

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

@jluhrsen
Copy link
Contributor

jluhrsen commented Jul 2, 2025

/test ci/prow/e2e-gcp-ovn
/test ci/prow/e2e-aws-ovn-edge-zones

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

@jluhrsen: The specified target(s) for /test were not found.
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
/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 images
/test lint
/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-metal-ipi-ovn
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
/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-openstack-ovn
/test e2e-openstack-serial
/test e2e-vsphere
/test e2e-vsphere-ovn-dualstack-primaryv6
/test e2e-vsphere-ovn-etcd-scaling
/test okd-scos-e2e-aws-ovn
/test okd-scos-images

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

pull-ci-openshift-origin-release-4.18-e2e-agnostic-ovn-cmd
pull-ci-openshift-origin-release-4.18-e2e-aws-csi
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-edge-zones
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-fips
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-microshift
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-microshift-serial
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-serial
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node-serial
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-single-node-upgrade
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-upgrade
pull-ci-openshift-origin-release-4.18-e2e-gcp-csi
pull-ci-openshift-origin-release-4.18-e2e-gcp-ovn
pull-ci-openshift-origin-release-4.18-e2e-gcp-ovn-rt-upgrade
pull-ci-openshift-origin-release-4.18-e2e-gcp-ovn-upgrade
pull-ci-openshift-origin-release-4.18-e2e-metal-ipi-ovn
pull-ci-openshift-origin-release-4.18-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-origin-release-4.18-e2e-metal-ipi-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-release-4.18-e2e-openstack-ovn
pull-ci-openshift-origin-release-4.18-images
pull-ci-openshift-origin-release-4.18-lint
pull-ci-openshift-origin-release-4.18-okd-scos-e2e-aws-ovn
pull-ci-openshift-origin-release-4.18-unit
pull-ci-openshift-origin-release-4.18-verify
pull-ci-openshift-origin-release-4.18-verify-deps
Details

In response to this:

/test ci/prow/e2e-gcp-ovn
/test ci/prow/e2e-aws-ovn-edge-zones

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

/retest-required

Remaining retests: 0 against base HEAD 7f2da90 and 2 for PR HEAD 6750f2a in total

3 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7f2da90 and 2 for PR HEAD 6750f2a in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7f2da90 and 2 for PR HEAD 6750f2a in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7f2da90 and 2 for PR HEAD 6750f2a in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 3, 2025

@openshift-cherrypick-robot: all tests passed!

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 638b81f into openshift:release-4.18 Jul 3, 2025
28 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-57081: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-57081 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #29879

/assign kyrtapz

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

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.18.0-202507040034.p0.g638b81f.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.18.0-0.nightly-2025-07-05-144120

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-critical Referenced Jira bug's severity is critical 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

Development

Successfully merging this pull request may close these issues.