Is the first onboard nic the one you use?
If so, I would wager that the combination of that nic and that
switch/configuration has some long link-up time in play.
I’ve not seen it myself or had to use it myself, but I am aware that there is a
section of https://fedoraproject.org/wiki/Anaconda/NetworkIssues
Suggesting use of linksleep *if* this is the case.
From: Damir Krstic [mailto:damir.krs...@gmail.com]
Sent: Monday, May 08, 2017 3:01 PM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] dracut error with stateful image
Just checking to see if anyone knows about dracut error messages. We are
getting close to booting 700+ with this new image and I am afraid we will have
a lot of failures because of the dracut error.
Thanks,
Damir
On Mon, May 1, 2017 at 2:23 PM Damir Krstic
<damir.krs...@gmail.com<mailto:damir.krs...@gmail.com>> wrote:
We are in process of building a RH 7 stateful image on our cluster. After
setting a node to install with this image, sometimes we will see the following
error:
dracut-initqueue[736]: Warning: No carrier detected on interface eno1
Usually, resetting the node fixes this issue (node installs properly). We are
planning to take downtime in June and install all 700+ nodes with this image. I
would like to clear up this delay / error if at all possible before the
downtime.
Has anyone seen this issue before?
Thanks,
Damir
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
