[#163] Avoiding to use 'latest' for critical packages wrt infrastruct…

…ure management
akvo · Apr 30, 2015 · 49ebcd1 · 49ebcd1
1 parent cdc55da
commit 49ebcd1
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/puppet/modules/puppetcontrol/manifests/init.pp b/puppet/modules/puppetcontrol/manifests/init.pp
@@ -26,7 +26,8 @@
     }
 
     package { 'puppetdb-terminus':
-        ensure => 'latest' #'1.6.3-1puppetlabs1'
+        # 'puppet' & 'puppet-common' packages are dependencies, so implicitly fixed to version '3.7.5-1puppetlabs1'
+        ensure => '2.3.3-1puppetlabs1'
     }
 
     # insert the ssh info

diff --git a/puppet/modules/puppetdb/manifests/server.pp b/puppet/modules/puppetdb/manifests/server.pp
@@ -13,7 +13,7 @@
         ensure => 'latest'
     } ->
     package { 'puppetdb':
-        ensure => 'latest' #'1.6.3-1puppetlabs1'  # version 2.0.0 refuses to start due to some obscure XML parsing issue
+        ensure => '2.3.3-1puppetlabs1'
     }
 
     service { 'puppetdb':