Also thinking... can we reproduce if we do the following: 1) allocate new baremetal instance 2) first boot fails to bring up network 3) reboot 4) second boot comes up (some of the time, right?) 5) login, rm -rf /var/log/cloud-init* /var/lib/cloud/* /etc/network/interfaces.d/* 6) reboot
If we're having issues with the devices becoming "up" on the switch, then we can simulate a fresh boot with the above but long after the switch will have seen the MAC addresses from the nics. We should see cloud-init from -proposed coming up just fine in that case. And we may need to see about adding some up-delay or poking the hosting provider for details w.r.t network switch config/nic config if there's stuff going on in the background that keeps the interfaces from coming up sooner. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684092 Title: cloud-init in xenial generates bond configs that do not appear to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1684092/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
