From 434397fc0df716595d9649b8b6232fff629ad9a9 Mon Sep 17 00:00:00 2001
From: Clark Boylan <clark.boylan@gmail.com>
Date: Thu, 23 Oct 2014 16:01:05 -0700
Subject: [PATCH] Stop notifying nodepool on log config changes

Previously puppet would restart nodepool whenever the nodepool log
config changes. This is problematic because nodepool will try to do a
graceful shutdown which can take hours. During this time period no new
nodes are built. Stop doing this and rely on manual nodepool restarts
(which is status quo for any other nodepool changes).

Change-Id: I522070df96d4e455a2c478bcf832ae6bb8729bf2
---
 modules/nodepool/manifests/init.pp | 1 -
 1 file changed, 1 deletion(-)

diff --git a/modules/nodepool/manifests/init.pp b/modules/nodepool/manifests/init.pp
index bc9ff26b2f..eef0b7de05 100644
--- a/modules/nodepool/manifests/init.pp
+++ b/modules/nodepool/manifests/init.pp
@@ -227,7 +227,6 @@ class nodepool (
     owner   => 'root',
     group   => 'root',
     content => template('nodepool/nodepool.logging.conf.erb'),
-    notify  => Service['nodepool'],
   }
 
   file { '/etc/init.d/nodepool':