Bug 2089303 - LEAPP upgrade fails to resolve ansible dependencies on RHEL8.6
Summary: LEAPP upgrade fails to resolve ansible dependencies on RHEL8.6
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: sabuchan
QA Contact:
URL:
Whiteboard:
Depends On: 2087144
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-23 11:48 UTC by Brad Buckingham
Modified: 2022-07-27 07:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
*Leapp utility upgrade fails to resolve Ansible dependencies on RHEL 8.6* In-place upgrades from RHEL 7 to RHEL 8 fail to resolve Ansible dependencies on RHEL 8.6. To work around this, run `rpm -e ansible ansible-test --nodeps` prior to the in-place upgrade.
Clone Of: 2087144
Environment:
Last Closed: 2022-07-25 13:15:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SATDOC-913 0 None None None 2022-05-23 12:07:58 UTC
Red Hat Knowledge Base (Solution) 6965044 0 None None None 2022-06-28 15:19:36 UTC

Description Brad Buckingham 2022-05-23 11:48:05 UTC
This bugzilla is a clone of a bugzilla on RHEL LEAPP.  It is being created to ensure that the workaround described below is included in the Satellite 6.11 release notes.

+++ This bug was initially created as a clone of Bug #2087144 +++

Description of problem:
LEAPP upgrade fails to resolve ansible dependencies on RHEL8.6

On RHEL8.5 we used ansible-2.9 and with the move to RHEL8.6 we use ansible-core 2.12 instead.


Version-Release number of selected component (if applicable):
Satellite-6.11-RHEL-8-20220516.t.0 (dev compose)

How reproducible:
deterministic

Steps to Reproduce:
1. Have 6.11 Satellite on RHEL7

2. Run LEAPP upgrade/preupgrade to RHEL8.6
# leapp preupgrade --enablerepo satellite --enablerepo maintenance
...

============================================================
                           ERRORS                           
============================================================

2022-05-17 07:58:22.600270 [ERROR] Actor: dnf_transaction_check
Message: DNF execution failed with non zero exit code.
STDOUT:
Last metadata expiration check: 0:01:14 ago on Tue May 17 07:56:56 2022.
Package foreman-installer-katello-1:3.1.2.5-1.el7sat.noarch 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.5-1.el7sat.noarch is already installed.

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

 Problem: problem with installed package ansible-2.9.27-1.el7ae.noarch
  - 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


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

Actual results:
leapp upgrade to 8.6 is broken

Expected results:
leapp upgrade works

Workaround:
prior leapp run "rpm -e ansible ansible-test --nodeps"

Comment 2 sabuchan 2022-06-10 20:17:21 UTC
RN draft:

LEAPP upgrades fail to resolve Ansible dependencies on RHEL 8.6. To work around this, run `rpm -e ansible ansible-test --nodeps` on your terminal prior to upgrading LEAPP.

Doc: https://docs.google.com/document/d/1xMkjPbkwF9ZJ95tEcWYmRRqVdusIZENHZsL3-B3YvJw/edit

Tagged @bbuckingham for review.

Comment 3 Brad Buckingham 2022-06-14 20:42:23 UTC
Proposed minor update to text in the doc referenced in comment 2.

Comment 4 sabuchan 2022-06-15 20:06:09 UTC
Final RN:

*Leapp utility upgrade fails to resolve Ansible dependencies on RHEL 8.6*

In-place upgrades from RHEL 7 to RHEL 8 fail to resolve Ansible dependencies on RHEL 8.6. 
To work around this, run `rpm -e ansible ansible-test --nodeps` prior to the in-place upgrade.


Note You need to log in before you can comment on or make changes to this bug.