Igor Zinovik 689f64984f Correctly kill nova-network forked dnsmasq processes ... Nova-network OCF script tries to stop dnsmasq processes that might be left after nova-network abnormal termination. It must do that to prevent appearence of two gateways and two DHCP servers in VM network. Right now script stops *all* dnsmasq processes it finds, but this way it kills dnsmasq processes that serves as upstream DNS server, which is managed by 'p_dns' pacemaker resource. Deadlock appears when 'p_vcenter_nova_network' resource tries to stop dnsmasq and 'p_dns' starts it again. Lets just find dnsmasq PIDs that were started by nova-network and terminate them. Change-Id: I4ec7a60e31a0ce02c1924e6294aa767ad840617d Closes-bug: #1458821		2015-06-12 18:12:25 +00:00
..
files	Correctly kill nova-network forked dnsmasq processes	2015-06-12 18:12:25 +00:00
lib/puppet/parser/functions	Refactored vmware class for multi HV	2015-02-18 14:28:27 +03:00
manifests	Merge "Fix cinder-vmware failing on Ubuntu"	2015-04-24 08:11:15 +00:00
spec	Remove workarounds after implementing dual hypervisor support	2015-04-01 12:39:12 +03:00
templates	Remove workarounds after implementing dual hypervisor support	2015-04-01 12:39:12 +03:00
.fixtures.yml	Use pacemaker puppet module instead of corosync for unit testing	2015-01-29 15:23:39 +03:00
Gemfile	configure nova-compute use one vsphere cluster	2014-12-17 22:52:14 +03:00
Rakefile	configure nova-compute use one vsphere cluster	2014-12-17 22:52:14 +03:00