Bug 805313 - network is not started on boot.
Summary: network is not started on boot.
Keywords:
Status: CLOSED DUPLICATE of bug 806347
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Mike Burns
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 20:42 UTC by Fabian Deutsch
Modified: 2016-04-27 04:49 UTC (History)
6 users (show)

Fixed In Version: 2.3.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-26 12:57:04 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 43781 0 master MERGED init: Restart networking early during boot Never

Description Fabian Deutsch 2012-03-20 20:42:15 UTC 
Description of problem:
The configured network of a freshly installed node is not brought up after reboot.

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

How reproducible:
always

Steps to Reproduce:
1. install node
2. configure network (e.g. static)
3. reboot
  
Actual results:
Status page says: not connected

Expected results:
Node is connected

Additional info:
A workaround is running
systemctl restart network.service
Comment 1 Fabian Deutsch 2012-03-22 21:13:48 UTC 
<apevec> ah I know, readonly will bindmount only over files which exist in rootfs
<apevec> which is not the case for ifcfg-*
<fabiand> ahh - nice
<apevec> that's why we had mount_config in ovirt-early
<apevec> where we create target mountpoints for all files in /config
<apevec> which again works for locations in rwtab
<apevec> (those are bindmounted on tmpfs earlier)
Comment 2 Fabian Deutsch 2012-03-22 21:22:30 UTC 
http://gerrit.ovirt.org/#change,3046
Comment 3 Fabian Deutsch 2012-03-26 12:57:04 UTC 

*** This bug has been marked as a duplicate of bug 806347 ***
Note You need to log in before you can comment on or make changes to this bug.