Public bug reported:
in a multi-node setup, I was rebooting one compute node (having one active VM
alive),
after the hypervisor reboot, nova-compute tried to start up, but failed,
because it could
not set the MTU of the network interface br100, because this bridged virtual
interface does not exist, nor does vlan100, as both should.
I assume that the nova-compute process should be responsible for
recreating them after a reboot if they don't exist anymore (of course
they don't after a reboot).
Creating br100 and vlan100 and attaching vlan100 to br100 was a quick
workaround to actually let nova-compute be able to finally boot up the instance
again.
but the VM cannot configure its network anymore.
this behaviour is seriously reproducable.
** Affects: ubuntu
Importance: Undecided
Status: New
** Project changed: nova => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004774
Title:
nova-compute won't start up after host reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1004774/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
