Bug 846772 - Sudo update b0rks localhost resolving completely
Sudo update b0rks localhost resolving completely
Status: CLOSED DUPLICATE of bug 846631
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sudo (Show other bugs)
5.8
Unspecified Unspecified
unspecified Severity urgent
: rc
: ---
Assigned To: Daniel Kopeček
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-08 12:06 EDT by Mario Mikocevic
Modified: 2012-08-09 05:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-08-09 05:45:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mario Mikocevic 2012-08-08 12:06:14 EDT
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 05:43:04 EDT
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 05:45:34 EDT

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

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