Bug 1510865

Summary: python-ldap is not a dependency of 389-ds-base
Product: Red Hat Enterprise Linux 7 Reporter: Marc Muehlfeld <mmuehlfe>
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: enewland, nkinder, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.7.5-10.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 14:21:13 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 Marc Muehlfeld 2017-11-08 10:48:22 UTC
Description of problem:
In RHEL 7.5 beta, if you install Directory Server, the python-ldap package is not installed as a dependency. However, the new ds-replcheck script provided by 389-ds-base needs it.



Version-Release number of selected component (if applicable):
389-ds-base-1.3.7.5-9.el7.x86_64



How reproducible:
Always.



Steps to Reproduce:
1. Install 389-ds-base
2. Run ds-replcheck



Actual results:
# ds-replcheck --help
Traceback (most recent call last):
  File "/usr/bin/ds-replcheck", line 14, in <module>
    import ldap
ImportError: No module named ldap



Expected results:
Command should work.
(install python-ldap to fix the problem.)


Additional info:
Add python-ldap as a dependency to 389-ds-base to fix the problem

Comment 3 Viktor Ashirov 2017-11-21 16:43:20 UTC
Build tested:
389-ds-base-1.3.7.5-10.el7.x86_64

Latest build pulls python-ldap:
# repoquery --requires --resolve  389-ds-base  | grep python-ldap 
python-ldap-0:2.4.15-2.el7.x86_64

ds-replcheck doesn't throw error.

Marking as VERIFIED, SanityOnly.

Comment 6 errata-xmlrpc 2018-04-10 14:21:13 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, 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-2018:0811