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.
This bug was initially created as a copy of Bug #1955101
I am copying this bug because:
I am seeing this again
OVS is 2.15.2
visible sporadically
it looks like after NM service restart something goes odd and just one port of ovs bond is up
95324ca5-3c6b-4d0f-9bc4-364ff4889d87
Bridge ovsbridge0
Port bond0
tag: 120
Interface eth3
type: system
Port port0
tag: 120
Interface iface0
type: internal
ovs_version: "2.15.2"
the other is up (from the NM PoV) but not in OVS
--- nmcli c ---
NAME UUID TYPE DEVICE
testeth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 ethernet eth0
ovs-iface0 97912903-3077-40e2-b234-fbacf186f0ec ovs-interface iface0
ovs-eth2 e7e63698-5d5d-4e48-93d8-c20098ade0e7 ethernet eth2
ovs-bond0 7ed90b92-d35c-4c91-a467-7324130d386b ovs-port bond0
ovs-bridge0 d79c4bd0-853d-4c9d-9f3a-6a95d131270c ovs-bridge ovsbridge0
ovs-eth3 7b61b193-f3da-4cc3-912b-03762cd4c81f ethernet eth3
ovs-port0 d1a37e03-8667-46f9-992b-12a9c02ed8ab ovs-port port0
^^ This may look like an OVS issue.
full log attached as html
This seems to be failing another way now.. after Reboot step:
using:
[root@wsfd-netdev34-vm-5 NetworkManager-ci]# test=NM_reboot_openvswitch_vlan_configuration; a=0; while ./test_run.sh $test; do :;((a++)); echo "ATTEMPT $a"; if [ $a -eq 100 ]; then break; fi ; done
52 attempts first time
4 second time
59 third time
attaching logs
-> back to assigned
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 (NetworkManager 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/RHEA-2022:1985