Skip to content

Avoid removing tap interfaces connected to a standard Linux bridge #17

@eroussy

Description

@eroussy

Abstract
When it runs, python3-setup-ovs first removes all the tap interfaces on the machine (except those declared in ignored_taps)
But this also means that it will remove tap interfaces on standard Linux bridges, i.e: bridges that are not handled by Open vSwitch.
I propose to modify the tool so that it removes only tap interfaces on OVS bridges

Concrete problem example
When a VM is already running on the hypervisor, it is connected to the br0 administration bridge by default:

root@hypervisor:~# brctl show
bridge name	  bridge id		  STP enabled	interfaces
br0		      8000.fa6836a3	  no		    eno1
							                vnet0

If you try to deploy an OVS bridge on this hypervisor, it will fail because it tries to remove vnet0 which is in use.
You will have to manually declare ignored_taps: ["vnet0"] in your inventory.

The user should not have to worry about that, thus python3-setup-ovs should not try to remove vnet0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions