[Puppet Users] Re: How to Prevent Both MySQL and Percona From Being Installed?

[Jochen Haeberle]

Hi,

well at least on my debian, the percona-server package "provides" mysql, a 
meta-package. Installing Percona sees to it that MySQL (or MariaDB) is 
purged from the system first. So the way I see it, you have no need to 
remove mysql from your machine. Just install percona-server, this will see 
to the removel of mysql.

Regards
Jochen

Am Mittwoch, 23. April 2014 22:57:09 UTC+2 schrieb Jon Forrest:
>
> I have an interesting problem (to me). I want to install Percona 
> mysql. This is easy. 
> But I also want to make sure regular MySQL isn't installed on the same 
> machine that's running Percona. 
>
> To install Percona, I have a resource like 
>
>   package { 
> 'percona-client': 
> name => 'Percona-Server-client-55', 
> ensure => installed, 
>   } 
>
> To make sure MySQL isn't installed I have 
>
>   package { 
> 'mysql': 
>   provider => "yum", 
>   ensure => purged, 
>   } 
>
> The problem is that Puppet tries to remove Percona, instead of MySQL. 
> This is because the Percona rpm provides the mysql feature. By this I mean 
> the output from 'yum provides mysql' contains (edited): 
>
> Percona-Server-client-55-5.5.36-rel34.2.el6.x86_64 : Percona Server - 
> Client 
> Repo: XXX 
> Matched from: 
> Other   : mysql 
>
> Percona-Server-client-55-5.5.36-rel34.2.el6.x86_64 : Percona Server - 
> Client 
> Repo: installed 
> Matched from: 
> Other   : Provides-match: mysql 
>
> Of course, trying to remove Percona fails because other things depend on 
> it, as they should. 
>
> The only ideas I have for removing MySQL, and not Percona, are: 
>
> 1) Use rpmrebuild to change what Percona provides 
> 2) Use something like (untested) 
>
> exec { "/usr/bin/yum -y remove mysql": 
>   onlyif => "/bin/rpm -qa |/bin/fgrep mysql" 
>
> 3) Just presume that MySQL won't be installed in the first place. 
> I could do this but I'd like my modules to be more accepting and 
> not require a specially prepared system. 
>
> Any suggestions? 
>
> Jon Forrest 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a6407d4a-3fdb-429f-aa94-dc259f220268%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppetlabs-mysql and Percona

[Jochen Haeberle]

Hi,

the module puppetlabs-mysql on the forge is tagged with percona, but I 
don't see a way to have the module install a Percona-Server. The module has 
providers for MySQL and MariaDB, but not Percona.

I tried working with puppetlabs-mysql, installing Percona with a 
package-resource ending with Percona-Server and MySQL beeing constantly 
installed and deinstalled.

What does everybody else use to manage a Percona-Server?


Thanks in advance

Jochen

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4660731a-b13c-45de-8002-80609d6a4773%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to find version of an application on nodes

[Jochen Haeberle]

Hi,

You could create a simple facter script to check for a installed software you 
are interested in.

The facter scripts are run on all nodes and you can check the result on each 
machine easily.

regards

> Am 25.01.2018 um 23:17 schrieb Brandon Blackmoor  >:
> 
> I apologize if this is a stupid question, but I am still a novice at Puppet. 
> I have been asked if it is possible to use Puppet to find out if an 
> application (apparmor, specifically) is installed on our various nodes 
> (Ubuntu servers, specifically). The nodes are all running puppet agent and so 
> on. We're currently running Puppet v2016.4.0.
> 
> Feel free to point me to existing documentation. I did search first, but my 
> search results either seemed irrelevant or involved way more than what I am 
> actually asking for. I'm not looking to write a new module, for example.
> 
> Thank you for any help or guidance you can offer.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/de967d90-53e8-4b7b-83bd-93592cc45a2d%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/F1530E6E-9821-41DD-9A21-B2621B5A786B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Unable to solve a require statement

[Jochen Haeberle]

Hi Peter,

Thanks for the tip. I tried that already, but it results in a

Error: Could not find resource 'Package[mysql-client]' in parameter 'require' 
(file: 
/etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
 line: 26) on node stretch.localdomain

I tried to require my profile::mysql class, where it set up the mailserver 
using puppetlabs-mysql, but this does not help.

Thanks,
Jochen

> Am 02.03.2018 um 19:08 schrieb P C Kroon  >:
> 
> Hi Jochen,
>  
> Try the following:
> require => [File[‘php-wpcli_latest_all.deb’], Package[‘mysql-client’]],
>  
> HTH
> Peter
>  
> From: Jochen Häberle 
> Sent: 02 March 2018 04:56
> To: puppet-users@googlegroups.com 
> Subject: [Puppet Users] Unable to solve a require statement
>  
> Hi,
>  
> I am having a problem installing wp-cli alongside MySQL on Debian 9.3 using 
> latest Puppet 5.4
>  
> I am using rotes and Profiles and in my wordpress.pp I have:
>  
> # WP-CLI
> # TODO install latest wp-cli
> file { 'php-wpcli_latest_all.deb':
>path => '/tmp/php-wpcli_latest_all.deb',
>ensure => 'file',
>source => 'puppet:///modules/profile/wordpress/php-wpcli_1.5.0_all.deb 
> ',
> }
>  
> package { 'wpcli':
>provider => dpkg,
>ensure   => installed,
>source   => '/tmp/php-wpcli_latest_all.deb',
> #   require  => File['php-wpcli_latest_all.deb'],
> #   require  => Service['mysql'],
> #   require  => Service['mysql'],
> }
>  
> You see some of the require Statements I already tried ;-)
>  
> To install MySQL (or MariaDB) I am using puppetlabs/mysql module from the 
> Forge. I am setting this up in a mysql Profile which I require in the former 
> mentioned wordpress.pp.
>  
> In my node definition, I include mysql.pp before wordpress.pp
>  
> The error I get is the following (among similar ones):
>  
> Error: Execution of '/usr/bin/dpkg --force-confold -i 
> /tmp/php-wpcli_latest_all.deb' returned 1: Selecting previously unselected 
> package php-wpcli.
> (Reading database ... 62113 files and directories currently installed.)
> Preparing to unpack /tmp/php-wpcli_latest_all.deb ...
> Unpacking php-wpcli (1.5.0) ...
> dpkg: dependency problems prevent configuration of php-wpcli:
> php-wpcli depends on mysql-client | mariadb-client; however:
>   Package mysql-client is not installed.
>   Package mariadb-client is not installed.
>  
> dpkg: error processing package php-wpcli (--install):
> dependency problems - leaving unconfigured
> Processing triggers for man-db (2.7.6.1-2) ...
> Errors were encountered while processing:
> php-wpcli
> Error: /Stage[main]/Profile::Software::Wordpress/Package[wpcli]/ensure: 
> change from 'purged' to 'present' failed: Execution of '/usr/bin/dpkg 
> --force-confold -i /tmp/php-wpcli_latest_all.deb' returned 1: Selecting 
> previously unselected package php-wpcli.
> (Reading database ... 62113 files and directories currently installed.)
> Preparing to unpack /tmp/php-wpcli_latest_all.deb ...
> Unpacking php-wpcli (1.5.0) ...
> dpkg: dependency problems prevent configuration of php-wpcli:
> php-wpcli depends on mysql-client | mariadb-client; however:
>   Package mysql-client is not installed.
>   Package mariadb-client is not installed.
>  
> dpkg: error processing package php-wpcli (--install):
> dependency problems - leaving unconfigured
> Processing triggers for man-db (2.7.6.1-2) ...
> Errors were encountered while processing:
> php-wpcli
>  
>  
> as I can install wp-cli using puppet when MySQL is already installed through 
> puppet, this is clearly an issue of sequence. But I cannot find a way to 
> solve this and to have MySQL installied before wp-cli.
>  
> Can anyone help me out, please?
>  
> Thanks, erhards
>  
> Jochen
>  
>  
>  
>   
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/19ADAF36-F85F-445E-AF5C-B59E47237BB8%40gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
>  
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/5a99930e.46d3620a.a69c6.203e%40mx.google.com
>  
> 

