[release-4.18] OCPBUGS-57081: Do not set the MTU when using NetworkAttachementDefinition
This is an automated cherry-pick of #29879
/assign kyrtapz
@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
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-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.
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.
/test e2e-aws-ovn-edge-zones Checking to see if this job now fails on all release-4.18 PRs or just #29871
/jira refresh
@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
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.
[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
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/test ci/prow/e2e-gcp-ovn /test ci/prow/e2e-aws-ovn-edge-zones
@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
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.
/retest-required
Remaining retests: 0 against base HEAD 7f2da908f99f71d3e9e71465209d3023bd1dfbd9 and 2 for PR HEAD 6750f2af817b0db465ca7f431cd349d0445b3eb0 in total
/retest-required
Remaining retests: 0 against base HEAD 7f2da908f99f71d3e9e71465209d3023bd1dfbd9 and 2 for PR HEAD 6750f2af817b0db465ca7f431cd349d0445b3eb0 in total
/retest-required
Remaining retests: 0 against base HEAD 7f2da908f99f71d3e9e71465209d3023bd1dfbd9 and 2 for PR HEAD 6750f2af817b0db465ca7f431cd349d0445b3eb0 in total
/retest-required
Remaining retests: 0 against base HEAD 7f2da908f99f71d3e9e71465209d3023bd1dfbd9 and 2 for PR HEAD 6750f2af817b0db465ca7f431cd349d0445b3eb0 in total
@openshift-cherrypick-robot: all tests passed!
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-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.
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.
[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.
Fix included in accepted release 4.18.0-0.nightly-2025-07-05-144120