Bug 805313

Summary:	network is not started on boot.
Product:	[Retired] oVirt	Reporter:	Fabian Deutsch <fabian.deutsch>
Component:	ovirt-node	Assignee:	Mike Burns <mburns>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, fdeutsch, jboggs, mburns, ovirt-bugs, ovirt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.3.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-26 12:57:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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 ***