Re: [Puppet Users] Unable to solve a require statement

[Jochen Haeberle]

Hi Peter,

The MySQL profile does indeed install the MySQL-client. But I can’t require it 
in the other profile class.

In class profile::software::wordpress I put  require profile::software::mysql, 
where I call the puppetlabs-mysql module to do the actual installation. Is 
there a better way to  describe the dependency?

Jochen

> Am 05.03.2018 um 21:19 schrieb P C Kroon  <mailto:p.c.kr...@rug.nl>>:
> 
> Hi,
>  
> Make sure you have that module also install the MySQL client, and require 
> mysql::client. I’m deliberately vague on the exact syntax since I’m not sure.
>  
> Peter
>  
> From: Jochen Haeberle <mailto:jochen.haebe...@gmail.com>
> Sent: 03 March 2018 13:43
> To: puppet-users@googlegroups.com <mailto:puppet-users@googlegroups.com>
> Subject: Re: [Puppet Users] Unable to solve a require statement
>  
> Hi Peter,
>  
> Thanks for the tip. I tried that already, but it results in a
>  
> Error: Could not find resource 'Package[mysql-client]' in parameter 'require' 
> (file: 
> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
>  line: 26) on node stretch.localdomain
>  
> I tried to require my profile::mysql class, where it set up the mailserver 
> using puppetlabs-mysql, but this does not help.
>  
> Thanks,
> Jochen
>  
> Am 02.03.2018 um 19:08 schrieb P C Kroon  <mailto:p.c.kr...@rug.nl>>:
>  
> Hi Jochen,
>  
> Try the following:
> require => [File[‘php-wpcli_latest_all.deb’], Package[‘mysql-client’]],
>  
> HTH
> Peter
>  
> From: Jochen Häberle <mailto:jochen.haebe...@gmail.com>
> Sent: 02 March 2018 04:56
> To: puppet-users@googlegroups.com <mailto:puppet-users@googlegroups.com>
> Subject: [Puppet Users] Unable to solve a require statement
>  
> Hi,
>  
> I am having a problem installing wp-cli alongside MySQL on Debian 9.3 using 
> latest Puppet 5.4
>  
> I am using rotes and Profiles and in my wordpress.pp I have:
>  
> # WP-CLI
> # TODO install latest wp-cli
> file { 'php-wpcli_latest_all.deb':
>path => '/tmp/php-wpcli_latest_all.deb',
>ensure => 'file',
>source => 'puppet:///modules/profile/wordpress/php-wpcli_1.5.0_all.deb 
> ',
> }
>  
> package { 'wpcli':
>provider => dpkg,
>ensure   => installed,
>source   => '/tmp/php-wpcli_latest_all.deb',
> #   require  => File['php-wpcli_latest_all.deb'],
> #   require  => Service['mysql'],
> #   require  => Service['mysql'],
> }
>  
> You see some of the require Statements I already tried ;-)
>  
> To install MySQL (or MariaDB) I am using puppetlabs/mysql module from the 
> Forge. I am setting this up in a mysql Profile which I require in the former 
> mentioned wordpress.pp.
>  
> In my node definition, I include mysql.pp before wordpress.pp
>  
> The error I get is the following (among similar ones):
>  
> Error: Execution of '/usr/bin/dpkg --force-confold -i 
> /tmp/php-wpcli_latest_all.deb' returned 1: Selecting previously unselected 
> package php-wpcli.
> (Reading database ... 62113 files and directories currently installed.)
> Preparing to unpack /tmp/php-wpcli_latest_all.deb ...
> Unpacking php-wpcli (1.5.0) ...
> dpkg: dependency problems prevent configuration of php-wpcli:
> php-wpcli depends on mysql-client | mariadb-client; however:
>   Package mysql-client is not installed.
>   Package mariadb-client is not installed.
>  
> dpkg: error processing package php-wpcli (--install):
> dependency problems - leaving unconfigured
> Processing triggers for man-db (2.7.6.1-2) ...
> Errors were encountered while processing:
> php-wpcli
> Error: /Stage[main]/Profile::Software::Wordpress/Package[wpcli]/ensure: 
> change from 'purged' to 'present' failed: Execution of '/usr/bin/dpkg 
> --force-confold -i /tmp/php-wpcli_latest_all.deb' returned 1: Selecting 
> previously unselected package php-wpcli.
> (Reading database ... 62113 files and directories currently installed.)
> Preparing to unpack /tmp/php-wpcli_latest_all.deb ...
> Unpacking php-wpcli (1.5.0) ...
> dpkg: dependency problems prevent configuration of php-wpcli:
> php-wpcli depends on mysql-client | mariadb-client; however:
>   Package mysql-client is not installed.
>   Package mariadb-client is not installed.
>  
> dpkg: error processing package php-wpcli (--install):
> dependency problems - leaving unconfigured
> Processing triggers for man-db (2.7.6.1-2) ...
> Errors were encountered while processing:
> php-wpcli
>  
>  
> as I can install wp-cli using pupp

[Puppet Users] python Script with answer file not working

[Jochen Haeberle]

Hi,

I am trying to install seafile with Puppet. Puppet 5.5.1 on Debian 9.

seafile is installed with an interactive shellscript calling a python script. I 
prepared an answer file, which is interactively working fine, up until where 
the db password is asked for. The input there is handled differently, not 
echoed back to the prompt and the execution changes to interactively for the 
input.

The code part getting the user input looks like the following:

# prompt for user input
if password:
answer = getpass.getpass(desc).strip()
else:
answer = raw_input(desc).strip()

Is there a way to get this to work in Puppet? I tried with the following exec:

exec { 'run seafile installer w answers file':
command   => 
"/opt/seafile/${instanz}/${seafile_folder}/setup-seafile-mysql.py 
/opt/seafile/${instanz}/${seafile_folder}5/${instanz}-answers.txt",
creates   => "/opt/seafile/${instanz}/seafile-server-latest",
require   => Archive[$seafile_archive],
provider  => shell,
  }
but I get:

Notice: 
/Stage[main]/Role::Share_server/Archive[seafile-server_6.2.5_x86-64.tar.gz]/ensure:
 download archive from 
puppet:///modules/profile/seafile/seafile-server_6.2.5_x86-64.tar.gz 
 to 
/opt/seafile/installed/seafile-server_6.2.5_x86-64.tar.gz and extracted in 
/opt/seafile/test with cleanup
Notice: 
/Stage[main]/Role::Share_server/File[/opt/seafile/test/seafile-server-6.2.5/test-answers.txt]/ensure:
 defined content as '{md5}25f64045b6676488e407c84c6a18eb20'
Notice: /Stage[main]/Role::Share_server/Exec[run seafile installer w answers 
file]/returns: /bin/sh: 1: 
/opt/seafile/test/seafile-server-6.2.5/setup-seafile-mysql.py: Permission denied

Can it be done?

Thanks in advance

Jochen

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/460B6AC6-31F5-49E2-BA5D-F06F34DD112F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] work on config that does not exist on first run

[Jochen Haeberle]

Hi again,

as outlined in my last post, I am trying to setup seafile using Puppet 5.5.1 on 
Debian 9.

I am struggling with a script based installation. As a work around, I tried to 
separate the steps. I want to prepare an answer file for the setup script, run 
that and adjust the config on the second puppet run.

I am having two problems:

When the script is run, there exists a symlink in the filesystem. Following a 
recipt from not so long ago, I want to use this:

exec {"check_installed":
  command => '/bin/true',
  onlyif => "/usr/bin/test -e /opt/seafile/${instanz}/seafile-server-latest",
}

1) I want to move the data folder created by the installer to a networked 
folder and create a symlink afterwards. The exec moving the folder is waiting 
for the existence of the folder, but the file resource doing the link is always 
executing. It seems like Puppet behaviour changed massively from version 3 I 
cannot find a working solution for this except writing a fact, which seems not 
manageable, as a fact may not be parameterized.
Is there a way to control execution of a file resource?

This runs all the time:
file { "/opt/seafile/${instanz}/seafile-data":
  ensure  => 'link',
  target  => "/mnt/seafile/${instanz}/seafile-data",
  require => Exec['check_installed'],
}

after that, the seafile installer will not run through, as the data-folder is 
already there.

2) I need to change the ini-based config crated during the setup. Problem is 
similar, whatever I do, this always runs and gives me an error:
ini_setting { "URL ${instanz}":
  ensure  => present,
  path=> "/opt/seafile/${instanz}/conf/ccnet.conf",
  section => 'General',
  setting => 'SERVICE_URL',
  value   => "https://${url}";,
  require => Exec['check_installed'],
}
This is not that problematic, it gives an error, but puppet continues on. But I 
guess, I could run 1) as exec to solve it, but not 2)

Thanks for any advice, regards

Jochen

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/F8DB3F41-CC88-48D3-BC55-A1A047CCAEE8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] python Script with answer file not working

[Jochen Haeberle]

My Bad! While playing around, I produced a typo. The script that should be 
executed is a .sh, not .py :-(

Nevertheless… even on CLI the script does not run with the answer file alone. I 
have to enter the pw manually, then the automated run continues.

Regards
Jochen

> Am 17.05.2018 um 05:03 schrieb Red Cricket  <mailto:red.cricket.b...@gmail.com>>:
> 
> Notice what your error message is ...  
> /opt/seafile/test/seafile-server-6.2.5/setup-seafile-mysql.py: Permission 
> denied
> make sure that  /opt/seafile/test/seafile-server-6.2.5/setup-seafile-mysql.py 
> is executable 
> 
> On Wed, May 16, 2018 at 7:50 PM, 程伟  <mailto:chengwei201...@gmail.com>> wrote:
> 
> 
> 在 2018年5月16日星期三 UTC+8下午8:31:53，Jochen Haeberle写道：
> Hi,
> 
> I am trying to install seafile with Puppet. Puppet 5.5.1 on Debian 9.
> 
> seafile is installed with an interactive shellscript calling a python script. 
> I prepared an answer file, which is interactively working fine, up until 
> where the db password is asked for. The input there is handled differently, 
> not echoed back to the prompt and the execution changes to interactively for 
> the input.
> 
> The code part getting the user input looks like the following:
> 
> # prompt for user input
> if password:
> answer = getpass.getpass(desc).strip()
> else:
> answer = raw_input(desc).strip()
> 
> Is there a way to get this to work in Puppet? I tried with the following exec:
> 
> exec { 'run seafile installer w answers file':
> command   => 
> "/opt/seafile/${instanz}/${seafile_folder}/setup-seafile-mysql.py 
> /opt/seafile/${instanz}/${seafile_folder}5/${instanz}-answers.txt",
> creates   => "/opt/seafile/${instanz}/seafile-server-latest",
> require   => Archive[$seafile_archive],
> provider  => shell,
>   }
> but I get:
> 
> Notice: 
> /Stage[main]/Role::Share_server/Archive[seafile-server_6.2.5_x86-64.tar.gz]/ensure:
>  download archive from 
> puppet:///modules/profile/seafile/seafile-server_6.2.5_x86-64.tar.gz <> to 
> /opt/seafile/installed/seafile-server_6.2.5_x86-64.tar.gz and extracted in 
> /opt/seafile/test with cleanup
> Notice: 
> /Stage[main]/Role::Share_server/File[/opt/seafile/test/seafile-server-6.2.5/test-answers.txt]/ensure:
>  defined content as '{md5}25f64045b6676488e407c84c6a18eb20'
> Notice: /Stage[main]/Role::Share_server/Exec[run seafile installer w answers 
> file]/returns: /bin/sh: 1: 
> /opt/seafile/test/seafile-server-6.2.5/setup-seafile-mysql.py: Permission 
> denied
> 
> Can it be done?
> 
> Thanks in advance
> 
> Jochen
> 
> I think it is a problem about command in exec resource. Why not try  
> "/opt/seafile/${instanz}/${seafile_folder}/setup-seafile-mysql.py 
> /opt/seafile/${instanz}/${seafile_folder}5/${instanz}-answers.txt" in your 
> shell? Or try "python 
> /opt/seafile/${instanz}/${seafile_folder}/setup-seafile-mysql.py 
> /opt/seafile/${instanz}/${seafile_folder}5/${instanz}-answers.txt"? When you 
> make it works in shell, then try it in puppet. 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> <mailto:puppet-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/92b21e37-9ecc-49dd-8d61-4f522278d54e%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/puppet-users/92b21e37-9ecc-49dd-8d61-4f522278d54e%40googlegroups.com?utm_medium=email&utm_source=footer>.
> 
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> <mailto:puppet-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/CAHu%2B3OxWr3b5aeWeB6%2BNYShwtc3j_L5XNOGSyivi9CQsO48pMA%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/puppet-users/CAHu%2B3OxWr3b5aeWeB6%2BNYShwtc3j_L5XNOGSyivi9CQsO48pMA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/D2C03B18-7CD7-4B3F-960C-8648AD6AA634%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] python Script with answer file not working

[Jochen Haeberle]

Thanks! There was an error in the resource. Should be setup-seafile-mysql.sh. 
(not .py)

But it does not work anyway :-/

even on cli, execution of the script with the answer file stops at the pw 
enter. After manually entering the pw, the automated execution continues.

Greetings
Jochen

