Activity log for bug #1877884

Date Who What changed Old value New value Message
2020-05-10 18:07:11 Kathryn Morgan bug added bug
2020-05-10 18:08:30 Kathryn Morgan description Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected: Running the following: `nmcli con up ovs-mgmt1` `nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal` Should raise the ovs interface(es) defined. Actual results: `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable` `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable` `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument: As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli con up ovs-mgmt1     nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager.
2020-05-10 18:09:12 Kathryn Morgan description Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli con up ovs-mgmt1     nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli con up ovs-mgmt1     nmcli connection add type ovs-interface \ con-name mgmt1 ifname mgmt1 \ ip4 192.168.16.2/24 gw4 192.168.16.1 master internal ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager.
2020-05-10 18:09:35 Kathryn Morgan description Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli con up ovs-mgmt1     nmcli connection add type ovs-interface \ con-name mgmt1 ifname mgmt1 \ ip4 192.168.16.2/24 gw4 192.168.16.1 master internal ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli connection add type ovs-interface \       con-name mgmt1 ifname mgmt1 \       ip4 192.168.16.2/24 gw4 192.168.16.1 master internal nmcli con up ovs-mgmt1 ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager.
2020-05-10 18:10:33 Kathryn Morgan summary OpenVSwitch support: no package for `nm-openvswitch` OpenVSwitch Support: no package for `nm-openvswitch`
2020-05-10 18:11:05 Kathryn Morgan description Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli connection add type ovs-interface \       con-name mgmt1 ifname mgmt1 \       ip4 192.168.16.2/24 gw4 192.168.16.1 master internal nmcli con up ovs-mgmt1 ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli connection add type ovs-interface \       con-name mgmt1 ifname mgmt1 \       ip4 192.168.16.2/24 gw4 192.168.16.1 master internal     nmcli con up ovs-mgmt1 ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Expected part of GNOME: https://developer.gnome.org/NetworkManager/stable/nm-openvswitch.html
2020-05-10 18:11:19 Kathryn Morgan description Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli connection add type ovs-interface \       con-name mgmt1 ifname mgmt1 \       ip4 192.168.16.2/24 gw4 192.168.16.1 master internal     nmcli con up ovs-mgmt1 ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Expected part of GNOME: https://developer.gnome.org/NetworkManager/stable/nm-openvswitch.html Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli connection add type ovs-interface \       con-name mgmt1 ifname mgmt1 \       ip4 192.168.16.2/24 gw4 192.168.16.1 master internal     nmcli con up ovs-mgmt1 ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Expected component of GNOME: https://developer.gnome.org/NetworkManager/stable/nm-openvswitch.html
2020-05-10 18:13:14 Kathryn Morgan description Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following: ```     nmcli connection add type ovs-interface \       con-name mgmt1 ifname mgmt1 \       ip4 192.168.16.2/24 gw4 192.168.16.1 master internal     nmcli con up ovs-mgmt1 ```   Should raise the ovs interface(es) defined. Actual results:     `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Expected component of GNOME: https://developer.gnome.org/NetworkManager/stable/nm-openvswitch.html Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following:     `nmcli con up ovs-mgmt1`     `nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal`   Should raise the ovs interface(es) defined. Actual results:     `Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager.
2020-05-10 18:13:48 Kathryn Morgan description Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following:     `nmcli con up ovs-mgmt1`     `nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal`   Should raise the ovs interface(es) defined. Actual results:     `Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`     `Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`     `Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following:     `nmcli con up ovs-mgmt1`     `nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal`   Should raise the ovs interface(es) defined. Actual results:   `Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`   `Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`   `Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager.
2020-05-10 18:14:09 Kathryn Morgan description Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following:     `nmcli con up ovs-mgmt1`     `nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal`   Should raise the ovs interface(es) defined. Actual results:   `Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable`   `Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`   `Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected:   Running the following:     `nmcli con up ovs-mgmt1`     `nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal`   Should raise the ovs interface(es) defined. Actual results: `Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable` `Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable`   `Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument:   As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager.
2020-05-11 13:41:57 Sebastien Bacher network-manager (Ubuntu): importance Undecided Wishlist
2020-05-11 13:42:00 Sebastien Bacher network-manager (Ubuntu): status New Triaged