Bug 805947

Summary:	systemd kills dnsmasq if you stop openstack-nova-network
Product:	[Fedora] Fedora	Reporter:	Mark McLoughlin <markmc>
Component:	openstack-nova	Assignee:	Mark McLoughlin <markmc>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	akscram, alexander.sakhnov, asalkeld, bfilippov, jonathansteffan, markmc, matt_domsch, mlvov, p, rbryant, rkukura
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-2012.1-0.10.rc1.fc17	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-08 03:34:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mark McLoughlin 2012-03-22 14:21:39 UTC

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).

Comment 1 Fedora Update System 2012-03-26 09:11:50 UTC

openstack-nova-2011.3.1-6.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/openstack-nova-2011.3.1-6.fc16

Comment 2 Fedora Update System 2012-03-26 09:15:17 UTC

openstack-nova-2012.1-0.9.rc1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/openstack-nova-2012.1-0.9.rc1.fc17

Comment 3 Fedora Update System 2012-03-28 05:56:38 UTC

Package openstack-nova-2012.1-0.9.rc1.fc17:
* 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:
https://admin.fedoraproject.org/updates/FEDORA-2012-4798/openstack-nova-2012.1-0.9.rc1.fc17
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-03-29 19:01:14 UTC

openstack-nova-2012.1-0.10.rc1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/openstack-nova-2012.1-0.10.rc1.fc17

Comment 5 Fedora Update System 2012-03-30 01:29:53 UTC

openstack-nova-2011.3.1-7.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/openstack-nova-2011.3.1-7.fc16

Comment 6 Fedora Update System 2012-04-08 03:34:47 UTC

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.

Comment 7 Fedora Update System 2012-04-12 03:00:34 UTC

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.