> Am 17.05.2018 um 05:03 schrieb Red Cricket  <mailto:red.cricket.b...@gmail.com>>:
> 
> Notice what your error message is ...  
> /opt/seafile/test/seafile-server-6.2.5/setup-seafile-mysql.py: Permission 
> denied
> make sure that  /opt/seafile/test/seafile-server-6.2.5/setup-seafile-mysql.py 
> is executable 
> 
> On Wed, May 16, 2018 at 7:50 PM, 程伟  <mailto:chengwei201...@gmail.com>> wrote:
> 
> 
> 在 2018年5月16日星期三 UTC+8下午8:31:53，Jochen Haeberle写道：
> Hi,
> 
> I am trying to install seafile with Puppet. Puppet 5.5.1 on Debian 9.
> 
> seafile is installed with an interactive shellscript calling a python script. 
> I prepared an answer file, which is interactively working fine, up until 
> where the db password is asked for. The input there is handled differently, 
> not echoed back to the prompt and the execution changes to interactively for 
> the input.
> 
> The code part getting the user input looks like the following:
> 
> # prompt for user input
> if password:
> answer = getpass.getpass(desc).strip()
> else:
> answer = raw_input(desc).strip()
> 
> Is there a way to get this to work in Puppet? I tried with the following exec:
> 
> exec { 'run seafile installer w answers file':
> command   => 
> "/opt/seafile/${instanz}/${seafile_folder}/setup-seafile-mysql.py 
> /opt/seafile/${instanz}/${seafile_folder}5/${instanz}-answers.txt",
> creates   => "/opt/seafile/${instanz}/seafile-server-latest",
> require   => Archive[$seafile_archive],
> provider  => shell,
>   }
> but I get:
> 
> Notice: 
> /Stage[main]/Role::Share_server/Archive[seafile-server_6.2.5_x86-64.tar.gz]/ensure:
>  download archive from 
> puppet:///modules/profile/seafile/seafile-server_6.2.5_x86-64.tar.gz <> to 
> /opt/seafile/installed/seafile-server_6.2.5_x86-64.tar.gz and extracted in 
> /opt/seafile/test with cleanup
> Notice: 
> /Stage[main]/Role::Share_server/File[/opt/seafile/test/seafile-server-6.2.5/test-answers.txt]/ensure:
>  defined content as '{md5}25f64045b6676488e407c84c6a18eb20'
> Notice: /Stage[main]/Role::Share_server/Exec[run seafile installer w answers 
> file]/returns: /bin/sh: 1: 
> /opt/seafile/test/seafile-server-6.2.5/setup-seafile-mysql.py: Permission 
> denied
> 
> Can it be done?
> 
> Thanks in advance
> 
> Jochen
> 
> I think it is a problem about command in exec resource. Why not try  
> "/opt/seafile/${instanz}/${seafile_folder}/setup-seafile-mysql.py 
> /opt/seafile/${instanz}/${seafile_folder}5/${instanz}-answers.txt" in your 
> shell? Or try "python 
> /opt/seafile/${instanz}/${seafile_folder}/setup-seafile-mysql.py 
> /opt/seafile/${instanz}/${seafile_folder}5/${instanz}-answers.txt"? When you 
> make it works in shell, then try it in puppet. 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> <mailto:puppet-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/92b21e37-9ecc-49dd-8d61-4f522278d54e%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/puppet-users/92b21e37-9ecc-49dd-8d61-4f522278d54e%40googlegroups.com?utm_medium=email&utm_source=footer>.
> 
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> <mailto:puppet-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/CAHu%2B3OxWr3b5aeWeB6%2BNYShwtc3j_L5XNOGSyivi9CQsO48pMA%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/puppet-users/CAHu%2B3OxWr3b5aeWeB6%2BNYShwtc3j_L5XNOGSyivi9CQsO48pMA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/B44B56F7-F7F5-43FC-A2E3-3BC8AF1FF7F5%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] python Script with answer file not working

[Jochen Haeberle]

Hi John,

> Am 17.05.2018 um 15:23 schrieb jcbollinger  >:
> 
> If it is available, by far the easiest and most robust way to install almost 
> any software -- puppet or no puppet -- is via an installation package for 
> your system's particular package management system.  I.e. an RPM on 
> RedHat-family and some other Linuxes, a DEB on Debian-family Linuxes, etc.. 

Definitely!

> Ideally, the package provider puts it in a package repository, but there are 
> ways to handle it even if they don't.It looks like there may even be 
> official Debian packages for Seafile 
>  (I googled 
> "seafile deb"), so I would definitely look in that direction.

I was not able to find any server packages. What you point to is a client, 
that’s a different story.

I guess this interactive installer script is a sort of cripple ware. There is a 
pro version, offering a scripted installation :-(

I managed to install seafile by now with a lot of puppet support in three 
phases:

1) Puppet: install files, prepare db, generate answer file, print reminder
2) Manual script run, entering db-password
3) Puppet: Setup Nginx, Let’s encrypt and move folders to network device

I do not really like this, but I do not see any other solution at the moment. I 
might easily run into concurrency issues

Thanks for your advice!

Greetings
Jochen


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3D9A1398-BDC2-4504-B937-4A4C4FB7D64E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Problem with adding apt repo source

[Jochen Haeberle]

Hi,

I am trying to add PHP 7.3 to some of my debian 9 boxes.

I am using puppetlabs/apache to setup apache and PHP. I want to add an apt repo 
(sury.org) with PHP 7.3 to the system. I am using puppetlabs/apt for that

I am having problems to first add the repo, run apt update and then setup 
apache. Whatever I do, the 7.3 packets are not available. To make things more 
complex, the sury repo requires ssl meaning some more packages to be available 
upfront.

I found the following discussion on problems with puppetlabs/apt to run apt 
update after adding a source but I cannot get the solution outlined to work: 
https://tickets.puppetlabs.com/browse/MODULES-2190


Here is my testing class:

class test_php {

#  Apt::Source <| |> ~> Class['apt::update'] -> Package <| |>

  include profile::base

  ensure_packages([
'software-properties-common',
'dirmngr',
'apt-transport-https',
'lsb-release',
'ca-certificates',
  ])

  exec { 'retrieve_sury_key':
command => "/usr/bin/wget -q https://packages.sury.org/php/apt.gpg -O 
/etc/apt/trusted.gpg.d/sury-php.gpg",
creates => "/etc/apt/trusted.gpg.d/sury-php.gpg",
  }
  file { '/etc/apt/trusted.gpg.d/sury-php.gpg':
mode=> '0755',
require => Exec["retrieve_sury_key"],
  }

  apt::source { 'sury_php':
comment   => 'This is the Sury PHP package repo',
location  => 'https://packages.sury.org/php/',
release   => 'stretch',
repos => 'main ',
notify_update => true,
require   => Package['software-properties-common', 'dirmngr', 
'apt-transport-https', 'lsb-release', 'ca-certificates',],
  }

  class { 'apache':
default_vhost => true,
default_mods  => false,
mpm_module=> 'prefork',

  }
  class { 'apache::mod::php':
php_version => '7.3'
  }
}

the commented line is the solution from the referenced ticket on apt, but it 
renders a circular dependency. The code as posted works on the second run, but 
gives the following error on the first run:

Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold 
install libapache2-mod-php7.3' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package libapache2-mod-php7.3
E: Couldn't find any package by glob 'libapache2-mod-php7.3'
E: Couldn't find any package by regex 'libapache2-mod-php7.3'
Error: 
/Stage[main]/Apache::Mod::Php/Apache::Mod[php7.3]/Package[libapache2-mod-php7.3]/ensure:
 change from 'purged' to 'present' failed: Execution of '/usr/bin/apt-get -q -y 
-o DPkg::Options::=--force-confold install libapache2-mod-php7.3' returned 100: 
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package libapache2-mod-php7.3
E: Couldn't find any package by glob 'libapache2-mod-php7.3'
E: Couldn't find any package by regex 'libapache2-mod-php7.3'
Notice: /Stage[main]/Apache/File[/etc/apache2/conf.d]: Dependency 
Package[libapache2-mod-php7.3] has failures: true
Warning: /Stage[main]/Apache/File[/etc/apache2/conf.d]: Skipping because of 
failed dependencies
Notice: /Stage[main]/Apache::Mod::Php/File[php7.3.conf]: Dependency 
Package[libapache2-mod-php7.3] has failures: true
Warning: /Stage[main]/Apache::Mod::Php/File[php7.3.conf]: Skipping because of 
failed dependencies


I could not find any working solution anywhere, all examples available seem to 
be for pretty old code.

Thanks in advance, regards

Jochen


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/03FAFC6A-B1D4-434C-B103-FD957044E28A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] ensure_packets not working

[Jochen Haeberle]

Hi,

I am using serverless puppet apply on some nodes. I prepared a set of manifests 
using forge plugins. I developed everything using Vagrant quite fine.

Now I put my code via git on a debian 9.7 VM with puppet 6.2 and am getting the 
following errors:

Error: Evaluation Error: Error while evaluating a Function Call, Duplicate 
declaration: Package[libapache2-mod-php7.3] is already declared at (file: 
/etc/puppetlabs/code/environments/production/modules/profile/manifests/software/apache.pp,
 line: 78); cannot redeclare (file: 
/etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
 line: 24) (file: 
/etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
 line: 24, column: 3)

Both instances use the stdlib function ensure_packages. If I remove one of the 
instances, I will get the error with another package.

puppetlabs/stdlib and all other modules are up to date, thanks to r10k, Code is 
working on a fresh vagrant machine.

What can be the culprit of this? I have no idea where to look for this problem.

Thanks in advance vor any hints, regards

Jochen

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1FF3C627-8E25-44EE-B188-5C23C3887BB1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: ensure_packets not working

[Jochen Haeberle]

Hi @all,

does anyone have an idea what could be happening? I think this might be 
some sort of configuration error on the node, on the other hand, puppet 
obviously seems able to compile a catalog.
What could be the reason for such a difference in behaviour on Debian 9.7 
either on Vagrant or VMware?

Thanks for any hints, regards

Jochen

Am Dienstag, 29. Januar 2019 00:02:42 UTC+1 schrieb Jochen Haeberle:
>
> Hi, 
>
> I am using serverless puppet apply on some nodes. I prepared a set of 
> manifests using forge plugins. I developed everything using Vagrant quite 
> fine. 
>
> Now I put my code via git on a debian 9.7 VM with puppet 6.2 and am 
> getting the following errors: 
>
> Error: Evaluation Error: Error while evaluating a Function Call, Duplicate 
> declaration: Package[libapache2-mod-php7.3] is already declared at (file: 
> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/apache.pp,
>  
> line: 78); cannot redeclare (file: 
> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
>  
> line: 24) (file: 
> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
>  
> line: 24, column: 3) 
>
> Both instances use the stdlib function ensure_packages. If I remove one of 
> the instances, I will get the error with another package. 
>
> puppetlabs/stdlib and all other modules are up to date, thanks to r10k, 
> Code is working on a fresh vagrant machine. 
>
> What can be the culprit of this? I have no idea where to look for this 
> problem. 
>
> Thanks in advance vor any hints, regards 
>
> Jochen

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4e0cd8c4-577f-42a6-a664-e6f4015fca5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: ensure_packets not working

[Jochen Haeberle]

are/apache.pp,
 
line: 78); cannot redeclare (file: 
/etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
 
line: 24) (file: 
/etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
 
line: 24, column: 3) on node my.host.name

I recreated my Vagrant machine, works like a charm. Both machines run 
Puppet 6.2.0 on Debian 9.7

Sorry for the extensive post, this is because I do not have any clue where 
to look.

Thanks, regards

Jochen


Am Mittwoch, 30. Januar 2019 22:40:26 UTC+1 schrieb Ben Ford:
>
> Sharing the code that you're working with will make it possible for people 
> to help solve your problem.
>
> On Wed, Jan 30, 2019 at 10:22 AM Jochen Haeberle  > wrote:
>
>> Hi @all,
>>
>> does anyone have an idea what could be happening? I think this might be 
>> some sort of configuration error on the node, on the other hand, puppet 
>> obviously seems able to compile a catalog.
>> What could be the reason for such a difference in behaviour on Debian 9.7 
>> either on Vagrant or VMware?
>>
>> Thanks for any hints, regards
>>
>> Jochen
>>
>> Am Dienstag, 29. Januar 2019 00:02:42 UTC+1 schrieb Jochen Haeberle:
>>>
>>> Hi, 
>>>
>>> I am using serverless puppet apply on some nodes. I prepared a set of 
>>> manifests using forge plugins. I developed everything using Vagrant quite 
>>> fine. 
>>>
>>> Now I put my code via git on a debian 9.7 VM with puppet 6.2 and am 
>>> getting the following errors: 
>>>
>>> Error: Evaluation Error: Error while evaluating a Function Call, 
>>> Duplicate declaration: Package[libapache2-mod-php7.3] is already declared 
>>> at (file: 
>>> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/apache.pp,
>>>  
>>> line: 78); cannot redeclare (file: 
>>> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
>>>  
>>> line: 24) (file: 
>>> /etc/puppetlabs/code/environments/production/modules/profile/manifests/software/wordpress.pp,
>>>  
>>> line: 24, column: 3) 
>>>
>>> Both instances use the stdlib function ensure_packages. If I remove one 
>>> of the instances, I will get the error with another package. 
>>>
>>> puppetlabs/stdlib and all other modules are up to date, thanks to r10k, 
>>> Code is working on a fresh vagrant machine. 
>>>
>>> What can be the culprit of this? I have no idea where to look for this 
>>> problem. 
>>>
>>> Thanks in advance vor any hints, regards 
>>>
>>> Jochen
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/4e0cd8c4-577f-42a6-a664-e6f4015fca5d%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/puppet-users/4e0cd8c4-577f-42a6-a664-e6f4015fca5d%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d79b17e4-9eb8-455b-89a1-afdf86f743b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: ensure_packets not working

[Jochen Haeberle]

Hi John,

thanks for your support! I see your point, especially with the different use of 
notify.

It’s disapointing to hear one should still keep away from ensure_packages, as 
it greatly helps me to install packages only when needed. This goes mostly for 
apache modules and php extensions in my case.

I will try to prepare a simple test which I can share.

Nevertheless the question remains why the code is working in my dev 
environment. Both environments are the same as much as you can get.

Regards
Jochen

> Am 31.01.2019 um 15:28 schrieb jcbollinger :
> 
> 
> 
> On Thursday, January 31, 2019 at 8:00:05 AM UTC-6, jcbollinger wrote:
> 
> As long as I'm standing on this soapbox, though, I'd like to remark that 
> ensure_packages() is a jerry-rig, not an actual solution to any Puppet 
> problem.  It and its brethren, ensure_package(), ensure_resources(), and 
> ensure_resource() should be avoided.
> 
> Oops: there is no ensure_package().  But the point remains.
> 
> As for the code you've presented, it indeed does reveal a problem, which is 
> also illustrative of my soapbox position.  One of the larger issues here 
> revolves around what to do when there are two or more declarations of a 
> resource that specify different parameters.  The two parameter lists cannot 
> both be satisfied (generally speaking), so which do we choose?  In fact, the 
> functions in question make the safe choice: none of the above.  Per the docs 
> for ensure_resource() 
> :
> 
> If the resource already exists, but does not match the specified parameters, 
> this function attempts to recreate the resource, leading to a duplicate 
> resource definition error.
> 
> In your case, one declaration of Package[libapache2-mod-php7.3] has a notify 
> parameter and the other does not.
> 
> There are several ways you might refactor this to solve the specific problem, 
> but I would suggest one of these:
> moving management of mod_php out of the apache profile
> My first inclination would be to put it in its own profile, or at least in 
> its own class, but
> you could also leave it as a responsibility of the Wordpress profile
> moving management of mod_php out of the Wordpress profile
> Again, you could put it in its own class or profile, but
> you could also let the Apache profile continue to manage it, possibly under 
> control of a class parameter
> Of course, you could also just ensure that the specified parameters are 
> identical in both places, but if you're relying on ensure_packages / 
> _resources / _resource a lot, then you will likely find that that becomes 
> tedious and error-prone.
> 
> 
> John
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/b67eecc5-1145-4eff-8d6b-fbf8808236e3%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/00300BBF-1BD4-43F4-A345-5D9707F53926%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] refactor use of ensure_packages to install new versions of php packages

[Jochen Haeberle]

thx for the smart ;-)

but when I redeclare the list, I end up keeping two lists of packages. The guy 
who I am, I will definitely fuck this up regularly… and that’s back to the root 
of my problem… I would like to somehow reuse the $myPackages structure with 
different values for $php_version. 

