Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
In multilib environment if booth architectures are installed the native architecture of the machine should appear on the disk (e.g. on x86_64 machine if booth i686 and x86_64 version of a package are installed the x86_64 versions of binaries and libraries should be installed). This can be broken under certain circumstances.
Version-Release number of selected component (if applicable):
rpm-4.11.1-23.el7
How reproducible:
always
Steps to Reproduce:
[root@rhel70 new]# uname -p
x86_64
[root@rhel70 new]# rpm -qa krb5\*
krb5-libs-1.12.2-8.el7.i686
krb5-libs-1.12.2-8.el7.x86_64
[root@rhel70 new]# rpm -ivh krb5-server-1.12.2-8.el7.*.rpm krb5-devel-1.12.2-8.el7.*.rpm
Preparing... ################################# [100%]
Updating / installing...
1:krb5-devel-1.12.2-8.el7 ################################# [ 25%]
2:krb5-server-1.12.2-8.el7 ################################# [ 50%]
3:krb5-devel-1.12.2-8.el7 ################################# [ 75%]
4:krb5-server-1.12.2-8.el7 ################################# [100%]
[root@rhel70 new]# file /usr/bin/sclient /usr/sbin/sserver
/usr/bin/sclient: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0xefe01735210a6015283c3bd7a8e6256f2d1bc4d6, stripped
/usr/sbin/sserver: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0xd1930e90c926388d35f3e01868a2169267207d13, stripped
[root@rhel70 new]#
[root@rhel70 new]# rpm -qV krb5-devel.i686
[root@rhel70 new]# rpm -qV krb5-devel.x86_64
S.5...... /usr/bin/sclient
S.5...... /usr/sbin/sserver
[root@rhel70 new]# rpm -qV krb5-server.i686
[root@rhel70 new]# rpm -qV krb5-server.x86_64
S.5...... /usr/bin/sclient
S.5...... /usr/sbin/sserver
[root@rhel70 new]#
Additional info:
The bug demonstrated itself because by mistake booth arch od krb5-server were distributed, what is a mistake. In the past only 2 krb5-devel and 1 krb5-server packages were released, and in that case the problem does not appear. In any case, this bug should be fixed also on rpm level.
[root@rhel70 new]# rpm -ivh krb5-server-1.12.2-8.el7.x86_64.rpm krb5-devel-1.12.2-8.el7.*.rpm
Preparing... ################################# [100%]
Updating / installing...
1:krb5-devel-1.12.2-8.el7 ################################# [ 33%]
2:krb5-server-1.12.2-8.el7 ################################# [ 67%]
3:krb5-devel-1.12.2-8.el7 ################################# [100%]
[root@rhel70 new]# file /usr/bin/sclient /usr/sbin/sserver
/usr/bin/sclient: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0xba6c46db5380ecefac4788835d67e3fe9359aeba, stripped
/usr/sbin/sserver: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0x1cfa9c9cd8c10594aafbc4085ee0d39b5d86b553, stripped
[root@rhel70 new]# rpm -qV krb5-devel.i686
[root@rhel70 new]# rpm -qV krb5-devel.x86_64
[root@rhel70 new]# rpm -qV krb5-server.x86_64
[root@rhel70 new]#
No, with multilib files with color=1 (typically 32 bit binaries) are silently overwritten by files with color=2 (typically 64 bit binaries). We already fixed this in 6.7. See #1170124.
One note why there is no conflict here. Let's have a look at file /usr/bin/sclient. We have this file in four packages (krb5-devel.i686, krb5-devel.x86_64, krb5-server.i686, krb5-server.x86_64) so we have following six combinations (4 choose 2 = 6).
/usr/bin/sclient(krb5-devel.i686) vs usr/bin/sclient(krb5-server.i686) -> the same content -> no file conflict
/usr/bin/sclient(krb5-devel.x86_64) vs usr/bin/sclient(krb5-server.x86_64) -> the same content -> no file conflict
/usr/bin/sclient(krb5-devel.i686) vs usr/bin/sclient(krb5-devel.x86_64) -> different colors -> no file conflict
/usr/bin/sclient(krb5-server.i686) vs usr/bin/sclient(krb5-server.x86_64) -> different colors -> no file conflict
/usr/bin/sclient(krb5-devel.i686) vs usr/bin/sclient(krb5-server.x86_64) -> different colors -> no file conflict
/usr/bin/sclient(krb5-server.i686) vs usr/bin/sclient(krb5-devel.x86_64) -> different colors -> no file conflict
So there is no conflict and 64bit variant of file /usr/bin/sclient should be installed.
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, 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://rhn.redhat.com/errata/RHBA-2015-2138.html