Bug 2148468

Summary:	[leapp][pes] IPU 7->8: conflict with nbdkit* packages
Product:	Red Hat Enterprise Linux 7	Reporter:	Christophe Besson <cbesson>
Component:	leapp-repository	Assignee:	Leapp Notifications Bot <leapp-notifications-bot>
Status:	CLOSED MIGRATED	QA Contact:	upgrades-and-conversions
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.9	CC:	awaltlov, pstodulk, ymankad
Target Milestone:	rc	Keywords:	MigratedToJIRA, Reproducer
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-12 12:33:54 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 Christophe Besson 2022-11-25 15:14:52 UTC

Description of problem:
A conflict occurs in the dnf transaction when nbdkit* packages are installed on the system.

Version-Release number of selected component (if applicable):
leapp-upgrade-el7toel8-0.17.0-1.el7_9

How reproducible:
Always

Steps to Reproduce:
# yum install nbdkit nbdkit-plugin-python2 nbdkit-plugin-python-common nbdkit-plugin-vddk
# leapp upgrade

Actual results:
 Problem: cannot install the best update candidate for package nbdkit-1.8.0-4.el7.x86_64
  - problem with installed package nbdkit-1.8.0-4.el7.x86_64
  - package nbdkit-1.24.0-4.module+el8.6.0+14480+c0a3aa0f.x86_64 requires nbdkit-server(x86-64) = 1.24.0-4.module+el8.6.0+14480+c0a3aa0f, but none of the providers can be installed
  - package nbdkit-server-1.16.2-4.module+el8.3.0+6922+fd575af8.x86_64 conflicts with nbdkit < 1.12 provided by nbdkit-1.4.2-4.module+el8+2586+bf759444.x86_64
  - package nbdkit-server-1.16.2-4.module+el8.3.0+6922+fd575af8.x86_64 conflicts with nbdkit < 1.12 provided by nbdkit-1.4.2-4.module+el8.0.0.z+3418+a72cf898.x86_64
  - package nbdkit-server-1.16.2-4.module+el8.3.0+6922+fd575af8.x86_64 conflicts with nbdkit < 1.12 provided by nbdkit-1.4.2-5.module+el8.0.0+4084+cceb9f44.x86_64
  - package nbdkit-server-1.16.2-4.module+el8.3.0+6922+fd575af8.x86_64 conflicts with nbdkit < 1.12 provided by nbdkit-1.4.2-4.module+el8.0.0+3075+09be6b65.x86_64
  - package nbdkit-server-1.16.2-4.module+el8.3.0+6922+fd575af8.x86_64 conflicts with nbdkit < 1.12 provided by nbdkit-1.4.2-5.module+el8.1.0+4066+0f1aadab.x86_64
  - cannot install both nbdkit-server-1.24.0-4.module+el8.6.0+14480+c0a3aa0f.x86_64 and nbdkit-server-1.16.2-4.module+el8.3.0+6922+fd575af8.x86_64
  - package nbdkit-python-plugin-1.16.2-4.module+el8.3.0+6922+fd575af8.x86_64 requires nbdkit-server(x86-64) = 1.16.2-4.module+el8.3.0+6922+fd575af8, but none of the providers can be installed
  - cannot install the best candidate for the job
  - nbdkit-1.8.0-4.el7.x86_64 does not belong to a distupgrade repository

Additional info:
- Removing nbdkit* packages workarounds the issue.

Comment 3 Petr Stodulka 2022-11-25 16:20:18 UTC

Hi Christophe, thanks for the report. It's potentially problem inside PES data. It will be investigated later.

Comment 5 RHEL Program Management 2023-09-12 12:32:00 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-12 12:33:54 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.