Bug 2155368

Summary: Failed to move ovs port to linux bridge and bond
Product: Red Hat Enterprise Linux 9 Reporter: Mingyu Shi <mshi>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.2CC: ferferna, jiji, jishi, network-qe, sfaye, till
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nmstate-2.2.5-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 07:31:53 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 Flags
NMtrace.log none

Description Mingyu Shi 2022-12-21 02:50:16 UTC 
Created attachment 1933862 [details]
NMtrace.log

Description of problem:
Failed to move ovs port to linux bridge and bond, it's an extend test of https://bugzilla.redhat.com/show_bug.cgi?id=2121315

Version-Release number of selected component (if applicable):
nmstate-2.2.2-2.el9.x86_64
NetworkManager-1.41.6-1.el9.x86_64
openvswitch2.15-2.15.0-76.el9fdp.x86_64
DISTRO=RHEL-9.2.0-20221220.0

How reproducible:
100%

Steps to Reproduce:
echo 'interfaces:
- name: ovs-br0
  type: ovs-bridge
  state: up
  bridge:
    port:
    - name: veth0
    - name: ovs-bond0
      link-aggregation:
        mode: balance-slb
        port:
        - name: veth2
        - name: veth1
        - name: veth4
        - name: veth3
- name: veth0
  type: veth
  state: up
  veth:
    peer: veth0_p
- name: veth3
  type: veth
  state: up
  veth:
    peer: veth3_p
- name: veth2
  type: veth
  state: up
  veth:
    peer: veth2_p
- name: veth1
  type: veth
  state: up
  veth:
    peer: veth1_p
- name: veth4
  type: veth
  state: up
  veth:
    peer: veth4_p' | nmstatectl apply

echo 'interfaces:
- name: ovs-br0
  type: ovs-bridge
  state: up
  bridge:
    port:
    - name: ovs-bond0
      link-aggregation:
        mode: balance-slb
        port:
        - name: veth2
        - name: veth3
- name: br0
  type: linux-bridge
  state: up
  bridge:
    port:
    - name: veth0
      vlan:
        mode: access
        tag: 305
- name: bond0
  type: bond
  state: up
  link-aggregation:
    mode: balance-rr
    port:
    - veth4
    - veth1
  ipv4:
    enabled: true
    address:
    - ip: 192.168.199.1
      prefix-length: 24
  ipv6:
    enabled: true
    address:
    - ip: 192:168:199::1
      prefix-length: 64' | nmstatectl apply

Actual results:
[2022-12-21T02:39:40Z WARN  nmstate::query_apply::net_state] nm_checkpoint_rollback() failed: Bug: DbusConnectionError: org.freedesktop.NetworkManager.InvalidArguments: checkpoint /org/freedesktop/NetworkManager/Checkpoint/10 does not exist
[2022-12-21T02:39:40Z INFO  nmstate::query_apply::net_state] Rollbacked to checkpoint /org/freedesktop/NetworkManager/Checkpoint/10
NmstateError: Bug: NotFound: Connection with UUID 696339a2-dcab-4c85-851c-fb83e4ac7e35 not found

Failed, and after rollback, all ovs and veth were removed 

Expected results:
No failure

Additional info:
Comment 1 Mingyu Shi 2022-12-21 02:55:04 UTC 
The key is moving to bond0,
moving to br0 works fine.
Comment 2 Gris Ge 2023-01-12 08:39:47 UTC 
Patch sent to upstream: https://github.com/nmstate/nmstate/pull/2193
Comment 5 Mingyu Shi 2023-01-31 13:06:02 UTC 
Verified with:
nmstate-2.2.5-1.el9.x86_64
nispor-1.2.9-1.el9.x86_64
NetworkManager-1.41.90-1.el9.x86_64
openvswitch2.15-2.15.0-79.el9fdp.x86_64
DISTRO=RHEL-9.2.0-20230127.12
Comment 7 errata-xmlrpc 2023-05-09 07:31:53 UTC 
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-2023:2190