Bug 470467
Summary: | Ethernet does not start at boot time | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jean Francois Martinez <jfm512> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | medium | ||
Version: | 10 | CC: | adam, lex.lists, notting, rvokal, tim |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-11 21:43:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jean Francois Martinez
2008-11-07 11:06:13 UTC
What happens when you do /etc/init.d/network restart? Note that you'll have to specifically enable the network service with chkconfig to have it start on boot. When I submitted the bug it did nothing. In fact it stopped the ethernet I had started manually and didn't restart it. After today's updates and the enabling of networking the problem has disappeared. It is a bizarre decison after 14 years of enabling networking by default that RedHat/Fedora has dedided to no longer do it. In fact from a usability viewpoint it is a bug since many users will be surprised by the new behavior. Do you have NetworkManager installed? Yes it is I did a default install. This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Please attach your ifcfg files, and the output of: chkconfig --list network chkconfig --list NetworkManager This looks like a duplicate of 467946. Is this still an issue for the reporter? If so, can you please provide the info Bill has requested. Problem is not present in the definitive release. You may close the bug. |