Bug 1028553

Summary: Removed openldap-devel; yum broken
Product: [Fedora] Fedora Reporter: Jon Dufresne <jon.dufresne>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: admiller, ffesti, firas.alkafri, jon.dufresne, jzeleny, packaging-team-maint, rjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-19 12:26:30 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:

Description Jon Dufresne 2013-11-08 18:46:29 UTC
I noticed yum wanted to upgrade openldap-devel. As I do not use LDAP nor develop against it, I thought it was strange it was installed. So I removed it using:

$ sudo yum remove openldap-devel

This removed the following: openldap-devel, apr-util-devel, httpd-devel.

Now all yum commands fail with the following error:

# yum upgrade
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

   liblber-2.4.so.2: cannot open shared object file: No such file or directory

Please install a package which provides this module, or
verify that the module is installed correctly.

It's possible that the above module doesn't match the
current version of Python, which is:
2.7.5 (default, Oct  8 2013, 12:19:40) 
[GCC 4.8.1 20130603 (Red Hat 4.8.1-1)]

If you cannot solve this problem yourself, please go to 
the yum faq at:
  http://yum.baseurl.org/wiki/Faq

Comment 1 Zdeněk Pavlas 2013-11-11 08:52:46 UTC
This might be a packaging bug, some components used by Yum may need liblber. Curl comes to mind, as it supports ldap:// URLs. Please run this, and copy-paste the traceback to verify.

$ python -c 'import yum'
$ python -c 'import pycurl'

Comment 2 Zdeněk Pavlas 2013-11-11 08:56:47 UTC
To fix the Yum breakage, you'll probably have to download openldap-devel.rpm manually and install it with rpm.

Comment 3 Zdeněk Pavlas 2013-11-11 10:43:41 UTC
Anyway, liblber-2.4.so.2 is owned by the openldap package, NOT by openldap-devel.. And there's a dependency chain yum => urlgrabber => curl => openldap already, so You should not be allowed to remove openldap.

So either you ran "rpm -e openldap --nodeps", or your system is broken be some other means.  Please check that openldap is installed, and reinstall it.

Comment 4 Richard W.M. Jones 2014-05-19 13:35:48 UTC
Likely to be an instance of:
https://bugzilla.redhat.com/show_bug.cgi?id=1028557

Comment 5 Jon Dufresne 2014-09-29 14:17:00 UTC
Removing NEEDINFO.

Comment 6 Fedora End Of Life 2015-01-09 20:32:00 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Richard W.M. Jones 2015-01-19 12:26:30 UTC

*** This bug has been marked as a duplicate of bug 1028557 ***