Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot detach OVS system interface from OVS bridge #809

Closed
cathay4t opened this issue Feb 18, 2020 · 3 comments
Closed

Cannot detach OVS system interface from OVS bridge #809

cathay4t opened this issue Feb 18, 2020 · 3 comments

Comments

@cathay4t
Copy link
Member

cathay4t commented Feb 18, 2020

Due to NetworkMaanager bug https://bugzilla.redhat.com/show_bug.cgi?id=1804167 we cannot
detach system interface from OVS bridge.

Test case test_create_and_remove_ovs_bridge_with_a_system_port will show the
system interface as down state after removing the OVS bridge. It could be related to this
issue as interface cannot detach from OVS bridge.

@cathay4t
Copy link
Member Author

To test this issue, apply these two yml files sequentially:

---
interfaces:
- name: eth1
  type: ethernet
  state: up
- name: br0
  type: ovs-bridge
  state: up
  bridge:
    port:
    - name: ovs0
    - name: eth1
- name: ovs0
  type: ovs-interface
  state: up

Then

---
interfaces:
- name: br0
  type: ovs-bridge
  state: up
  bridge:
    port:
    - name: ovs0

@ffmancera ffmancera self-assigned this Feb 18, 2020
cathay4t added a commit to cathay4t/nmstate that referenced this issue Feb 18, 2020
With NM 1.22.8, the OVS is stable now except modifying existing
OVS ports which fails the
`test_create_and_remove_ovs_bridge_with_a_system_port` test due to

    nmstate#809

Signed-off-by: Gris Ge <fge@redhat.com>
@cathay4t
Copy link
Member Author

This is resolved by NM in NetworkManager-1.22.8

@cathay4t cathay4t changed the title Cannot deattach OVS system interface from OVS bridge Cannot detach OVS system interface from OVS bridge Feb 19, 2020
@cathay4t
Copy link
Member Author

This issue is only fixed after NM 1.22.8 released. So currently our CI still fail on this test case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants