On Tue, 30 May 2017 21:23:58 +0200 Emmanuel Kasper <[email protected]> wrote:
> Than you for the detailed bug report. > > I understand the unstable network card ordering can perturbate the > network config if the NIC is assigned the name eth1 instead of eth0. > But I am wondering why is that changing the type of the second NIC > make the device ordering stable. > Are you sure this fixes the issue ? I've been thinking about it a bit. It could be a "race" between which kernel module gets initialised first? This is highly hypothetical from my side, mind you, just one thing that pops to my mind. I would need to read up quite a bit on the topic to be sure. So, if you use same network adapter type everywhere, same module gets used, and possibly the OS/kernel will always have the same ordering of network cards. Or... It could be dependant on network module implementation itself as well :) As for the fix, I have been bringing machines up and down a bunch of times since applying workaround in the Vagrantfile, and it has worked flawlessly. The moment I remove the configuration, I start getting failures. Practically no two consecutive "vagrant up" runs will bring-up the network interfaces correctly in a batch of about 6-7 machines that get set-up. Best regards -- Branko Majic XMPP: [email protected] Please use only Free formats when sending attachments to me. Бранко Мајић XMPP: [email protected] Молим вас да додатке шаљете искључиво у слободним форматима.
