Bug 750509

Summary: NetworkManager calls nscd incorrectly during "IP Configure Commit"
Product: [Fedora] Fedora Reporter: John Beranek <john>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: dcbw, emisca, loganjerry, rrauenza, udovdh, ville.skytta
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 13:47:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Patch to be added to NetworkManager RPM
none
Patch to be added to NetworkManager RPM none

Description John Beranek 2011-11-01 12:30:59 UTC
Description of problem:

NetworkManager appears to be calling nscd incorrectly during the "IP Configure Commit" phase, and in my configuration this is leading to a failure to start ypbind correctly, thereby disabling NIS support.

The error log I see is:

Nov  1 12:53:55 localhost NetworkManager[1031]: <warn> could not spawn process '
/etc/init.d/nscd condrestart': Failed to execute child process "/etc/init.d/nscd
" (No such file or directory)
Nov  1 12:53:55 localhost NetworkManager[1031]: NetworkManager[1031]: <warn> could not spawn process '/etc/init.d/nscd condrestart': Failed to execute child process "/etc/init.d/nscd" (No such file or directory)
Nov  1 12:53:55 localhost NetworkManager[1031]: <info> (em1): device state change: ip-config -> activated (reason 'none') [70 100 0]
Nov  1 12:53:55 localhost NetworkManager[1031]: NetworkManager[1031]: <info> (em1): device state change: ip-config -> activated (reason 'none') [70 100 0]
Nov  1 12:53:55 localhost ypbind[1140]: Host name lookup failure

So, NetworkManager is trying to call an init.d script, but nscd no longer _has_ an init.d script.


Version-Release number of selected component (if applicable):

NetworkManager-0.9.1.90-5.git20110927.fc16.i686
nscd-2.14.90-14.i686
ypbind-1.33-7.fc16.i686

How reproducible:

Always

Steps to Reproduce:
1.Configure a machine for NIS that requires DNS to find the NIS server
2.Boot the machine
  
Actual results:

Machine doesn't bind to the NIS successfully

Expected results:

Machine binds to the NIS successfully

Additional info:

Comment 1 John Beranek 2011-11-01 12:32:37 UTC
Note: This is with a 'yum upgrade'd Fedora 16 Beta.

Comment 2 Emilio Scalise 2011-11-14 09:59:56 UTC
I can confirm this bug on my machine. My installation is an upgrade from fedora 15 using preupgrade.

nscd-2.14.90-14.x86_64

NetworkManager-openconnect-0.9.0-3.fc16.x86_64
NetworkManager-vpnc-0.9.0-1.fc16.x86_64
NetworkManager-gtk-0.9.1.90-5.git20110927.fc16.x86_64
NetworkManager-gnome-0.9.1.90-5.git20110927.fc16.x86_64
NetworkManager-0.9.1.90-5.git20110927.fc16.x86_64
NetworkManager-pptp-0.9.0-1.fc16.x86_64
NetworkManager-glib-0.9.1.90-5.git20110927.fc16.x86_64
NetworkManager-openvpn-0.9.0-1.fc16.x86_64

Comment 3 Jerry James 2011-12-21 21:42:02 UTC
Just hit this bug.  Is a fix in the works?

Comment 4 John Beranek 2012-01-05 23:46:21 UTC
Created attachment 551042 [details]
Patch to be added to NetworkManager RPM

Here's a patch, in case it helps accelerate the fix.

Comment 5 John Beranek 2012-01-05 23:50:22 UTC
Created attachment 551044 [details]
Patch to be added to NetworkManager RPM

Removed noise from my patch, apologies for the noise.

Comment 6 Dan Winship 2012-05-02 17:33:58 UTC
*** Bug 759404 has been marked as a duplicate of this bug. ***

Comment 7 Ville Skyttä 2012-05-02 18:10:19 UTC
See also the other suggested patch in bug 759404 comment 1 - I believe that one should work in both sysv and systemd environments.

Comment 8 Fedora End Of Life 2013-01-16 13:07:31 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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 9 Fedora End Of Life 2013-02-13 13:47:27 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.