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.

nmstate-plugin-ovsdb has been added in AppStream for RHEL 8 via BZ #1847229 .
It's missing in RHEL 9.0 and it's required for running oVirt on RHEL 9.

The package is included in CentOS Stream 9.

The ovsdb is not a plugin anymore in RHEL 9 but embedded into libnmstate as we rewrite nmstate into rust.

The rpm SPEC has `Obsoletes: nmstate-plugin-ovsdb < 2.1-1`, so upgrading from RHEL 8 should still works.

Could you check again?

(In reply to Gris Ge from comment #1)
> The ovsdb is not a plugin anymore in RHEL 9 but embedded into libnmstate as
> we rewrite nmstate into rust.
> 
> The rpm SPEC has `Obsoletes: nmstate-plugin-ovsdb < 2.1-1`, so upgrading
> from RHEL 8 should still works.
> 
> Could you check again?

Is this documented somewhere? I'll open an oVirt bug about this change.

rpm -qv python3-libnmstate
python3-libnmstate-2.1.1-0.alpha.20220519.437e4a9.el9.x86_64

rpm -q --obsoletes python3-libnmstate
nmstate-plugin-ovsdb < 2.1-1
python39-libnmstate < 2.1.1-0.alpha.20220519.437e4a9.el9

But in RHEL 9.0 it was shipped 2.0.0-2 which has:

Provides	
python-libnmstate = 2.0.0-2.el9
python3-libnmstate = 2.0.0-2.el9
python3.9-libnmstate = 2.0.0-2.el9
python3.9dist(nmstate) = 2
python3dist(nmstate) = 2
Obsoletes	
python39-libnmstate < 2.0.0-2.el9

So, 9.0 is still broken.

oVirt tracker: https://github.com/oVirt/vdsm/issues/219

Hi Sandro,

In RHEL 9.0, you still have `nmstate-plugin-ovsdb.noarch` in the AppStream, it should works as it was in RHEL 8.