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.
DescriptionRobert G. 'Doc' Savage
2011-09-27 11:53:51 UTC
Created attachment 525104[details]
Capture of yum update session, including all GLIBC errors
Description of problem: glibc errors reported during yum update
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. yum -y update (see re-run in attachment)
2.
3.
Actual results: see attachment
Expected results:
Additional info:
ERROR with rpm_check_debug vs depsolve:
libc.so.6 is needed by openldap-2.4.23-15.el6_1.3.i686
libc.so.6(GLIBC_2.0) is needed by openldap-2.4.23-15.el6_1.3.i686
libc.so.6(GLIBC_2.1) is needed by openldap-2.4.23-15.el6_1.3.i686
libc.so.6(GLIBC_2.1.2) is needed by openldap-2.4.23-15.el6_1.3.i686
libc.so.6(GLIBC_2.1.3) is needed by openldap-2.4.23-15.el6_1.3.i686
libc.so.6(GLIBC_2.12) is needed by openldap-2.4.23-15.el6_1.3.i686
libc.so.6(GLIBC_2.3) is needed by openldap-2.4.23-15.el6_1.3.i686
libc.so.6(GLIBC_2.3.2) is needed by openldap-2.4.23-15.el6_1.3.i686
libc.so.6(GLIBC_2.3.4) is needed by openldap-2.4.23-15.el6_1.3.i686
libc.so.6(GLIBC_2.4) is needed by openldap-2.4.23-15.el6_1.3.i686
libresolv.so.2 is needed by openldap-2.4.23-15.el6_1.3.i686
libresolv.so.2(GLIBC_2.2) is needed by openldap-2.4.23-15.el6_1.3.i686
Please report this error in https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%206&component=yum
** Found 663 pre-existing rpmdb problem(s), 'yum check' output follows:
PyQt4-devel-4.6.2-8.el6.x86_64 has missing requires of qt4-devel
atk-1.28.0-2.el6.i686 has missing requires of libc.so.6
atk-1.28.0-2.el6.i686 has missing requires of libc.so.6(GLIBC_2.0)
atk-1.28.0-2.el6.i686 has missing requires of libc.so.6(GLIBC_2.1.3)
atk-1.28.0-2.el6.i686 has missing requires of libc.so.6(GLIBC_2.2)
...assuming you have a glibc installed, I'd guess you want to rerun rpm --rebuilddb ... but do you have glibc installed?
Comment 3Robert G. 'Doc' Savage
2011-09-27 22:00:30 UTC
Yes, glibc is installed:
#rpm -qa | grep glibc
glibc-2.12-1.25.el6_1.3.x86_64
Reran rpm --rebuilddb ... Problem persisted until I removed an i686 package that shouldn't have been there:
# yum erase openldap-2.4.23-15.el6_1.1.i686
Then yum update completed normally. OK to close.
Comment 4RHEL Program Management
2011-10-07 16:20:28 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Created attachment 525104 [details] Capture of yum update session, including all GLIBC errors Description of problem: glibc errors reported during yum update Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. yum -y update (see re-run in attachment) 2. 3. Actual results: see attachment Expected results: Additional info: