Bug 1988507

Summary: VDSM cannot update due to missing openvswitch versions on ppc64le architecture
Product: Red Hat Enterprise Virtualization Manager Reporter: Vinícius Ferrão <vinicius>
Component: distributionAssignee: Martin Tessun <mtessun>
Status: CLOSED NOTABUG QA Contact: Lukas Svaty <lsvaty>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4.7CC: amusil, bugs, daturece, liliu, lsurette, mburman, mhicks, michal.skrivanek, mperina, mtessun, sbonazzo, soliu, srevivo, the
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-17 10:13:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Rel-Eng RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vinícius Ferrão 2021-07-30 17:09:30 UTC 
Description of problem:
VDSM fails to update due to missing openvswitch and/or incompatible package

Version-Release number of selected component (if applicable):
vdsm-hook-vhostmd-4.40.70.6-1.el8ev.noarch
vdsm-http-4.40.35.1-1.el8ev.noarch
vdsm-api-4.40.35.1-1.el8ev.noarch
vdsm-network-4.40.35.1-1.el8ev.ppc64le
vdsm-hook-fcoe-4.40.35.1-1.el8ev.noarch
vdsm-hook-openstacknet-4.40.70.6-1.el8ev.noarch
vdsm-common-4.40.35.1-1.el8ev.noarch
vdsm-hook-vmfex-dev-4.40.35.1-1.el8ev.noarch
vdsm-yajsonrpc-4.40.35.1-1.el8ev.noarch
vdsm-python-4.40.35.1-1.el8ev.noarch
vdsm-client-4.40.35.1-1.el8ev.noarch
vdsm-4.40.35.1-1.el8ev.ppc64le
vdsm-jsonrpc-4.40.35.1-1.el8ev.noarch
vdsm-hook-ethtool-options-4.40.35.1-1.el8ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Try to do an upgrade on RHV 4.4 running on ppc64le

Actual results:
Fails to update RHV

Expected results:
Proper upgrade of RHV

Additional info:

openvswitch seems to be totally missing:

[root@rhvpower ~]# dnf install rhv-openvswitch
Updating Subscription Management repositories.
Last metadata expiration check: 2:37:40 ago on Fri 30 Jul 2021 10:27:39 AM EDT.
Error: 
 Problem: cannot install the best candidate for the job
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

During the dnf update phase this happens:
[root@rhvpower ~]# dnf update
Updating Subscription Management repositories.
Last metadata expiration check: 2:28:31 ago on Fri 30 Jul 2021 10:27:39 AM EDT.
Error: 
 Problem 1: package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-network-4.40.35.1-1.el8ev.ppc64le
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 2: package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-python-4.40.35.1-1.el8ev.noarch
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 3: package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-4.40.70.6-1.el8ev.ppc64le requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-4.40.35.1-1.el8ev.ppc64le
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 4: package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-client-4.40.70.6-1.el8ev.noarch requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-client-4.40.35.1-1.el8ev.noarch
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 5: package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-4.40.70.6-1.el8ev.ppc64le requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-hook-vmfex-dev-4.40.35.1-1.el8ev.noarch
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 6: package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-http-4.40.70.6-1.el8ev.noarch requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-http-4.40.35.1-1.el8ev.noarch
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 7: package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-jsonrpc-4.40.70.6-1.el8ev.noarch requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-jsonrpc-4.40.35.1-1.el8ev.noarch
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 8: package vdsm-4.40.70.6-1.el8ev.ppc64le requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-hook-ethtool-options-4.40.70.6-1.el8ev.noarch requires vdsm = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-hook-ethtool-options-4.40.35.1-1.el8ev.noarch
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 9: package vdsm-4.40.70.6-1.el8ev.ppc64le requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-hook-fcoe-4.40.70.6-1.el8ev.noarch requires vdsm = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-hook-fcoe-4.40.35.1-1.el8ev.noarch
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 10: package ovirt-host-dependencies-4.4.7-1.el8ev.ppc64le requires vdsm-client >= 4.40.60, but none of the providers can be installed
  - package vdsm-client-4.40.70.6-1.el8ev.noarch requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-client-4.40.60.6-1.el8ev.noarch requires vdsm-api = 4.40.60.6-1.el8ev, but none of the providers can be installed
  - package vdsm-client-4.40.60.7-1.el8ev.noarch requires vdsm-api = 4.40.60.7-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - cannot install both vdsm-api-4.40.70.6-1.el8ev.noarch and vdsm-api-4.40.60.6-1.el8ev.noarch
  - cannot install both vdsm-api-4.40.70.6-1.el8ev.noarch and vdsm-api-4.40.60.7-1.el8ev.noarch
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-api-4.40.35.1-1.el8ev.noarch
  - cannot install the best update candidate for package ovirt-host-dependencies-4.4.1-4.el8ev.ppc64le
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 11: problem with installed package vdsm-python-4.40.35.1-1.el8ev.noarch
  - package vdsm-python-4.40.35.1-1.el8ev.noarch requires vdsm-common = 4.40.35.1-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.40-1.el8ev.noarch requires vdsm-network = 4.40.40-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.50.8-1.el8ev.noarch requires vdsm-network = 4.40.50.8-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.50.10-1.el8ev.noarch requires vdsm-network = 4.40.50.10-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.60.6-1.el8ev.noarch requires vdsm-network = 4.40.60.6-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.60.7-1.el8ev.noarch requires vdsm-network = 4.40.60.7-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - cannot install both vdsm-common-4.40.70.6-1.el8ev.noarch and vdsm-common-4.40.35.1-1.el8ev.noarch
  - package vdsm-network-4.40.40-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - package vdsm-network-4.40.50.8-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - package vdsm-network-4.40.50.10-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - package vdsm-network-4.40.60.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - package vdsm-network-4.40.60.7-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-common-4.40.35.1-1.el8ev.noarch
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 12: package ovirt-host-dependencies-4.4.7-1.el8ev.ppc64le requires vdsm-client >= 4.40.60, but none of the providers can be installed
  - package vdsm-client-4.40.70.6-1.el8ev.noarch requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package vdsm-client-4.40.60.6-1.el8ev.noarch requires vdsm-yajsonrpc = 4.40.60.6-1.el8ev, but none of the providers can be installed
  - package vdsm-client-4.40.60.7-1.el8ev.noarch requires vdsm-yajsonrpc = 4.40.60.7-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - cannot install both vdsm-yajsonrpc-4.40.70.6-1.el8ev.noarch and vdsm-yajsonrpc-4.40.60.6-1.el8ev.noarch
  - cannot install both vdsm-yajsonrpc-4.40.70.6-1.el8ev.noarch and vdsm-yajsonrpc-4.40.60.7-1.el8ev.noarch
  - package ovirt-host-4.4.7-1.el8ev.ppc64le requires ovirt-host-dependencies = 4.4.7-1.el8ev, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package vdsm-yajsonrpc-4.40.35.1-1.el8ev.noarch
  - cannot install the best update candidate for package ovirt-host-4.4.1-4.el8ev.ppc64le
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
 Problem 13: problem with installed package ovirt-host-4.4.1-4.el8ev.ppc64le
  - package ovirt-host-4.4.5-1.el8ev.ppc64le requires ovirt-host-dependencies = 4.4.5-1.el8ev, but none of the providers can be installed
  - package ovirt-host-4.4.6-1.el8ev.ppc64le requires ovirt-host-dependencies = 4.4.6-1.el8ev, but none of the providers can be installed
  - package ovirt-host-4.4.7-1.el8ev.ppc64le requires ovirt-host-dependencies = 4.4.7-1.el8ev, but none of the providers can be installed
  - package ovirt-host-dependencies-4.4.5-1.el8ev.ppc64le requires vdsm-client >= 4.40.50, but none of the providers can be installed
  - package ovirt-host-dependencies-4.4.6-1.el8ev.ppc64le requires vdsm-client >= 4.40.60, but none of the providers can be installed
  - package ovirt-host-dependencies-4.4.7-1.el8ev.ppc64le requires vdsm-client >= 4.40.60, but none of the providers can be installed
  - package vdsm-client-4.40.50.8-1.el8ev.noarch requires vdsm-python = 4.40.50.8-1.el8ev, but none of the providers can be installed
  - package vdsm-client-4.40.50.10-1.el8ev.noarch requires vdsm-python = 4.40.50.10-1.el8ev, but none of the providers can be installed
  - package vdsm-client-4.40.60.6-1.el8ev.noarch requires vdsm-python = 4.40.60.6-1.el8ev, but none of the providers can be installed
  - package vdsm-client-4.40.60.7-1.el8ev.noarch requires vdsm-python = 4.40.60.7-1.el8ev, but none of the providers can be installed
  - package vdsm-client-4.40.70.6-1.el8ev.noarch requires vdsm-python = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package ovirt-host-4.4.1-4.el8ev.ppc64le requires cockpit-dashboard, but none of the providers can be installed
  - package vdsm-python-4.40.50.8-1.el8ev.noarch requires vdsm-network = 4.40.50.8-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.50.10-1.el8ev.noarch requires vdsm-network = 4.40.50.10-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.60.6-1.el8ev.noarch requires vdsm-network = 4.40.60.6-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.60.7-1.el8ev.noarch requires vdsm-network = 4.40.60.7-1.el8ev, but none of the providers can be installed
  - package vdsm-python-4.40.70.6-1.el8ev.noarch requires vdsm-network = 4.40.70.6-1.el8ev, but none of the providers can be installed
  - package cockpit-bridge-238.2-1.el8.ppc64le conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-224.2-1.el8.noarch
  - package cockpit-bridge-238.2-1.el8.ppc64le conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-184.1-1.el8.noarch
  - package cockpit-bridge-238.2-1.el8.ppc64le conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-197.3-1.el8.noarch
  - package cockpit-bridge-238.2-1.el8.ppc64le conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-211.3-1.el8.noarch
  - package vdsm-network-4.40.50.8-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - package vdsm-network-4.40.50.10-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - package vdsm-network-4.40.60.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - package vdsm-network-4.40.60.7-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - package vdsm-network-4.40.70.6-1.el8ev.ppc64le requires openvswitch >= 2.11, but none of the providers can be installed
  - cannot install the best update candidate for package cockpit-bridge-224.2-1.el8.ppc64le
  - nothing provides openvswitch2.11 needed by rhv-openvswitch-1:2.11-7.el8ev.noarch
  - nothing provides openvswitch2.11 needed by ovirt-openvswitch-2.11-1.el8ev.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)


Those are the enabled repositories on the machine:
[root@rhvpower ~]# dnf repolist
Updating Subscription Management repositories.
repo id                                                    repo name
advanced-virt-for-rhel-8-ppc64le-rpms                      Advanced Virtualization for RHEL 8 Power, little endian (RPMs)
ansible-2.9-for-rhel-8-ppc64le-rpms                        Red Hat Ansible Engine 2.9 for RHEL 8 ppc64le (RPMs)
codeready-builder-for-rhel-8-ppc64le-rpms                  Red Hat CodeReady Linux Builder for RHEL 8 Power, little endian (RPMs)
cuda-rhel8-ppc64le                                         cuda-rhel8-ppc64le
epel                                                       Extra Packages for Enterprise Linux 8 - ppc64le
epel-modular                                               Extra Packages for Enterprise Linux Modular 8 - ppc64le
mlnx_ofed_5.4-1.0.3.0_base                                 Mellanox Technologies rhel8.4-ppc64le mlnx_ofed 5.4-1.0.3.0 GA
rhel-8-for-ppc64le-appstream-rpms                          Red Hat Enterprise Linux 8 for Power, little endian - AppStream (RPMs)
rhel-8-for-ppc64le-baseos-rpms                             Red Hat Enterprise Linux 8 for Power, little endian - BaseOS (RPMs)
rhv-4-mgmt-agent-for-rhel-8-ppc64le-rpms                   Red Hat Virtualization 4 Management Agents for RHEL 8 Power, little endian (RPMs)


For self repairs, I've already trying reseting the virt module and enabling it after. But it had no effect on fixing the issue.

Thanks.
Comment 1 RHEL Program Management 2021-08-02 06:51:38 UTC 
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Comment 2 Ales Musil 2021-08-03 05:26:33 UTC 
Hi,

it seems like you are completely missing FDP repository on this host.

Sandro, can someone from your team please take look? 

Thanks,
Ales
Comment 3 Vinícius Ferrão 2021-08-03 17:06:51 UTC 
Hi Ales, in fact FDP is totally missing on ppc64le. I've checked on subscription manager, and on ppc64le is has available only the beta repositories:

Repo ID:   fast-datapath-beta-for-rhel-8-ppc64le-rpms
Repo Name: Fast Datapath Beta for RHEL 8 Power, little endian (RPMs)
Repo URL:  https://cdn.redhat.com/content/beta/layered/rhel8/ppc64le/fast-datapath/os
Enabled:   0

Repo ID:   fast-datapath-beta-for-rhel-8-ppc64le-debug-rpms
Repo Name: Fast Datapath Beta for RHEL 8 Power, little endian (Debug RPMs)
Repo URL:  https://cdn.redhat.com/content/beta/layered/rhel8/ppc64le/fast-datapath/debug
Enabled:   0

Repo ID:   fast-datapath-beta-for-rhel-8-ppc64le-source-rpms
Repo Name: Fast Datapath Beta for RHEL 8 Power, little endian (Source RPMs)
Repo URL:  https://cdn.redhat.com/content/beta/layered/rhel8/ppc64le/fast-datapath/source/SRPMS
Enabled:   0

On x86_64, FDP is available and enabled:

Repo ID:   fast-datapath-for-rhel-8-x86_64-rpms
Repo Name: Fast Datapath for RHEL 8 x86_64 (RPMs)
Repo URL:  https://cdn.redhat.com/content/dist/layered/rhel8/x86_64/fast-datapath/os
Enabled:   1

Thanks.
Comment 4 Vinícius Ferrão 2021-08-03 17:28:45 UTC 
Alright, it seems to be a license related issue.

The system have the proper license, but "Red Hat Virtualization Manager for Power" is not enabled on it since the machine isn't the manager. But FDP for ppc64le is available on "Red Hat Virtualization Manager for Power" (SKU RV00099), so I've attached this subscription to the host and was able to start the upgrade process. It's running right now.

Installing dependencies:
 nmstate-plugin-ovsdb                         noarch              1.0.2-11.el8_4                  rhel-8-for-ppc64le-appstream-rpms                     22 k
 nsight-compute-2021.2.1                      ppc64le             2021.2.1.2-1                    cuda-rhel8-ppc64le                                    73 M
 openvswitch-selinux-extra-policy             noarch              1.0-28.el8fdp                   fast-datapath-for-rhel-8-ppc64le-rpms                 16 k
 openvswitch2.11                              ppc64le             2.11.3-86.el8fdp                fast-datapath-for-rhel-8-ppc64le-rpms                 12 M
 ovirt-openvswitch                            noarch              2.11-1.el8ev                    rhv-4-mgmt-agent-for-rhel-8-ppc64le-rpms             8.7 k
 ovirt-python-openvswitch                     noarch              2.11-1.el8ev                    rhv-4-mgmt-agent-for-rhel-8-ppc64le-rpms             7.7 k
 python3-openvswitch2.11                      ppc64le             2.11.3-86.el8fdp                fast-datapath-for-rhel-8-ppc64le-rpms                265 k
Installing weak dependencies:
 network-scripts-openvswitch2.11              ppc64le             2.11.3-86.el8fdp                fast-datapath-for-rhel-8-ppc64le-rpms                 54 k

SKU RH3387200 should have FDP enabled, but it only have FDP Beta enabled. The issue nails down to it.

As the end of this writing the upgrade process completed successfully.
Comment 11 Michal Skrivanek 2022-01-13 13:42:40 UTC 
Hi, is there anything else to follow up on in this bug, or is comment #8 good enough and we can close this?
Comment 12 Vinícius Ferrão 2022-01-13 16:13:46 UTC 
Hi Michal, I can't see comment #8. It seems to be RH Internal.
Comment 13 Michal Skrivanek 2022-01-17 12:45:18 UTC 
huh, I thought you do...so then the updates that happened some time ago were not really that useful if you haven't seen them:/

The comment is that RH3387200 is not in the list that has FDP, meanwhile RV00099 is in. It should be by design. If you want RH3387200 to also contain the FDP channels you'd need o talk to Product Management or whoever you got the subscription from. 

@mtessun - it looks like misconfiguration to me, but it could be that it's just a wrong SKU (see comment #6)
Comment 14 Vinícius Ferrão 2022-01-26 18:45:36 UTC 
The subscription came from Red Hat Technology Partner channel, it's a NFR subscription. So something should be fixed directly by RH, right? Is there anywhere I can report this?

Thank you.
Comment 15 Liu Song 2022-01-27 02:56:43 UTC 
@Vincius Which subscription do you use in x86_64?

I think both Fast Datapath and Fast Datapath Beta should exist in RH3387200, or neither of them exists in RH3387200. Only including Beta content in a subscription is weird. 
Let's ask the RHV product marketing manager Gerry Riveros for details.
Another way is to file a ticket in Red Hat Salesforce.
Comment 18 the 2022-02-24 08:30:01 UTC 
Abstract the content from comment #16 as this ticket is raised by external customer and they cannot see private reply.

After consulted with Business Operations, the conclusion is that neither PID 474 (FDP for Power LE) nor 475 (FDP Beta for Power LE) should be contained in any RHEL SKU including RH3387200. Supporting material: https://access.redhat.com/articles/3538141

The workflow to remove PID 475 (FDP Beta for Power LE) will go through an internal process and would not be tracked here.

Hence, closing this bug as not a bug.