See bug #805942 for a description of a similar bug with libvirt.
The restart issue doesn't apply to nova, since I nova will start dnsmasq again on startup.
So, KillMode=process might be enough for us, but I do worry about whether that means we might leak other processes that we'd prefer not to leak.
This is important, because the theory with upgrades is that you should be able to should down all the services for a period while leaving the instances running. If we kill dnsmasq, however, that means that instances will lose network connectivity when they try to renew their lease (after 2 minutes by default).
openstack-nova-2011.3.1-6.fc16 has been submitted as an update for Fedora 16.
openstack-nova-2012.1-0.9.rc1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openstack-nova-2012.1-0.9.rc1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
openstack-nova-2012.1-0.10.rc1.fc17 has been submitted as an update for Fedora 17.
openstack-nova-2011.3.1-7.fc16 has been submitted as an update for Fedora 16.
openstack-nova-2011.3.1-7.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
openstack-nova-2012.1-0.10.rc1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.