Bug 1332232 - hosted-engine --deploy errors out with code "29" -- "no link present"
Summary: hosted-engine --deploy errors out with code "29" -- "no link present"
Keywords:
Status: CLOSED DUPLICATE of bug 1233405
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: Network
Version: 2.0.0
Hardware: x86_64
OS: Linux
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Yedidyah Bar David
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-02 14:55 UTC by Daniel Beckman
Modified: 2017-05-11 09:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-04 08:25:57 UTC
oVirt Team: Network
mmirecki: needinfo+
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
ovirt hosted engine setup log (337.88 KB, text/plain)
2016-05-02 14:55 UTC, Daniel Beckman
no flags Details

Description Daniel Beckman 2016-05-02 14:55:57 UTC
Created attachment 1152983 [details]
ovirt hosted engine setup log

Description of problem:

When I run hosted-engine --deploy, it errors out with the error in summary. 
Some background: I have 10G Ethernet interfaces that take a while to start up - "ifup" run the first time fails with "..no link present". Running "ifup" a second time completes without error. As a workaround, my ifcfg file includes "LINKDELAY=10". But ovirt setup does not appear to support the LINKDELAY option. Per Edy Haas (ehaas):
"As an workaround, you could use a VDSM before_ifcfg_write hook to add this parameter for the specific nic.
Please open a bug on this so we can track it."


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

Latest release of 3.6 from standard oVirt repos


How reproducible:


Steps to Reproduce:
1. run "hosted-engine --depoy" using an Intel 10-Gigabit interface (X540-AT2) with delayed link initialization


Actual results:
Setup errors out with above error

Expected results:
Setup would be able to insert a delay so that interfaces that take longer to come up aren't immediately flagged as down

Additional info:

Log from setup attached.

Comment 1 Daniel Beckman 2016-05-02 17:13:02 UTC
Hello,

I'd like to try out the VDSM hook "before_ifcfg_write" but despite reading through the available documentation I'm not sure how to implement that.

Comment 2 Dan Kenigsberg 2016-05-04 08:25:57 UTC
Marcin, can you point Daniel to your sample ifcfg hook?

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

Comment 3 Marcin Mirecki 2016-06-27 13:17:41 UTC
There is a blog entry on this:
https://www.ovirt.org/blog/2016/05/modify-ifcfg-files/


Note You need to log in before you can comment on or make changes to this bug.