RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1782899 - libstoragemgmt prevents `dnf groupinstall base`
Summary: libstoragemgmt prevents `dnf groupinstall base`
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libsolv
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 8.0
Assignee: Lukáš Hrázký
QA Contact: Eva Mrakova
URL:
Whiteboard:
Depends On: 1792370
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-12 15:42 UTC by David Galloway
Modified: 2021-05-18 15:00 UTC (History)
5 users (show)

Fixed In Version: libsolv-0.7.16-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1792370 (view as bug list)
Environment:
Last Closed: 2021-05-18 15:00:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
full DNF output (38.81 KB, text/plain)
2019-12-12 15:42 UTC, David Galloway
no flags Details
output from dnf -v groupinstall base (74.89 KB, text/plain)
2019-12-12 21:27 UTC, Tony Asleson
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:1655 0 None None None 2021-05-18 15:00:30 UTC

Description David Galloway 2019-12-12 15:42:38 UTC
Created attachment 1644464 [details]
full DNF output

Description of problem:
`dnf groupinstall base` fails on RHEL8 because libstoragemgmt tries to install i686 packages which conflict with existing x86_64 packages.

Version-Release number of selected component (if applicable):
libstoragemgmt 1.8.1-2.el8

How reproducible:
100%

Steps to Reproduce:
1. Install RHEL8
2. Enable baseos and appstream repos
3. `dnf groupinstall base`

Actual results:
Error: Transaction check error:
  file /usr/lib/tmpfiles.d/libstoragemgmt.conf conflicts between attempted installs of libstoragemgmt-1.6.2-9.el8.i686 and libstoragemgmt-1.8.1-2.el8.x86_64
  file /usr/share/doc/libstoragemgmt/NEWS conflicts between attempted installs of libstoragemgmt-1.6.2-9.el8.i686 and libstoragemgmt-1.8.1-2.el8.x86_64
  file /usr/share/man/man1/lsmcli.1.gz conflicts between attempted installs of libstoragemgmt-1.6.2-9.el8.i686 and libstoragemgmt-1.8.1-2.el8.x86_64
  file /usr/share/man/man1/lsmd.1.gz conflicts between attempted installs of libstoragemgmt-1.6.2-9.el8.i686 and libstoragemgmt-1.8.1-2.el8.x86_64
  file /usr/share/man/man1/simc_lsmplugin.1.gz conflicts between attempted installs of libstoragemgmt-1.6.2-9.el8.i686 and libstoragemgmt-1.8.1-2.el8.x86_64
  file /usr/share/man/man5/lsmd.conf.5.gz conflicts between attempted installs of libstoragemgmt-1.6.2-9.el8.i686 and libstoragemgmt-1.8.1-2.el8.x86_64


Expected results:
An x86_64 package wouldn't bring in i686 packages if no other i686 packages are present on the system?

Additional info:
# rpm -qa | grep libstorage
python3-libstoragemgmt-clibs-1.6.2-9.el8.x86_64
python3-libstoragemgmt-1.6.2-9.el8.noarch
libstoragemgmt-1.6.2-9.el8.x86_64

`rpm -qa | grep i686` returns nothing.

Comment 3 Tony Asleson 2019-12-12 21:00:37 UTC
I'm not sure what is going on with this.  A system exhibiting this problem will do the following without pulling in i686 packages:


# sudo dnf update libstoragemgmt
# sudo dnf update

If I exclude i686 to force a more meaningful error I get none.

#  sudo dnf groupinstall base -x \*i686

I think we are going to need someone more versed with dnf to take a look at this.  The system I was using is still in same state and will reproduce the issue.

Comment 4 Tony Asleson 2019-12-12 21:20:18 UTC
Assigning to dnf for analysis.

Comment 6 Tony Asleson 2019-12-12 21:27:42 UTC
Created attachment 1644569 [details]
output from dnf -v groupinstall base

Comment 7 Jaroslav Mracek 2020-01-16 18:54:04 UTC
Thanks for the report. From Comment 0 I can see that the issue is file conflict not in depsolving. The question is why i686 packages were pulled in or whe they have different version than x86_64? I also know that handling of i686 was improved in 8.1. Therefore please could you try to reproduce the issue once again but before any action please upgrade dnf, libdnf, libsolv to the latest version. Then did you experience different behaviour?

Comment 8 Jaroslav Mracek 2020-01-17 13:10:11 UTC
The issue is reproducible even with latest dnf, libdnf, libsolv-0.7.10.

Comment 9 Jaroslav Mracek 2020-01-17 15:02:42 UTC
There is a work around. Instead of `dnf groupinstall base` please could you try `dnf groupinstall base --nobest` and then `dnf group upgrade base`. Then i686 packages will not appears in transaction.


There is an issue in dnf or libsolv that handles the situation incorrectly. But I am unable to create a simple testcase for libsolv upstream with incorrect behaviour.

But there is another  problem in packaging of libstoragemgmt. python3-libstoragemgmt-clibs.x86-64 requires `libstoragemgmt = 1.8.1-2.el8`, but it should require `libstoragemgmt(x86-64) = 1.8.1-2.el8`. Following patch will resolve it.

