Bug 703880

Summary:	getpwuid unreliable when using NIS, missing flag: -DUSE_BINDINGDIR=1
Product:	[Fedora] Fedora	Reporter:	Francis.Montagnac
Component:	glibc	Assignee:	Andreas Schwab <schwab>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	14	CC:	fweimer, jakub, schwab
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glibc-2.14-2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	706903 (view as bug list)		Environment:
Last Closed:	2011-06-07 04:25:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Francis.Montagnac 2011-05-11 14:08:00 UTC

Description of problem:

On a machine using NIS for passwd in compat mode and with a big
netgroup (~ 790 users), the uid resolution is unreliable.

Version-Release number of selected component (if applicable):
glibc-2.13-1.x86_64

How reproducible: every time, with and without nscd running.

Steps to Reproduce:
1. in /etc/nsswitch.conf: passwd:     compat
2. in /etc/passwd: +@NETGROUP::::::
   where NETGROUP contains ~ 790 users.
3. "ls -l" in a directory containing a sub-directory per user owned by
   each of them.

Actual results:

All the uid's are not reliably translated to user names.

Expected results:

All the uid's translated to user names.

Additional info:

A fix that works (at least for me) is to recompile glibc with the
following flags for ypclnt.c in glibc-fedora.patch

+CFLAGS-ypclnt.c = -fno-strict-aliasing -DUSE_BINDINGDIR=1

instead of:

+CFLAGS-ypclnt.c = -fno-strict-aliasing

Comment 1 Fedora Update System 2011-05-27 15:21:42 UTC

glibc-2.13.90-14 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/glibc-2.13.90-14

Comment 2 Fedora Update System 2011-05-27 20:24:51 UTC

Package glibc-2.13.90-14:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing glibc-2.13.90-14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/glibc-2.13.90-14
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2011-06-02 19:08:53 UTC

Package glibc-2.14-1:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing glibc-2.14-1'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/glibc-2.14-1
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2011-06-04 02:55:47 UTC

Package glibc-2.14-2:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing glibc-2.14-2'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/glibc-2.14-2
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2011-06-07 04:25:07 UTC

glibc-2.14-2 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.