Mhmm… as I write this this sounds like a use for a template…

Regards
Jochen

> Am 12.10.2020 um 13:46 schrieb A Manzer :
> 
> Seems pretty smart to me, tbh.
> 
> The only problem is that $myPackages is constant, so already includes the 
> "7.4" values from $php_version.  You'll need to declare a new list (because 
> you can't change variables) inside your .each block.
> 
> $php_remove.each | String $php_str_remove | { 
>  $myRemovePackages = [
>  "php${php_str_remove}-xml",
>  "php${php_str_remove}-zip",
>  "php${php_str_remove}-curl",
>  "php${php_str_remove}-mbstring",
>  "libapache2-mod-php${php_str_remove}",
> ] 
>  ensure_packages($myRemovePackages,
>  { 
>   'ensure' => 'absent', 
>  }  )
>  }
>  }
> 
> On Monday, October 12, 2020 at 5:10:34 AM UTC-4 jochen@gmail.com wrote:
> Hi all,
> 
> I posted a question on Stackoverflow before the weekend, but no responses and 
> not many views yet, unfortunately. So please forgive me asking this again 
> here. refactor ensure_packages to switch version of installed packages 
> https://stackoverflow.com/q/64284862/13088564?sem=2 
> 
> 
> 
> I am successfully installing several PHP modules by version with puppet on 
> Debian linux like this:
> 
> $php_version = '7.3' 
> ensure_packages([ 
> "php$php_version-xml", 
>  "php$php_version-zip", 
>  "php$php_version-curl", 
>  "php$php_version-mbstring", 
>  "libapache2-mod-php$php_version",
>  ], 
>  { 'ensure' => 'present', } )
> now I want to prepare for an update from PHP 7.3 to 7.4. This basically 
> works, but the 7.3 packages stay installed. I would like to adapt the code to 
> remove the old packages. I am looking for a way to reuse the list of packages 
> of modules for uninstalling.
> 
> I am thinking of a signature like this
> 
> class profile::software::apache (
>  $php_version = '7.4',
>  $php_remove = ['7.0‘, ‘7.3']
> , #... 
> ) {
> 
> $myPackages = [
>  "php$php_version-xml",
>  "php$php_version-zip",
>  "php$php_version-curl",
>  "php$php_version-mbstring",
>  "libapache2-mod-php$php_version",
>  ] 
>  
> ensure_packages($myPackages, {
>  'ensure' => 'present', 
>  } ) 
> 
>  $php_remove.each | String $php_version | { 
>  ensure_packages($myPackages,
>  { 
>   'ensure' => 'absent', 
>  }  )
>  }
>  }
> Is there a way to solve this?
> 
> thx
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/470cea3c-b64f-4666-827f-0bccfb101afcn%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/63C45E2D-B9FD-49A6-96EC-1CD608A60F21%40gmail.com.

Re: [Puppet Users] refactor use of ensure_packages to install new versions of php packages

[Jochen Haeberle]

I think you will get sort of „cannot redeclare“… otherwise I agree, it would 
work like you suggest.

But with the solution you propose, I guess I will have one structure for the 
packages to be installed and another for the ones to be removed.

But I want to manage only one list of packages… more save against errors 
managing the list… I have those packages all over the place...

I will have to think along the lines of single and double quoting… thx

> Am 12.10.2020 um 13:56 schrieb A Manzer :
> 
> If you redeclare the list outside the .each block, you'll end up with the 
> same list.  Also if you redeclare it outside, against the $php_remove array, 
> you'll get something weird.
> 
> If you redeclare it inside the .each block, it'll be local to that block, get 
> destroyed on the second run, and you'll end up with a fresh copy for the next 
> value of your $php_remove array.
> 
> You need to make sure you don't reuse variable names so you don't get 
> confused, but it'll work.
> 
> 
> If you want to use the same package list in both places, you may be able to 
> play some games with single- and double-quoting, but I don't think I'd 
> recommend that.
> 
> On Monday, October 12, 2020 at 7:51:12 AM UTC-4 jochen@gmail.com wrote:
> thx for the smart ;-)
> 
> but when I redeclare the list, I end up keeping two lists of packages. The 
> guy who I am, I will definitely fuck this up regularly… and that’s back to 
> the root of my problem… I would like to somehow reuse the $myPackages 
> structure with different values for $php_version. 
> 
> Mhmm… as I write this this sounds like a use for a template…
> 
> Regards
> Jochen
> 
> 
>> Am 12.10.2020 um 13:46 schrieb A Manzer > >:
>> 
> 
>> Seems pretty smart to me, tbh.
>> 
>> The only problem is that $myPackages is constant, so already includes the 
>> "7.4" values from $php_version.  You'll need to declare a new list (because 
>> you can't change variables) inside your .each block.
>> 
>> $php_remove.each | String $php_str_remove | { 
>>  $myRemovePackages = [
>>  "php${php_str_remove}-xml",
>>  "php${php_str_remove}-zip",
>>  "php${php_str_remove}-curl",
>>  "php${php_str_remove}-mbstring",
>>  "libapache2-mod-php${php_str_remove}",
>> ] 
>>  ensure_packages($myRemovePackages,
>>  { 
>>   'ensure' => 'absent', 
>>  }  )
>>  }
>>  }
>> 
>> On Monday, October 12, 2020 at 5:10:34 AM UTC-4 jochen@gmail.com 
>>  wrote:
>> Hi all,
>> 
>> I posted a question on Stackoverflow before the weekend, but no responses 
>> and not many views yet, unfortunately. So please forgive me asking this 
>> again here. refactor ensure_packages to switch version of installed packages 
>> https://stackoverflow.com/q/64284862/13088564?sem=2 
>> 
>> 
>> 
>> I am successfully installing several PHP modules by version with puppet on 
>> Debian linux like this:
>> 
>> $php_version = '7.3' 
>> ensure_packages([ 
>> "php$php_version-xml", 
>>  "php$php_version-zip", 
>>  "php$php_version-curl", 
>>  "php$php_version-mbstring", 
>>  "libapache2-mod-php$php_version",
>>  ], 
>>  { 'ensure' => 'present', } )
>> now I want to prepare for an update from PHP 7.3 to 7.4. This basically 
>> works, but the 7.3 packages stay installed. I would like to adapt the code 
>> to remove the old packages. I am looking for a way to reuse the list of 
>> packages of modules for uninstalling.
>> 
>> I am thinking of a signature like this
>> 
>> class profile::software::apache (
>>  $php_version = '7.4',
>>  $php_remove = ['7.0‘, ‘7.3']
>> , #... 
>> ) {
>> 
>> $myPackages = [
>>  "php$php_version-xml",
>>  "php$php_version-zip",
>>  "php$php_version-curl",
>>  "php$php_version-mbstring",
>>  "libapache2-mod-php$php_version",
>>  ] 
>>  
>> ensure_packages($myPackages, {
>>  'ensure' => 'present', 
>>  } ) 
>> 
>>  $php_remove.each | String $php_version | { 
>>  ensure_packages($myPackages,
>>  { 
>>   'ensure' => 'absent', 
>>  }  )
>>  }
>>  }
>> Is there a way to solve this?
>> 
>> thx
>> 
>> 
> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet-users...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/470cea3c-b64f-4666-827f-0bccfb101afcn%40googlegroups.com
>>  
>> .
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> 

Re: [Puppet Users] refactor use of ensure_packages to install new versions of php packages

[Jochen Haeberle]

Hi Garrett,

thx for the thoughts. I am basically doing as you suggest. Whenever possible I 
hold to latest versions of package maintainers

