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.
Description of problem:
The ovs-bond has certain parameters that needs to be configured via other-config [1].
The expected output for ovs-bond would be
[root@dell-r640-oss-14 ~]# sudo ovs-vsctl list port
_uuid : b23fcf87-b175-4532-a42c-7f8c22811496
bond_active_slave : "e4:43:4b:5c:96:82"
bond_downdelay : 0
bond_fake_iface : false
bond_mode : balance-slb
bond_updelay : 0
cvlans : []
external_ids : {NM.connection.uuid="98b3bcbf-7be6-4eae-ac31-9738fe309b2a"}
fake_bridge : false
interfaces : [4f598dfb-acb1-4a3d-a7fb-196e59ed40f1, 7c501de1-eb59-4f2c-b21d-0dd212d32fef]
lacp : off
mac : []
name : ovs-bond1
other_config : {bond-miimon-interval="100"}
protected : false
qos : []
rstp_statistics : {}
rstp_status : {}
statistics : {}
status : {}
tag : []
trunks : []
vlan_mode : []
Also its required for Bridges Table, as we have a need to set the "other_config : mac-table-size" for the bridge.
So IMHO the ovs-db object shall be present at global level, bridge level and port level. The BZ description needs this refinement.
[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html/director_installation_and_usage/assembly_configuring-overcloud-networking_installing-director-on-the-undercloud#ref_open-vswitch-ovs-bonding-options_network-interface-bonding
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
The manpage of `ovs-vswitchd.conf.db` indicate the `other_config` is `map of string-string pairs`, hence I would like to suggest NetworkManager support arbitrary `other_config` and let OVS daemon validate it.
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/RHBA-2023:2485
Description of problem: The ovs-bond has certain parameters that needs to be configured via other-config [1]. The expected output for ovs-bond would be [root@dell-r640-oss-14 ~]# sudo ovs-vsctl list port _uuid : b23fcf87-b175-4532-a42c-7f8c22811496 bond_active_slave : "e4:43:4b:5c:96:82" bond_downdelay : 0 bond_fake_iface : false bond_mode : balance-slb bond_updelay : 0 cvlans : [] external_ids : {NM.connection.uuid="98b3bcbf-7be6-4eae-ac31-9738fe309b2a"} fake_bridge : false interfaces : [4f598dfb-acb1-4a3d-a7fb-196e59ed40f1, 7c501de1-eb59-4f2c-b21d-0dd212d32fef] lacp : off mac : [] name : ovs-bond1 other_config : {bond-miimon-interval="100"} protected : false qos : [] rstp_statistics : {} rstp_status : {} statistics : {} status : {} tag : [] trunks : [] vlan_mode : [] Also its required for Bridges Table, as we have a need to set the "other_config : mac-table-size" for the bridge. So IMHO the ovs-db object shall be present at global level, bridge level and port level. The BZ description needs this refinement. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html/director_installation_and_usage/assembly_configuring-overcloud-networking_installing-director-on-the-undercloud#ref_open-vswitch-ovs-bonding-options_network-interface-bonding Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: