Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Bug 2085446

Summary: LEAPP preupgrade --target 8.6 fails to resolve conflicts for rubygem-openscap
Product: Red Hat Satellite Reporter: Gaurav Talreja <gtalreja>
Component: PackagingAssignee: Evgeni Golov <egolov>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: egolov, pmendezh
Target Milestone: 6.11.0Keywords: Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: tfm-rubygem-openscap-0.4.9-7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-05 14:35:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gaurav Talreja 2022-05-13 11:47:10 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
Satellite 6.11.0

How reproducible:
Always

Steps to Reproduce:
1. Install LEAPP and setup satellite rhel8 repositories 
2. Run LEAPP preupgrade

# leapp preupgrade --target 8.6 --enablerepo sat-maintain_el8 --enablerepo sat_el8
.
============================================================
                           ERRORS
============================================================

2022-05-13 05:46:45.107012 [ERROR] Actor: dnf_transaction_check
Message: DNF execution failed with non zero exit code.
STDOUT:
Last metadata expiration check: 0:01:23 ago on Fri May 13 05:45:07 2022.
Package foreman-installer-katello-1:3.1.2.2-2.el7sat.noarch is already installed.
Package tfm-pulpcore-python3-createrepo_c-0.17.7-5.1.el7pc.x86_64 is already installed.
Package rubygem-foreman_maintain-1:1.0.10-1.el7sat.noarch is already installed.
Package satellite-installer-6.11.0.7-1.el7sat.noarch is already installed.
Package katello-4.3.0-1.el7sat.noarch is already installed.
Package foreman-installer-1:3.1.2.2-2.el7sat.noarch is already installed.
Package createrepo_c-0.17.7-5.1.el7pc.x86_64 is already installed.

STDERR:
Warning: Package marked by Leapp to install not found in repositories metadata: rubygem-foreman_ansible_core rubygem-foreman-tasks-core boost-python3-devel boost-python3 rubygem-foreman_remote_execution_core log4j12
Warning: Package marked by Leapp to upgrade not found in repositories metadata: gpg-pubkey python2-leapp leapp-upgrade-el7toel8 leapp
Transaction check:

 Problem 1: package rubygem-smart_proxy_ansible-3.3.1-1.el8sat.noarch requires ansible >= 2.2, but none of the providers can be installed
  - cannot install the best update candidate for package ansible-2.9.27-1.el7ae.noarch
  - cannot install the best update candidate for package ansible-test-2.9.27-1.el7ae.noarch
  - package python38-galaxy-importer-0.4.1-2.el8pc.noarch requires /usr/bin/ansible-test, but none of the providers can be installed
  - package ansible-test-2.12.2-3.1.el8.x86_64 requires ansible-core = 2.12.2-3.1.el8, but none of the providers can be installed
  - package ansible-test-2.9.0-2.el8.noarch requires ansible = 2.9.0-2.el8, but none of the providers can be installed
  - package ansible-test-2.9.1-1.el8.noarch requires ansible = 2.9.1-1.el8, but none of the providers can be installed
  - package ansible-test-2.9.2-1.el8ae.noarch requires ansible = 2.9.2-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.4-1.el8ae.noarch requires ansible = 2.9.4-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.5-1.el8ae.noarch requires ansible = 2.9.5-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.6-1.el8ae.noarch requires ansible = 2.9.6-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.7-1.el8ae.noarch requires ansible = 2.9.7-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.9-1.el8ae.noarch requires ansible = 2.9.9-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.10-1.el8ae.noarch requires ansible = 2.9.10-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.11-1.el8ae.noarch requires ansible = 2.9.11-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.13-1.el8ae.noarch requires ansible = 2.9.13-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.14-1.el8ae.noarch requires ansible = 2.9.14-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.15-1.el8ae.noarch requires ansible = 2.9.15-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.16-1.el8ae.noarch requires ansible = 2.9.16-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.17-1.el8ae.noarch requires ansible = 2.9.17-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.18-1.el8ae.noarch requires ansible = 2.9.18-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.19-1.el8ae.noarch requires ansible = 2.9.19-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.20-1.el8ae.noarch requires ansible = 2.9.20-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.21-1.el8ae.noarch requires ansible = 2.9.21-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.22-1.el8ae.noarch requires ansible = 2.9.22-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.23-1.el8ae.noarch requires ansible = 2.9.23-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.24-1.el8ae.noarch requires ansible = 2.9.24-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.25-1.el8ae.noarch requires ansible = 2.9.25-1.el8ae, but none of the providers can be installed
  - package ansible-test-2.9.26-1.el8ae.noarch requires ansible = 2.9.26-1.el8ae, but none of the providers can be installed
  - package ansible-core-2.12.2-3.1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.27-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.0-2.el8.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.1-1.el8.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.2-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.4-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.5-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.6-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.7-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.9-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.10-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.11-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.13-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.14-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.15-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.16-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.17-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.18-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.19-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.20-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.21-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.22-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.23-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.24-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.25-1.el8ae.noarch
  - cannot install both ansible-2.9.27-1.el8ae.noarch and ansible-2.9.26-1.el8ae.noarch
  - package python38-pulp-ansible-1:0.10.1-1.el8pc.noarch requires python38-galaxy-importer >= 0.3.1, but none of the providers can be installed
  - ansible-test-2.9.27-1.el7ae.noarch does not belong to a distupgrade repository
  - conflicting requests
  - ansible-2.9.27-1.el7ae.noarch does not belong to a distupgrade repository
 Problem 2: problem with installed package openscap-1.2.17-14.el7_9.x86_64
  - cannot install the best update candidate for package openscap-1.2.17-14.el7_9.x86_64
  - openscap-1.3.0-7.el8.i686 has inferior architecture
  - package rubygem-openscap-0.4.9-6.el8sat.noarch requires openscap < 1.3.6, but none of the providers can be installed
  - openscap-1.3.1-1.el8.i686 has inferior architecture
  - openscap-1.3.2-6.el8.i686 has inferior architecture
  - openscap-1.3.3-5.el8.i686 has inferior architecture
  - openscap-1.3.3-6.el8_3.i686 has inferior architecture
  - openscap-1.3.4-5.el8.i686 has inferior architecture
  - openscap-1.3.4-6.el8_4.i686 has inferior architecture
  - openscap-1.3.5-6.el8.i686 has inferior architecture
  - cannot install both openscap-1.3.6-3.el8.x86_64 and openscap-1.3.0-7.el8.x86_64
  - cannot install both openscap-1.3.6-3.el8.x86_64 and openscap-1.3.1-1.el8.x86_64
  - cannot install both openscap-1.3.6-3.el8.x86_64 and openscap-1.3.2-6.el8.x86_64
  - cannot install both openscap-1.3.6-3.el8.x86_64 and openscap-1.3.3-5.el8.x86_64
  - cannot install both openscap-1.3.6-3.el8.x86_64 and openscap-1.3.3-6.el8_3.x86_64
  - cannot install both openscap-1.3.6-3.el8.x86_64 and openscap-1.3.4-5.el8.x86_64
  - cannot install both openscap-1.3.6-3.el8.x86_64 and openscap-1.3.4-6.el8_4.x86_64
  - cannot install both openscap-1.3.6-3.el8.x86_64 and openscap-1.3.5-6.el8.x86_64
  - package rubygem-smart_proxy_openscap-0.9.2-1.el8sat.noarch requires rubygem(openscap) >= 0.4.7, but none of the providers can be installed
  - package rubygem-smart_proxy_openscap-0.9.2-1.el8sat.noarch requires rubygem(openscap) < 0.5, but none of the providers can be installed
  - package rubygem-smart_proxy_openscap-0.9.2-1.el8sat.noarch requires (rubygem(openscap) >= 0.4.7 with rubygem(openscap) < 0.5), but none of the providers can be installed
  - openscap-1.2.17-14.el7_9.x86_64 does not belong to a distupgrade repository
  - conflicting requests


============================================================
                       END OF ERRORS
============================================================

Actual results:
LEAPP preupgrade fails to resolve conflicts for 8.6

Expected results:
LEAPP preupgrade should pass

Additional info:
Problem1 with rubygem-smart_proxy_ansible seems already reported in BZ 2084624
Comment 1 Lukas Pramuk 2022-05-13 11:50:11 UTC 
rubygem-smart_proxy_ansible issue manifests even on fresh RHEL8 install and is already tracked by BZ 2084624
Comment 2 Lukas Pramuk 2022-05-21 21:26:16 UTC 
VERIFIED.

@Satellite 6.11.0 Snap21
rubygem-openscap-0.4.9-7.el8sat.noarch

by the following manual reproducer:

1) Have a Satellite 6.11 EL7

2) Install LEAPP and resolve all inhibitors

# subscription-manager repos --enable rhel-7-server-extras-rpms
# yum --disableplugin=foreman-protector -y install leapp

3) Apply the fix of BZ 2087144 (blocking BZ - do not enable ansible 2.9 el8 repo)

# rm -f /usr/share/leapp-repository/repositories/system_upgrade/el7toel8/actors/satellite_upgrade_facts/actor.py*
# wget -P /usr/share/leapp-repository/repositories/system_upgrade/el7toel8/actors/satellite_upgrade_facts https://github.com/oamg/leapp-repository/raw/ce02fa83a2f3cff089133ed9bb05dbdd6755132d/repos/system_upgrade/el7toel8/actors/satellite_upgrade_facts/actor.py

4) Setup Satellite 6.11 EL8 internal repos and run leapp preupgrade check

# leapp preupgrade --enablerepo satellite --enablerepo maintenance
...

============================================================
                           REPORT                           
============================================================

A report has been generated at /var/log/leapp/leapp-report.json
A report has been generated at /var/log/leapp/leapp-report.txt

============================================================
                       END OF REPORT                        
============================================================

Answerfile has been generated at /var/log/leapp/answerfile

>>> preupgrade check is successful no issues with openscap rpm
Comment 5 errata-xmlrpc 2022-07-05 14:35:42 UTC 
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 (Moderate: Satellite 6.11 Release), 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/RHSA-2022:5498