** Impact ** When using nova with quantum network manager, dnsmasq is started after nova-network has been restarted therefore no new IP addresses for isntances.
** Development Fix ** This has been fixed in the development release in https://review.openstack.org/6452 and fixed in quantal. ** Stable fix ** This has been fixed in the stable/essex tree in https://review.openstack.org/7267 ** Test Case ** Scenario : 1. nova is configured to use QuantumManager 2. VMs are running 3. nova-network process is stopped/killed 4. All dnsmasq processes are killed 5. nova-network is restarted Expected Result : dnsmasq should be restarted when nova-network process comes up Actual Result : dnsmasq process is NOT started by nova-network during initialization ** Regression Impact ** Minimal this is a non-standard case on Ubuntu. ** Summary changed: - With QuantumManager, nova-network does not start dnsmasq during initialization + [SRU] With QuantumManager, nova-network does not start dnsmasq during initialization -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/977759 Title: [SRU] With QuantumManager, nova-network does not start dnsmasq during initialization To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/977759/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
