Bug 2163461

Summary:	convert2rhel fails with Problem 2: package kernel-4.18.0-348.23.1.el8_5.x86_64 requires kernel-core-uname-r = 4.18.0-348.23.1.el8_5.x86_64, but none of the providers can be installed
Product:	Red Hat Enterprise Linux 8	Reporter:	jcastran
Component:	convert2rhel	Assignee:	Michal Bocek <mbocek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	upgrades-and-conversions
Severity:	unspecified	Docs Contact:	Miriam Portman <mportman>
Priority:	unspecified
Version:	8.7	CC:	prjagtap
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	convert2rhel-1.3.2-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-31 08:47:47 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 jcastran 2023-01-23 14:58:48 UTC

Description of problem:
convert2rhel is failing to install the new RHEL 8 kernel

Version-Release number of selected component (if applicable):
convert2rhel-1.1-1

How reproducible:
have not yet reproduced

Actual results:
CRITICAL - Failed to resolve dependencies in the transaction.
[01/16/2023 14:58:48] DEBUG - Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/convert2rhel/pkgmanager/handlers/dnf.py", line 119, in _resolve_dependencies
    self._base.resolve(allow_erasing=True)
  File "/usr/lib/python3.6/site-packages/dnf/base.py", line 860, in resolve
    raise exc
dnf.exceptions.DepsolveError:
 Problem 1: conflicting requests
 Problem 2: package kernel-4.18.0-348.23.1.el8_5.x86_64 requires kernel-core-uname-r = 4.18.0-348.23.1.el8_5.x86_64, but none of the providers can be installed
  - conflicting requests
 Problem 3: package kernel-modules-4.18.0-348.23.1.el8_5.x86_64 requires kernel-uname-r = 4.18.0-348.23.1.el8_5.x86_64, but none of the providers can be installed
  - conflicting requests

Comment 3 Michal Bocek 2023-07-31 08:47:47 UTC

@ahosek has analyzed all the related customers cases and tried to reproduce the issue. All of them were failing with convert2rhel 1.2 and all of them succeeded under 1.3. Closing as fixed.