Bug 859190 - NetworkManager-wait-online fails at boot
NetworkManager-wait-online fails at boot
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-09-20 14:49 EDT by Ray Mikkelson
Modified: 2013-02-13 08:56 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 911289 (view as bug list)
Last Closed: 2013-02-13 08:56:45 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/messages for 3 separate boot sequences (46.92 KB, application/octet-stream)
2012-09-20 14:49 EDT, Ray Mikkelson
no flags Details

  None (edit)
Description Ray Mikkelson 2012-09-20 14:49:19 EDT
Created attachment 615047 [details]
/var/log/messages for 3 separate boot sequences

Description of problem:

NetworkManager-wait-online.service fails at boot every time.  Typically at 31-32 seconds after boot, the following prints to /var/log/messages:

Sep 19 17:14:03 myserver systemd[1]: NetworkManager-wait-online.service: main process exited, code=exited, status=1
Sep 19 17:14:03 myserver systemd[1]: Unit NetworkManager-wait-online.service entered failed state.

/var/log/boot.log has:

Starting Network Manager Wait Online...
Failed to start Network Manager Wait Online

This is annoying because ypbind needs to wait for NetworkManager to come online/active before it tries to activate.  This then causes a domino effect resulting in other failures (cron, etc.)

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

NetworkManager.x86_64                   1:0.9.4-6.git20120521.fc16   @updates   

How reproducible:

Every time

Steps to Reproduce:
1. systemctl enable NetworkManager-wait-online.service
2. boot
Actual results:

Fails (see above)

Expected results:


Additional info:

systemctl status NetworkManager-wait-online.service

NetworkManager-wait-online.service - Network Manager Wait Online
	  Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service; enabled)
	  Active: failed since Wed, 19 Sep 2012 17:14:03 -0500; 19h ago
	Main PID: 914 (code=exited, status=1/FAILURE)
	  CGroup: name=systemd:/system/NetworkManager-wait-online.service

Server is a Dell Optiplex 390 with a Intel i5 2400 CPU with Intel H61 Express Chipset.
Comment 1 Fedora End Of Life 2013-01-16 08:14:32 EST
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: 
Comment 2 Fedora End Of Life 2013-02-13 08:56:48 EST
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.

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