Bug 782102

Summary: [ovirtmgmt] [bridge] - fail to start bridge after restart due to eth link is not ready
Product: [Retired] oVirt Reporter: yeylon <yeylon>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED DUPLICATE QA Contact: yeylon <yeylon>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, bazulay, iheim, srevivo, ykaul
Target Milestone: ---Flags: danken: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-29 21:10:03 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:
Attachments:
Description Flags
log none

Description yeylon@redhat.com 2012-01-16 14:25:48 UTC
Created attachment 555522 [details]
log

Description of problem:

i've working with an IBM blade (2 of them) and from some reason the bridge is not not starting after reboot due to eth0 is not ready yet.
as a result the host will start with no network libvirt fail to start and so is vdsm.

we might need to consider adding "delay=0.1" in the bridge ifcfg file as we used to do in rhel.

adding messages.




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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dan Kenigsberg 2012-01-29 21:10:03 UTC
More details are available in bug 785557, I believe

*** This bug has been marked as a duplicate of bug 785557 ***