Bug 696707 – nss_ldap client does not seem to get a response from ldap server

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 696707 - nss_ldap client does not seem to get a response from ldap server

Summary:	nss_ldap client does not seem to get a response from ldap server

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 5
Classification:	Red Hat
Component:	nss_ldap (Show other bugs)
Sub Component:
Version:	5.8
Hardware:	All Linux

Priority	high Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Nalin Dahyabhai
QA Contact:	Ondrej Moriš
Docs Contact:

URL:
Whiteboard:
Keywords:	OtherQA

Depends On:
Blocks:	758797
	Show dependency tree / graph

Reported:	2011-04-14 13:07 EDT by Heath Petty
Modified:	2014-07-24 23:36 EDT (History)
CC List:	12 users (show)

See Also:
Fixed In Version:	nss_ldap-253-46.el5
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:	574306
Environment:
Last Closed:	2012-02-21 01:38:48 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
RHEL 4 patch applied to RHEL 5 nss_ldap (1.05 KB, patch) 2011-04-14 13:16 EDT, Heath Petty	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2012:0268	normal	SHIPPED_LIVE	nss_ldap bug fix and enhancement update	2012-02-20 10:06:24 EST

Groups: None (edit)

Comment 1 Heath Petty 2011-04-14 13:16:38 EDT

Created attachment 492173 [details]
RHEL 4 patch applied to RHEL 5 nss_ldap

This is not my patch, I just applied the patch for RHEL 4 to RHEL 5.

Comment 2 Heath Petty 2011-04-14 13:17:06 EDT

Customer has tested this patch and it solves their issue.

-Heath

Comment 7 errata-xmlrpc 2012-02-21 01:38:48 EST

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.

http://rhn.redhat.com/errata/RHBA-2012-0268.html

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