But Debian often comes with old versions of PHP which poses a problem. So I 
tend to use sury repositories to install newer but well tested packages of PHP. 
This repository offers several versions of PHP, at the moment mostly 7.3 and 
7.4. Common software packages now tend to switch to PHP 7.4 so sometime you 
sort of should follow that move to keep up to date.
Debian 9 came with PHP 7.0 I think (7.1 the most), which should not be used any 
more, but Debian 9 is still actively updated.

So whether I am on dev, preproduction, staging or live. If I do go this way for 
PHP, I will have to decide which version of PHP to use. And when I decide to 
switch the version, I can easily have Puppet do that, but the old versions keep 
installed and will be updated as well, which is undesirable.

Regards
Jochen

> Am 12.10.2020 um 19:07 schrieb Garrett Honeycutt :
> 
> On 10/12/20 5:10 AM, jochen@gmail.com  wrote:
>> Hi all,
>> 
>> I posted a question on Stackoverflow before the weekend, but no
>> responses and not many views yet, unfortunately. So please forgive me
>> asking this again here. refactor ensure_packages to switch version of
>> installed packages https://stackoverflow.com/q/64284862/13088564?sem=2
>> 
>> 
>> I am successfully installing several PHP modules by version with puppet
>> on Debian linux like this:
>> 
>> $php_version = '7.3' 
>> ensure_packages([ 
>> "php$php_version-xml", 
>>  "php$php_version-zip", 
>>  "php$php_version-curl", 
>>  "php$php_version-mbstring", 
>>  "libapache2-mod-php$php_version",
>>  ], 
>>  { 'ensure' => 'present', } )
>> 
>> now I want to prepare for an update from PHP 7.3 to 7.4. This basically
>> works, but the 7.3 packages stay installed. I would like to adapt the
>> code to remove the old packages. I am looking for a way to reuse the
>> list of packages of modules for uninstalling.
>> 
>> I am thinking of a signature like this
>> 
>> class profile::software::apache (
>>  $php_version = '7.4',
>>  $php_remove = ['7.0‘, ‘7.3']
>> , #... 
>> ) {
>> 
>> $myPackages = [
>>  "php$php_version-xml",
>>  "php$php_version-zip",
>>  "php$php_version-curl",
>>  "php$php_version-mbstring",
>>  "libapache2-mod-php$php_version",
>>  ] 
>>  
>> ensure_packages($myPackages, {
>>  'ensure' => 'present', 
>>  } ) 
>> 
>>  $php_remove.each | String $php_version | { 
>>  ensure_packages($myPackages,
>>  { 
>>   'ensure' => 'absent', 
>>  }  )
>>  }
>>  }
>> 
>> Is there a way to solve this?
>> 
>> thx
>> 
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to puppet-users+unsubscr...@googlegroups.com
>> > >.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/64abfa9c-5b7a-4aac-8a78-8e5152e8d66cn%40googlegroups.com
>>  
>> 
>> >  
>> >.
> 
> Hi Jochen,
> 
> Can Puppet handle this, yes! Should it, absolutely not. As you have seen
> from the posts you are going to quickly have a huge list of things you
> do not want on your system which becomes hard to manage. Instead of
> that, suggest you manage what packages are available in your
> repositories. You can tell puppet to install php-whatever and not
> specify 7.3 vs 7.4 vs 7.4.2, etc. You could have systems in different
> environments use different paths in your repo definitions such that you
> can test new packages in a pre-production environment and then update
> the URL's in other environments. You will end up with a much more
> reliable change management process for patching than attempting to track
> all the versions in Puppet.
> 
> Best regards,
> -g
> 
> 
> -- 
> Garrett Honeycutt
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/eb2655bd-b4ee-d487-e646-1ad2ad537120%40garretthoneycutt.com
>  
> .

-- 
Y

Re: [Puppet Users] refactor use of ensure_packages to install new versions of php packages

[Jochen Haeberle]

Hi all,

I solved this with the use of puppet iteration functions:

class profile::software::apache (
  $php_version= '7.4',
  $php_remove = ['7.0‘, ‘7.3'],
  #...
) {
  # build a hash of PHP Versions with a value of either present or absent
  # and iterate over it with each
  $phpInstallHash = { $php_version => 'present' }
  #notify { "Value of phpRemove: ${php_remove}": }
  if $php_remove {
# We have the array, use the map function to build remove hash
$phpRemoveHash = $php_remove.map |$version| {
  { $version => 'absent' }
}
$phpFullHash = $phpInstallHash + $phpRemoveHash
  } else {
$phpFullHash = $phpInstallHash
  }
  #notify { "phpHash to iterate over to install/uninstall: ${phpFullHash}": }

  #iterate over the result installing/uninstalling
  $phpFullHash.each | $php_version, $ensure_value | {
ensure_packages([
  "php$php_version-xml",
  "php$php_version-zip",
  "php$php_version-curl",
  "php$php_version-mbstring",
  "libapache2-mod-php$php_version",
],
  {
'ensure' => $ensure_value,
require  => [Class['apt::update'],
  Apt::Source['source_php_sury'],
],
notify   => Class['apache::service'],
  }
)

  }
}

It works for me. I answered my StackOverflow question as well. Any thoughts?

As Garret pointed out, this for sure is not a recommended or usual way to do 
things. The need for this stems from my use of the Sury PHP repository, which 
offers several versions of PHP. I chose to use with 7.3 or 7.4 and get all 
important and security related from that tree, so it’s not like pinning a 
package to a fixed version.

regards,
Jochen
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6DC35A2E-459D-41B3-B363-40F48B5E5720%40gmail.com.

Re: [Puppet Users] Newbie wants to know your favourite distro for Puppet Server

[Jochen Haeberle]

I am going well with Debian, but that’s what I usually use.

I guess I had a hard time running Puppet against Windows only… although it is 
possible, I think the worlds are so apart that there are some rough edges… you 
probably are more easy when you know your Puppet from unix and then start to 
conquer Windows.

Next thing, I would start out with Puppet serverless and add Puppet Master 
later…

I would recommend some titles from the PACKT library, they helped me very much. 

Best,
Jochen

> Am 16.06.2021 um 16:30 schrieb Jarod Schoen :
> 
> Thank you. I'll try to be more thorough in my reading. Everyone else seems to 
> be ok during setup.
> 
> On Wednesday, 16 June 2021 at 09:29:12 UTC-4 dhei...@opentext.com 
>  wrote:
> Am Dienstag, den 15.06.2021, 09:40 -0700 schrieb Jarod Schoen:
> 
>> I've been practicing getting Puppet Server (Master) up and running on a 
>> whole variety of distros. CentOS, Ubuntu, Debian... and the more 
>> instructions I read, the more its impossible to understand how Puppet works 
>> and should be installed.
> 
> Well, it works the same regardless of how it's installed. Anyway, 
> installation (from packages) on Linux depends on which distribution family 
> (RedHat or Debian) you're using. RedHat family distributions (RedHat, CentOS) 
> use the RedHat Package Manager (rpm) and its wrappers yum and/or dnf for 
> package management, while Debian family distributions (Debian, Ubuntu) use 
> the Debian package manager (dpkg, with apt wrapped around it). The 
> documentation contains detailed instructions about how to install Puppet 
> packages on either family. It all boils down to
> 
> Download and install a matching release package which will setup the 
> Puppetlabs package repository for your distribution/version and desired 
> Puppet version
> Use the native package manager to install Puppet server and/or agent packages
> 
>> What is the #1 best distro for puppet server and
> 
> For me, that's definitively Debian 
> 
>> do you know any great instructions for installing the latest Puppet 
>> Server/Agents v7
> 
> Yes, the Puppet documentation: 
> https://puppet.com/docs/puppet/7/install_and_configure.html 
> 
> 
> HTH...
> 
> Dirk
> -- 
> Dirk Heinrichs
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> Phone: +49 2226 15966 18 
> Email: dhei...@opentext.com 
> 
> Website:  <>www.recommind.de 
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) please 
> notify the sender immediately and destroy this e-mail. Any unauthorized 
> copying, disclosure or distribution of the material in this e-mail is 
> strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/48555e8b-6953-45ca-ba72-41e90228dd48n%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0C153534-CD8B-4216-BFB3-8379ED746249%40gmail.com.

