Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 846772

Summary: Sudo update b0rks localhost resolving completely
Product: Red Hat Enterprise Linux 5 Reporter: Mario Mikocevic <mario.mikocevic>
Component: sudoAssignee: Daniel Kopeček <dkopecek>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 5.8CC: dkopecek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-09 09:45:34 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 Mario Mikocevic 2012-08-08 16:06:14 UTC 
Description of problem:

Updating sudo to latest
sudo-1.7.2p1-14.el5_8.2
b0rked server to inability to resolve any local name

ie
/etc/hosts
127.0.0.1  localhost testname

some programs cannot resolve that anymore like php, python scripts
but interestingly ping(8) works.

I resolved this by
yum remove sudo
yum downgrade glibc glibc-common nscd
yum update glibc
yum install sudo

and now local name resolving works.
Comment 1 Mario Mikocevic 2012-08-09 09:43:04 UTC 
Found the culprit, upgrading sudo changes file permission of /etc/nsswitch.conf from 644 to 600.
It happens only on x86_64 arch.
Comment 2 Daniel Kopeček 2012-08-09 09:45:34 UTC 

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