Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1734754[details]
verification
Verified with versions:
nmstate-0.3.4-15.el8_3.noarch
NetworkManager-1.26.0-9.el8_3.x86_64
DISTRO=RHEL-8.3.0-updates-20201031.0
Linux dell-r330-6.gsslab.brq.redhat.com 4.18.0-240.1.1.el8_3.x86_64 #1 SMP Fri Oct 16 13:36:46 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux
python3-openvswitch2.13-2.13.0-39.el8fdp.x86_64
openvswitch-selinux-extra-policy-1.0-22.el8fdp.noarch
openvswitch2.13-2.13.0-39.el8fdp.x86_64
nmstate-plugin-ovsdb-0.3.4-15.el8_3.noarch
To reproduce, you need to have NetworkManager-ovs installed on the HOST, otherwise NM would regard ovs devices as common interfaces(type unknown for nmstate). Verify within a container, do the following on the host:
dnf install podman NetworkManager NetworkManager-ovs openvswitch2.11 ## or 2.13
systemctl start openvswitch
systemctl restart NetworkManager
ovs-vsctl add-br br0
ovs-vsctl add-port br0 vxlan1 -- set interface vxlan1 type=vxlan options:remote_ip=192.168.1.2 options:key=flow options:dst_port=8472
podman run --network=host --privileged -it --volume /run/dbus/system_bus_socket:/run/dbus/system_bus_socket centos:8 bash -c "dnf install -b -y dnf-plugins-core && dnf copr enable -y networkmanager/NetworkManager-1.26 && dnf install -y $nmstate_fixed_version && nmstatectl show"
Or on the host, install the fixed version and nmstate, modify this function(in libnmstate/ifaces/ovs.py)
def is_ovs_running():
try:
subprocess.run(
("systemctl", "status", "openvswitch"),
...
to replace 'openvswitch' with any text of a fake process. Running 'nmstatectl show', no failure. But notice that you still cannot use nmstate to commit a change of ovs things.
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-2020:5488
Created attachment 1734754 [details] verification Verified with versions: nmstate-0.3.4-15.el8_3.noarch NetworkManager-1.26.0-9.el8_3.x86_64 DISTRO=RHEL-8.3.0-updates-20201031.0 Linux dell-r330-6.gsslab.brq.redhat.com 4.18.0-240.1.1.el8_3.x86_64 #1 SMP Fri Oct 16 13:36:46 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux python3-openvswitch2.13-2.13.0-39.el8fdp.x86_64 openvswitch-selinux-extra-policy-1.0-22.el8fdp.noarch openvswitch2.13-2.13.0-39.el8fdp.x86_64 nmstate-plugin-ovsdb-0.3.4-15.el8_3.noarch To reproduce, you need to have NetworkManager-ovs installed on the HOST, otherwise NM would regard ovs devices as common interfaces(type unknown for nmstate). Verify within a container, do the following on the host: dnf install podman NetworkManager NetworkManager-ovs openvswitch2.11 ## or 2.13 systemctl start openvswitch systemctl restart NetworkManager ovs-vsctl add-br br0 ovs-vsctl add-port br0 vxlan1 -- set interface vxlan1 type=vxlan options:remote_ip=192.168.1.2 options:key=flow options:dst_port=8472 podman run --network=host --privileged -it --volume /run/dbus/system_bus_socket:/run/dbus/system_bus_socket centos:8 bash -c "dnf install -b -y dnf-plugins-core && dnf copr enable -y networkmanager/NetworkManager-1.26 && dnf install -y $nmstate_fixed_version && nmstatectl show" Or on the host, install the fixed version and nmstate, modify this function(in libnmstate/ifaces/ovs.py) def is_ovs_running(): try: subprocess.run( ("systemctl", "status", "openvswitch"), ... to replace 'openvswitch' with any text of a fake process. Running 'nmstatectl show', no failure. But notice that you still cannot use nmstate to commit a change of ovs things.