Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (nmstate bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4696
Description of problem: MTU of an ovs patch port is shown as 0, as ip, mac and mtu are not supported on a patch port, it's better to make these unseen. Version-Release number of selected component (if applicable): nmstate-0.3.3-2.el8.noarch NetworkManager-1.26.0-1.el8.x86_64 DISTRO=RHEL-8.3.0-20200716.n.0 Linux hp-dl388g8-04.rhts.eng.pek2.redhat.com 4.18.0-226.el8.x86_64 #1 SMP Wed Jul 15 07:40:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux openvswitch2.12-2.12.0-12.el8fdp.x86_64 openvswitch-selinux-extra-policy-1.0-19.el8fdp.noarch How reproducible: 100% Steps to Reproduce: # cat ovs-patch.yaml --- interfaces: - name: patch0 type: ovs-interface state: up patch: peer: patch1 - name: ovs-br0 type: ovs-bridge state: up bridge: options: stp: true port: - name: patch0 - name: patch1 type: ovs-interface state: up patch: peer: patch0 - name: ovs-br1 type: ovs-bridge state: up bridge: options: stp: true port: - name: patch1 1. nmstatectl set ovs-patch.yaml 2. nmstatectl show patch0 --- dns-resolver: config: search: [] server: [] running: search: - rhts.eng.pek2.redhat.com server: - 10.73.2.107 - 10.73.2.108 - 10.66.127.10 route-rules: config: [] routes: config: [] running: [] interfaces: - name: patch0 type: ovs-interface state: up ipv4: enabled: false ipv6: enabled: false autoconf: false dhcp: false lldp: enabled: false mtu: 0 patch: peer: patch1 Actual results: Expected results: Additional info: