Bug 2095641
| Summary: | nmstate rust cannot update ovs when a different port name exists in NM | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Mingyu Shi <mshi> | ||||
| Component: | nmstate | Assignee: | Gris Ge <fge> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Mingyu Shi <mshi> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 9.1 | CC: | ferferna, jiji, jishi, network-qe, sfaye, till | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | nmstate-2.1.3-0.20220714.81d80992.el9 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-11-15 10:01:25 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Mingyu Shi
2022-06-10 05:15:46 UTC
BTW, on RHEL 8, after successfully applied, the port name changed to(to keep the same name for the ovs interface and the ovs port, like what "ovs-vsctl" does):
+ nmcli con
NAME UUID TYPE DEVICE
smyle ff3577fc-9285-43e1-b2cb-d68b1db7ce02 ethernet ens3
ovs-slave-br-ex 45673042-11bc-4df3-92b1-f82a3f9e5c16 ovs-interface br-ex
br-ex-port 14944b18-f2f1-4186-bbfe-c9a6ac33393f ovs-port br-ex
cnv-veth d3572b4a-4c2d-46e2-9fa9-b5a8fadb014c veth cnv-veth
ovn-veth bce14fee-c996-47ef-99cd-22bf6dfa999c veth ovn-veth
ovn-veth-port 77124ad5-7e94-4f1f-af65-a5c50d07b8d9 ovs-port ovn-veth
ovs-bridge-br-ex d133ce79-8939-4fa5-bdad-145901e1d413 ovs-bridge br-ex
ovspatch0-port 9e8b0bb9-847e-48c6-b5ff-6113d15837cd ovs-port ovspatch0
ovspatch0_p-port 735b9ff3-b967-4f48-b52b-40b1cf06c5ef ovs-port ovspatch0_p
ovs-slave-ovspatch0 d39534e7-0ad5-4735-917d-a71ca9849d92 ovs-interface ovspatch0
ovs-slave-ovspatch0_p da40c874-e6ec-4728-8749-4f382b6ce7e3 ovs-interface ovspatch0_p
ovs-slave-veth0 5dd0acd6-4cd4-41d3-8a1e-60cc0402b462 ethernet veth0
veth0-port ccf6546b-fc14-4faf-bb1a-a5cd34988359 ovs-port veth0
+ ovs-vsctl show
a5a57d5b-39fc-4104-9cbc-417797687f02
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port ovspatch0
Interface ovspatch0
type: patch
options: {peer=ovspatch0_p}
Port ovn-veth
Interface ovn-veth
type: system
Port veth0
Interface veth0
type: system
Port ovspatch0_p
Interface ovspatch0_p
type: patch
options: {peer=ovspatch0}
ovs_version: "2.15.5"
Patch sent to upstream: https://github.com/nmstate/nmstate/pull/1961 The key point of reproducer is create new veth and attach this new veth to existing OVS bridge in the single transaction. Pretested with: nmstate-2.1.3-0.20220713051645600109.pr1959.9.gb4024cfe.el9.x86_64 NetworkManager-1.39.8-1.el9.x86_64 openvswitch2.15-2.15.0-65.el9fdp.x86_64 Verified with: nmstate-2.1.3-1.el9.x86_64 NetworkManager-1.39.10-1.el9.x86_64 openvswitch2.15-2.15.0-66.el9fdp.x86_64 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-2022:7991 |