[SOLVED] Interface Configuration Loop

Started by ericdude101, February 22, 2017, 12:24:11 AM

Previous topic - Next topic
February 22, 2017, 12:24:11 AM Last Edit: February 22, 2017, 09:01:07 AM by franco
Hello,

Im trying to resolve an issue with a new installation, I was able to get everything installed and setup without issue EXCEPT:

I'm using a three NIC setup to have an out of band management port which I was able to configure and have work exactly as expected, but as soon as I reboot I see the message during boot that says "Default interfaces not found -- Running interface assignment option." which is totally automated and reset all my interface config and breaks my setup.

Is this a self-healing option I can simply disable or is this a software bug of some sort?

If interfaces go away during boot, the system tries to recover into a good known state based on the interfaces that are present in the system.

Are you using a USB NIC? If the NIC takes too long to be visible or changes its name, there's a problem. There are scripting workarounds for this in the form of boot delays we could try.

I did end up enabling a delay in the loader.config file which appears to have fixed it

There's a plugin for that: os-boot-delay. /boot/loader.conf changes are not permanent. Either use the plugin (it has a fixed 10 seconds delay at this time) or edit /boot/loader.conf.local instead.


Cheers,
Franco

The file /boot/loader.conf.local doesn't exist. I actually enabled the delay in the file located at /boot/defaults/loader.conf

Quote from: ericdude101 on February 24, 2017, 01:42:20 AM
The file /boot/loader.conf.local doesn't exist. I actually enabled the delay in the file located at /boot/defaults/loader.conf


/boot/defaults/loader.conf is also not persistent, any changes will be lost in an upgrade.

Either create the file /boot/loader.conf.local and put the changes there, or install the os-boot-delay plugin as franco said.