From bfa9f0aa3e9dfc6dd50a000bf59c06feb07144e8 Mon Sep 17 00:00:00 2001 From: Clayton O'Neill Date: Sat, 6 Jun 2015 12:20:26 +0000 Subject: [PATCH] Run db_sync when heat-common is upgraded The other packages appear to already have this, but heat-common isn't triggering a db sync, and at least on Ubuntu, if this package is upgraded first, all the others get pulled in also. When that happens, Puppet doesn't trigger a notification for the other packages and the db sync is never run. Change-Id: I454220ee6c501c416b60564fd3b1f00fdecfd296 --- manifests/init.pp | 1 + spec/classes/heat_init_spec.rb | 5 +++++ 2 files changed, 6 insertions(+) diff --git a/manifests/init.pp b/manifests/init.pp index c20b3c8c..9a2d87b2 100644 --- a/manifests/init.pp +++ b/manifests/init.pp @@ -521,6 +521,7 @@ class heat( user => 'heat', refreshonly => true, logoutput => on_failure, + subscribe => Package['heat-common'], } } } diff --git a/spec/classes/heat_init_spec.rb b/spec/classes/heat_init_spec.rb index 52f20349..533c5921 100644 --- a/spec/classes/heat_init_spec.rb +++ b/spec/classes/heat_init_spec.rb @@ -122,6 +122,11 @@ describe 'heat' do ) end + it 'has db_sync enabled' do + is_expected.to contain_exec('heat-dbsync').with( + :subscribe => 'Package[heat-common]', + ) + end it 'configures debug and verbose' do is_expected.to contain_heat_config('DEFAULT/debug').with_value( params[:debug] )