Red Hat Bugzilla – Bug 486815
network not coming after boot without network manager
Last modified: 2009-12-18 03:00:10 EST
Description of problem:
network not coming up after boot
Version-Release number of selected component (if applicable):
system-config-network-cmd --profile common --activate
the interface is not comiong up. activating from the gui app works
# system-config-network-cmd --profile common --activate
Activating network device eth0, please wait...
An unhandled exception has occured. This is most likely a bug.
Please file a detailed bug report against the component system-config-network at
using the text below.
Summary: TB /usr/share/system-config-network/netconfpkg/NC_functions.py:581:generic_run_dialog:AttributeError: 'list' object has no attribute 'join'
Traceback (most recent call last):
File "/usr/sbin/system-config-network-cmd", line 378, in main
(ret, msg) = device.activate()
File "/usr/share/system-config-network/netconfpkg/NCDevice.py", line 516, in activate
dialog = dialog )
File "/usr/share/system-config-network/netconfpkg/NC_functions.py", line 581, in generic_run_dialog
log.log(1, "Running %s %s" % (command, argv.join()))
AttributeError: 'list' object has no attribute 'join'
Local variables in innermost frame:
errlabel: Cannot activate network device eth0!
title: Network device activating...
argv: ['/sbin/ifup', 'eth0', 'up']
label: Activating network device eth0, please wait...
catchfd: (1, 2)
select: <module 'select' from '/usr/lib/python2.5/lib-dynload/selectmodule.so'>
Because NetworkManager also clears the DNS settings on boot (reported in another bug), but the interface(s) don't come up after boot without being controlled by NetworkManager, there is no way to configure a Fedora 10 system to be rebooted successfully without intelligent manual intervention to reconfigure the network immediately after booting. This is a show-stopper for us, since the system cannot automatically recover from power failures or be restarted remotely during maintenance. This is especially troublesome if multiple systems are involved.
Please change the priority to high. I would say urgent, but time has run out already, it's too late, and I don't have enough time to fix it myself before the deadline.
I saw from another post that "yum remove NetworkManager" then using system-config-services to enable the "network" service fixes these problems.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.