Bug 489371 - removal of fedora-lsb irrevocably causes hostname resolution failure for a lot of tools
Summary: removal of fedora-lsb irrevocably causes hostname resolution failure for a lo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: net-tools
Version: 9
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: http://fpaste.org/paste/5538
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-09 18:30 UTC by Daniel K. Attling
Modified: 2009-07-14 16:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-14 16:25:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Daniel K. Attling 2009-03-09 18:30:11 UTC
Description of problem:
When sendmail is removed using yum (yum remove sendmail) redhat-lsb is also removed with it. This breaks hostname resolution for a lot of tools (ssh, w3m, and dig to name a few). Performing a `yum install redhat-lsb` does not restore this functionality.

Version-Release number of selected component (if applicable):
kernel-2.6.27.19-78.2.30.fc9.x86_64
redhat-lsb-3.1-19.fc8.x86_64
w3m-0.5.2-10.fc9.x86_64
bind-utils-9.5.1-1.P1.fc9.x86_64
openssh-clients-5.1p1-3.fc9.x86_64

How reproducible:


Steps to Reproduce:
1. yum -y remove sendmail
2. host esther2
3. ping esther2
4. ssh esther2 (or w3m esther2)
  
Actual results:
2. esther2 resolves fine
3. esther2 responds to ping
4. "ssh: Could not resolve hostname esther2: Name or service not known"

Expected results:
ssh connection to esther2



strace capture of `ssh esther2`:

open("/etc/resolv.conf", O_RDONLY)      = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=70, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fbc708c6000
read(3, "search corp.swiss.se\nnameserver "..., 4096) = 70
read(3, "", 4096)                       = 0
close(3)                                = 0
munmap(0x7fbc708c6000, 4096)            = 0
open("/etc/hosts", O_RDONLY|0x80000 /* O_??? */) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=598, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fbc708c6000
read(3, "# Do not remove the following li"..., 4096) = 598
read(3, "", 4096)                       = 0
close(3)                                = 0
munmap(0x7fbc708c6000, 4096)            = 0
open("/etc/hosts", O_RDONLY|0x80000 /* O_??? */) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=598, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fbc708c6000
read(3, "# Do not remove the following li"..., 4096) = 598
read(3, "", 4096)                       = 0
close(3)                                = 0
munmap(0x7fbc708c6000, 4096)            = 0
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=55193, ...}) = 0
mmap(NULL, 55193, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fbc708b9000
close(3)                                = 0
open("/lib64/tls/x86_64/libnss_mdns4_minimal.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/lib64/tls/x86_64", 0x7fff788c41e0) = -1 ENOENT (No such file or directory)
open("/lib64/tls/libnss_mdns4_minimal.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/lib64/tls", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/lib64/x86_64/libnss_mdns4_minimal.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/lib64/x86_64", 0x7fff788c41e0)   = -1 ENOENT (No such file or directory)
open("/lib64/libnss_mdns4_minimal.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/lib64", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0
open("/usr/lib64/tls/x86_64/libnss_mdns4_minimal.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/usr/lib64/tls/x86_64", 0x7fff788c41e0) = -1 ENOENT (No such file or directory)
open("/usr/lib64/tls/libnss_mdns4_minimal.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/usr/lib64/tls", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/usr/lib64/x86_64/libnss_mdns4_minimal.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/usr/lib64/x86_64", 0x7fff788c41e0) = -1 ENOENT (No such file or directory)
open("/usr/lib64/libnss_mdns4_minimal.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/usr/lib64", {st_mode=S_IFDIR|0755, st_size=53248, ...}) = 0
munmap(0x7fbc708b9000, 55193)           = 0
write(2, "ssh: Could not resolve hostname "..., 68ssh: Could not resolve hostname esther2: Name or service not known
) = 68
exit_group(255)                         = ?

Comment 1 Bug Zapper 2009-06-10 03:36:16 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2009-07-14 16:25:04 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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