diff --git a/libstoragemgmt.spec b/libstoragemgmt.spec
index 37dd22c..b15d35f 100644
--- a/libstoragemgmt.spec
+++ b/libstoragemgmt.spec
@@ -70,7 +70,7 @@ support and open source plug-ins written in python 3.
 %package        -n python3-%{name}-clibs
 Summary:        Python 3 C extension module for %{name}
 Group:          System Environment/Libraries
-Requires:       %{name} = %{version}-%{release}
+Requires:       %{name}%{?_isa} = %{version}-%{release}
 %{?python_provide:%python_provide python3-%{name}-clibs}
 
 %description    -n python3-%{name}-clibs

Comment 10 David Galloway 2020-01-21 14:36:26 UTC
(In reply to Jaroslav Mracek from comment #9)
> There is a work around. Instead of `dnf groupinstall base` please could you
> try `dnf groupinstall base --nobest` and then `dnf group upgrade base`. Then
> i686 packages will not appears in transaction.
> 
> 

I confirm this workaround works for me!  Thank you!

Comment 11 Jaroslav Mracek 2020-01-28 14:58:41 UTC
I tried to create a libsolv reproducer but simplified case worked as expected.


repo @System 0 testtags <inline>
#>=Pkg: libstoragemgmt 1.0 1 x86_64
#>=Prq: python3-libstoragemgmt = 1.0-1
#>=Prv: libstoragemgmt = 1.0-1
#>=Pkg: python3-libstoragemgmt-clibs 1.0 1 x86_64
#>=Prq: libstoragemgmt = 1.0-1
#>=Prv: python3-libstoragemgmt-clibs = 1.0-1
#>=Pkg: python3-libstoragemgmt 1.0 1 noarch
#>=Prq: libstoragemgmt = 1.0-1
#>=Prv: python3-libstoragemgmt = 1.0-1

repo updates 0 testtags <inline>
#>=Pkg: libstoragemgmt 2.0 1 x86_64
#>=Prq: python3-libstoragemgmt = 2.0-1
#>=Prv: libstoragemgmt = 2.0-1
#>=Pkg: python3-libstoragemgmt-clibs 2.0 1 x86_64
#>=Prq: libstoragemgmt = 2.0-1
#>=Prv: python3-libstoragemgmt-clibs = 2.0-1
#>=Pkg: python3-libstoragemgmt 2.0 1 noarch
#>=Prq: libstoragemgmt = 2.0-1
#>=Prq: python3-libstoragemgmt-clibs
#>=Prv: python3-libstoragemgmt = 2.0-1
#>=Pkg: libstoragemgmt 2.0 1 i686
#>=Prq: python3-libstoragemgmt = 2.0-1
#>=Prv: libstoragemgmt = 2.0-1
#>=Pkg: python3-libstoragemgmt-clibs 2.0 1 i686
#>=Prq: libstoragemgmt = 2.0-1
#>=Prv: python3-libstoragemgmt-clibs = 2.0-1



system x86_64 rpm @System
poolflags implicitobsoleteusescolors

solverflags allowvendorchange keepexplicitobsoletes bestobeypolicy keeporphans yumobsoletes
job install oneof libstoragemgmt-1.0-1.x86_64@@System libstoragemgmt-2.0-1.x86_64@updates libstoragemgmt-2.0-1.i686@updates [forcebest,targeted,setevr,setarch]
#job update all packages [forcebest]
#job update all packages
#job install oneof test-package-alpha-1.0-2.i386@updates [forcebest,targeted,setevr,setarch]
#job install oneof test-package-alpha-1.0-2.i386@updates [setevr,setarch]
result transaction,problems <inline>
#>upgrade libstoragemgmt-1.0-1.x86_64@@System libstoragemgmt-2.0-1.x86_64@updates
#>upgrade python3-libstoragemgmt-1.0-1.noarch@@System python3-libstoragemgmt-2.0-1.noarch@updates
#>upgrade python3-libstoragemgmt-clibs-1.0-1.x86_64@@System python3-libstoragemgmt-clibs-2.0-1.x86_64@updates

Comment 12 Lukáš Hrázký 2020-05-19 13:41:21 UTC
I've reported a bug against libsolv with a minimal test case reproducer of the problem:
https://github.com/openSUSE/libsolv/issues/383

I've also noticed python3-libstoragemgmt-1.8.3-1.el8 provides its name in two versions:

$ dnf repoquery --provides python3-libstoragemgmt-1.8.3-1.el8
python3-libstoragemgmt = 1.6.2-9.el8
python3-libstoragemgmt = 1.8.3-1.el8

This seems wrong and probably should be fixed. (it doesn't fix the i686 problem though)

Comment 17 Lukáš Hrázký 2020-10-13 12:28:57 UTC
The issue was fixed in upstream libsolv and should be a part of the 0.7.16 release.

I've created a test in our CI: https://github.com/rpm-software-management/ci-dnf-stack/pull/897

Comment 18 Lukáš Hrázký 2020-10-14 08:45:30 UTC
Changing the component to libsolv, as the fix was there:
https://github.com/openSUSE/libsolv/commit/894382f0c4ddf6d34b264544c3523a9094ec2a09

(slated for 0.7.16 release or higher)

Comment 25 errata-xmlrpc 2021-05-18 15:00:22 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 (libsolv bug fix and enhancement update), 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/RHBA-2021:1655


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