Description of problem: Right now, ovirt-openvswitch Provides: openvswitch, and other oVirt components refer to 'openvswitch'. This was done because the original openvswitch package was renamed to have major.minor in the package name (not (only) version). This is confusing and misleading. All oVirt components should instead use ovirt-openvswitch directly, and ovirt-openvswitch itself should stop providing openvswitch. See also the discussion on https://gerrit.ovirt.org/c/ovirt-engine/+/115208 .
All packages were changed to explicitly require ovirt-openvswitch, unortunately python3-ovsdbapp which is not our package still relies on this implicit provide. Changing the title to reflect what was done and closing as NEXTRELEASE.
Sorry, I do not understand - if openvswitch package _name_ now includes the version, how can you use python3-ovsdbapp without oVirt (ovirt-openvswitch)? Are we the only users of it? If so, it should be changed as well. Otherwise, is there some other non-oVirt package that Provides: openvswitch? Perhaps we should conflict with it somewhere or something like that. Please clarify the situation and mention any relevant open bugs remaining. Thanks!
ovsdbapp comes from OpenStack, I would not be surprised if they are using some similar system. I don't know about any package that would conflict with ours. It might be possible that this require remains from times when openvswitch version was not part of the package.
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.