Re: [Puppet Users] Manage Amavisd Service

[Jochen Haeberle]

> Am 25.11.2023 um 22:16 schrieb 'Kenyon Ralph' via Puppet Users 
> :
> 
> 
> This is a problem with amavis, not puppet. You'll need to do systemctl status 
> amavis, journalctl --pager-end --unit amavis, and look at amavis's own logs 
> to see why the service is dying or not starting.

The service restarts manually fine with service amavis restart

The question is not why it died but how to get it running again using Puppet.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/E7603628-2896-4A06-A35C-2D72E81E3644%40gmail.com.

Re: [Puppet Users] Manage Amavisd Service

[Jochen Haeberle]

> Am 27.11.2023 um 17:54 schrieb 'Kenyon Ralph' via Puppet Users 
> :
> 
> The service restarts manually fine with service amavis restart
> 
> The question is not why it died but how to get it running again using Puppet.
> 
>  Puppet simply runs systemctl start amavis if you have ensure => running. If 
> it is dying, it most likely has nothing to do with Puppet.

sure, Puppet is not involved in the dying. But my problem is, why it is not 
restarting the service. When I had the problem, 

service amavis start did not work, but service amavis restart did. So I changed 
my declaration to

service { 'amavis':
hasrestart => true,
ensure => running
}

Perhaps this will work better. 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/46ED7143-7DA2-4334-A16D-D4EE48608F58%40gmail.com.

Re: [Puppet Users] Manage Amavisd Service

[Jochen Haeberle]

now I have a declaration that kicks in when the problem occurs:

service { 'amavis':
hasrestart => true,
provider => 'systemd',
restart => '/usr/sbin/service amavis restart',
status => '/usr/bin/systemctl is-active --quiet amavis && [ 
"$(/usr/bin/systemctl show -p SubState --value amavis)" = "running" ] && exit 0 
|| exit 1',
ensure => running
}


the status-line detects the problem fine and when I run this, puppet says it’s 
chaning the service status:

Notice: /Stage[main]/Main/Service[amavis]/ensure: ensure changed 'stopped' to 
'running'

But it is not running after that. Manually running  

/usr/sbin/service amavis restart

brings up the service fine.

Anyone has a tipp what I am doing wrong?

thx

> Am 28.11.2023 um 12:45 schrieb Jochen Haeberle :
> 
> 
> 
>> Am 27.11.2023 um 17:54 schrieb 'Kenyon Ralph' via Puppet Users 
>> :
>> 
>> The service restarts manually fine with service amavis restart
>> 
>> The question is not why it died but how to get it running again using Puppet.
>> 
>>  Puppet simply runs systemctl start amavis if you have ensure => running. If 
>> it is dying, it most likely has nothing to do with Puppet.
> 
> sure, Puppet is not involved in the dying. But my problem is, why it is not 
> restarting the service. When I had the problem, 
> 
> service amavis start did not work, but service amavis restart did. So I 
> changed my declaration to
> 
> service { 'amavis':
> hasrestart => true,
> ensure => running
> }
> 
> Perhaps this will work better. 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/BD107A9D-ED3E-46F9-9A29-CF9D62FB4D94%40gmail.com.

Re: [Puppet Users] Manage Amavisd Service

[Jochen Haeberle]

Hi Nick,

good point! As of the debug log, it seems to issue the start command, although 
the dog says that puppet would use the restart command if hasrestart is set to 
true

I will have to wait for the problem to reoccur to finally test this. Thanks a 
lot

> Am 01.12.2023 um 19:10 schrieb Nick Bertrand :
> 
> Hi Jochen,
> 
> When amavis is in the broken state, does `service amavis start` fix it or is 
> it just `service amavis restart` that fixes it? If 'restart' works, but 
> 'start' doesn't, I wonder if Puppet is running the start command instead of 
> restart. Running the puppet agent in debug mode should show you the actual 
> command being run. If you see `systemctl start amavis` is being run, you 
> might try setting the `start` parameter to what you have `restart` set to:
> 
> service { 'amavis':
> ...
> start => '/usr/sbin/service amavis restart',
> ...
> }
> 
> Thanks,
> 
> Nick
> 
> On Fri, Dec 1, 2023 at 11:39 AM Jochen Haeberle  <mailto:jochen.haebe...@gmail.com>> wrote:
>> now I have a declaration that kicks in when the problem occurs:
>> 
>> service { 'amavis':
>> hasrestart => true,
>> provider => 'systemd',
>> restart => '/usr/sbin/service amavis restart',
>> status => '/usr/bin/systemctl is-active --quiet amavis && [ 
>> "$(/usr/bin/systemctl show -p SubState --value amavis)" = "running" ] && 
>> exit 0 || exit 1',
>> ensure => running
>> }
>> 
>> 
>> the status-line detects the problem fine and when I run this, puppet says 
>> it’s chaning the service status:
>> 
>> Notice: /Stage[main]/Main/Service[amavis]/ensure: ensure changed 'stopped' 
>> to 'running'
>> 
>> But it is not running after that. Manually running  
>> 
>> /usr/sbin/service amavis restart
>> 
>> brings up the service fine.
>> 
>> Anyone has a tipp what I am doing wrong?
>> 
>> thx
>> 
>>> Am 28.11.2023 um 12:45 schrieb Jochen Haeberle >> <mailto:jochen.haebe...@gmail.com>>:
>>> 
>>> 
>>> 
>>>> Am 27.11.2023 um 17:54 schrieb 'Kenyon Ralph' via Puppet Users 
>>>> mailto:puppet-users@googlegroups.com>>:
>>>> 
>>>> The service restarts manually fine with service amavis restart
>>>> 
>>>> The question is not why it died but how to get it running again using 
>>>> Puppet.
>>>> 
>>>>  Puppet simply runs systemctl start amavis if you have ensure => running. 
>>>> If it is dying, it most likely has nothing to do with Puppet.
>>> 
>>> sure, Puppet is not involved in the dying. But my problem is, why it is not 
>>> restarting the service. When I had the problem, 
>>> 
>>> service amavis start did not work, but service amavis restart did. So I 
>>> changed my declaration to
>>> 
>>> service { 'amavis':
>>> hasrestart => true,
>>> ensure => running
>>> }
>>> 
>>> Perhaps this will work better. 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet-users+unsubscr...@googlegroups.com 
>> <mailto:puppet-users+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/BD107A9D-ED3E-46F9-9A29-CF9D62FB4D94%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/puppet-users/BD107A9D-ED3E-46F9-9A29-CF9D62FB4D94%40gmail.com?utm_medium=email&utm_source=footer>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> <mailto:puppet-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/CAP15v%2B-MB6rKu26AZWqJtq3Z9Dy1QkcGt8Z2Dy%3DkYG-Mf2A9Lw%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/puppet-users/CAP15v%2B-MB6rKu26AZWqJtq3Z9Dy1QkcGt8Z2Dy%3DkYG-Mf2A9Lw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/55BBEFEF-119A-4FCF-84AE-B68F774AD344%40gmail.com.