Re: [Puppet Users] Re: postrun command in windows

[Rakesh Kathpal]

Dear Josh,

Thanks a lot for the update.

I understand this seems to be a bug.. have seen the ticket open on this..

Wanted to know if there any workaround?

Thanks & Regards,

Rakesh K.


On Fri, Jul 4, 2014 at 12:46 AM, Josh Cooper  wrote:

>
>
>
> On Wed, Jul 2, 2014 at 11:26 AM, Rakesh Kathpal 
> wrote:
>
>> Yes.. it works perfectly from commandline..
>>  On 2 Jul 2014 19:33, "Brahim Dagher"  wrote:
>>
>>> Do you have success running 'puppet facts upload' from the command line?
>>>
>>> On Tuesday, July 1, 2014 7:38:40 AM UTC-4, Rakesh K wrote:

 Hi,

 My puppet.conf on windows looks like the following

 [main]
 server="mypuppetmaster.com"
 pluginsync=true
 autoflush=true
 environment=production
 certname ="mypuppetagent.com"
 report=true
 postrun_command='puppet facts upload'

 When I am trying the puppet run, I am getting the error below

 *Error: Could not run command from postrun_command: CreateProcess()
 failed: The system cannot find the file specified.*

 I even tried using the complete path but still same issue...

 I am using puppet 3.4.2., please let me know if there is any resolution
 for this issue..

 Thanks,

 Rakesh K.

>>>  --
>>> 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/b8935d03-9dd1-48e4-9efe-c26877624003%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/CAEJrXMW_hshroTEyathLMM%3DiL7kPgn0zZzn5hMfU4zMJ3XDa8g%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> This is https://tickets.puppetlabs.com/browse/PUP-1431. If you use
> process monitor, you will likely see puppet is calling CreateProcess with a
> program named "puppet facts upload" instead of the "puppet" program with
> arguments "facts upload".
>
> Josh
>
> --
> Josh Cooper
> Developer, Puppet Labs
>
> *Join us at PuppetConf 2014 , September
> 20-24 in San Francisco*
> *Register by July 31st to take advantage of the Early Bird discount
>  **—**save
> $249!*
>
> --
> 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/CA%2Bu97u%3D9GDccKZUhbvN8qCOr_m%2BY1rTV84wzXBvWrHgpnE%3D%2Bhg%40mail.gmail.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/CAEJrXMWWjA5_W7HaMa_3OWXPYjz1B5y2zDS9f9%3DShQQgnTaEAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] report all nodes that do NOT have a certain class assigned to them

[Pete Brown]

Hi Jay,

Have you had a look at puppetdbquery?

https://forge.puppetlabs.com/dalen/puppetdbquery


On 25 June 2014 04:01, Jay Benner  wrote:
> Seems like this should be easy, but I am having a tough time sorting it out.
> I am using PE 3.1 and I want to know which of my nodes are missing a certain
> class.  Its pretty easy to get a list of the nodes that have the class in
> the console, but that still leaves a lot of math for me to do as I have
> thousands of nodes.  The search inventory tool has something close with
> being able to search via fact presence or absence, but there doesn't seem to
> be a fact that corresponds to my class.  Even if I distributed a fact with
> my class, that would only report for nodes that actually got the class,
> whereas I want hits on the fact's absence.  Anyone solved this riddle
> already?
>
> --
> 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/e5187012-2753-42a1-9a56-6f0d4bacb252%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/CAJ8DPF5Fej%2BOgyr7HXSRKy0sesJcoMP3pNyk89atdEy%2BobOZQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re:

[Zheng Bin]

Hi, Frank

May I ask you if your problem has been solved, as I'm now coming across the 
same issue with you.

Thanks,
Bin

On Sunday, March 17, 2013 2:03:08 AM UTC+8, ureal frank wrote:
>
> Hi,
>
> I'm trying to setup a Puppet 3.1.1 (master) under NetBSD 6.0.1
>
> I've installed Ruby 1.9.3 through pkgin and Puppet with $ gem install 
> puppet.
>
> (pkgsrc has a puppet port under sysutils/puppet but is very very 
> outdated... version 0.25) 
>
> After generate and configure puppet.conf with $ puppet master --genconfig 
> > puppet.conf
> (I've symlinked /etc/puppet to /etc/pkg/etc/puppet for NetBSD compliance) 
>
> then I got this
>
> $ puppet master --no-daemonize -v -d -o --trace
>
> Debug: Failed to load library 'selinux' for feature 'selinux'
> Debug: Using settings: adding file resource 'confdir': 
> 'File[/usr/pkg/etc/puppet]{:path=>"/usr/pkg/etc/puppet", 
> :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
> Debug: Using settings: adding file resource 'vardir': 
> 'File[/var/lib/puppet]{:path=>"/var/lib/puppet", :ensure=>:directory, 
> :loglevel=>:debug, :links=>:follow, :backup=>false}'
> Debug: Failed to load library 'shadow' for feature 'libshadow'
> Debug: Puppet::Type::User::ProviderDirectoryservice: file 
> /usr/bin/dsimport does not exist
> Debug: Puppet::Type::User::ProviderUseradd: file chage does not exist
> Debug: Failed to load library 'ldap' for feature 'ldap'
> Debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
> Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not 
> exist
> Debug: Puppet::Type::User::ProviderPw: file pw does not exist
> Debug: Puppet::Type::User::ProviderDirectoryservice: file 
> /usr/bin/dsimport does not exist
> Debug: Puppet::Type::User::ProviderUseradd: file chage does not exist
> Debug: Failed to load library 'ldap' for feature 'ldap'
> Debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
> Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not 
> exist
> Debug: Puppet::Type::User::ProviderPw: file pw does not exist
>
> Error: Could not create resources for managing Puppet's files and 
> directories in sections [:main, :master, :ssl, :metrics]: undefined method 
> `exists?' for nil:NilClass
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/type/user.rb:367:in 
> `exists?'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings.rb:713:in 
> `service_user_available?'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings/file_setting.rb:54:in
>  
> `safe_to_use_settings_value?'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings/file_setting.rb:45:in
>  
> `value'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings/file_setting.rb:108:in
>  
> `owner'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings/file_setting.rb:156:in
>  
> `to_resource'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings.rb:847:in 
> `block in to_catalog'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings.rb:844:in 
> `each'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings.rb:844:in 
> `to_catalog'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings.rb:906:in 
> `block in use'
> /usr/pkg/lib/ruby/1.9.3/sync.rb:227:in `sync_synchronize'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings.rb:900:in 
> `use'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/application/master.rb:269:in
>  
> `setup'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/application.rb:362:in
>  
> `block (2 levels) in run'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/application.rb:456:in
>  
> `plugin_hook'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/application.rb:362:in
>  
> `block in run'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/util.rb:504:in 
> `exit_on_fail'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/application.rb:362:in
>  
> `run'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/util/command_line.rb:132:in
>  
> `run'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/util/command_line.rb:86:in
>  
> `execute'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/bin/puppet:4:in ` (required)>'
> /usr/pkg/bin/puppet:23:in `load'
> /usr/pkg/bin/puppet:23:in `'
> Error: Could not prepare for execution: Could not create resources for 
> managing Puppet's files and directories in sections [:main, :master, :ssl, 
> :metrics]: undefined method `exists?' for nil:NilClass
> undefined method `exists?' for nil:NilClass
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/type/user.rb:367:in 
> `exists?'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings.rb:713:in 
> `service_user_available?'
> /usr/pkg/lib/ruby/gems/1.9.3/gems/puppet-3.1.1/lib/puppet/settings/file_setting.rb:54:in
>  
> `safe_to_use_settings_value?'
> /usr/pkg/lib/ru

Re: [Puppet Users] "Each" loop issue

[Henrik Lindberg]

On 2014-03-07 23:00, martin.li...@gmail.com wrote:

Hi Ellison,

That's right. That seems to be the case.
I've been googling around, and seems that the new parser has a different
scope from where it can grab the variables. Sadly, I can't find the way
to make it work.
Should I include something special in order to make the hiera variable
available to the template?



There was a change to dynamic scoping - they were allowed when they 
should not. That problem was fixed in the future parser branch of the 
logic. This issue is PUP-1220.


Not seeing your entire configuration it is hard to tell where the 
missing variable is defined and if it should be visible or not.
If you can reference the variable at the point where you are making the 
call to produce the template text, then something odd is going on.


say doing something like:

notice "The variable is set to: $the_var"
template(...)

- henrik

--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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/lp51u5%24elo%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Windows warning about source permissions

[Michael Legleux]

The directory already exists.
Puppet master and agent are both 3.6.2
This is in the debug from the run on the agent.

Debug: Using settings: adding file resource 'pluginfactdest': 
'File[C:/ProgramData/PuppetLabs/puppet/var/facts.d]{:path=>"C:/ProgramData/PuppetLabs/puppet/var/facts.d",
 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'


On Tuesday, July 1, 2014 7:53:34 PM UTC-7, Michael Legleux wrote:
>
> This warning is haunting me:
>
> Copying owner/mode/group from the source file on Windows is deprecated; 
> use source_permissions => ignore.
>
> It is referenced here:
> http://docs.puppetlabs.com/windows/writing.html#managing-file-permissions
>
> I am not copying ANY files or anything yet, the site.pp is otherwise 
> blank. What files are PUPPET copying?
> This folder is empty:
> so I put this in site.pp
> if $osfamily == 'windows' {
> File { source_permissions => ignore } }
> to no avail.
>
> Must I just live with this warning? What gives? 
> Immediately after the warning it says
> Debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts.d]: Copying owner 
> from the source file on Windows is deprecated; user source_permissions => 
> ignore.
> Debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts.d]: Copying mode 
> from the source file on Windows is deprecated; user source_permissions => 
> ignore.
> Debug: /File[C:/ProgramData/PuppetLabs/puppet/var/facts.d]: Copying group 
> from the source file on Windows is deprecated; user source_permissions => 
> ignore.
>
> C:/ProgramData/PuppetLabs/puppet/var/facts.d is empty!
>

-- 
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/e4a17a27-bb72-4be1-b085-72e100d12f72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] "Each" loop issue

[martin . listz]

Hi Ellison,

That's right. That seems to be the case.
I've been googling around, and seems that the new parser has a different 
scope from where it can grab the variables. Sadly, I can't find the way to 
make it work. 
Should I include something special in order to make the hiera variable 
available to the template?

Again, thanks for taking the time.

Best regards,


El jueves, 3 de julio de 2014 13:57:46 UTC-3, Ellison Marks escribió:
>
> That error means that the @server_roles variable is holding nil, as nil 
> does not have an each method to call. Perhaps the new parser is evaluating 
> things differently and not setting that variable.
>
> On Tuesday, July 1, 2014 5:25:15 PM UTC-7, martin...@gmail.com wrote:
>>
>> Henrik, Tristan, thanks for your replies!
>>
>> I've added "parser = future" on both master and agent, inside [main], and 
>> also I'm still using "--parser future", just in case.
>> You both were right, and I'd use "notify" instead of "notice" in that 
>> snippet.
>>
>> I think that parser option is working now, but it's breaking a template 
>> that was working until now. So here I go again for your help, as I don't 
>> think that the parser should be doing this.
>>
>> Here is the output of the new error:
>>
>> *Error: Could not retrieve catalog from remote server: Error 400 on 
>> SERVER: Failed to parse template sudo/sudoers.erb:*
>> *  Filepath: 
>> /etc/puppet/environments/integration/modules/sudo/templates/sudoers.erb*
>> *  Line: 42*
>> *  Detail: undefined method `each' for nil:NilClass*
>> * on node test01*
>>
>> Here is the line 42 of the template file:
>>
>> ...
>> DEPLOY ALL = NOPASSWD: /usr/bin/service apache2 restart
>> DEPLOY ALL = NOPASSWD: /usr/bin/service php5-fpm restart
>> *<% @server_roles.each do |role| -%>  <== line 42*
>> <% if role == "testuser" %>
>> DEPLOY ALL = NOPASSWD: /usr/bin/service tomcat7 restart
>> DEPLOY ALL = NOPASSWD: /usr/bin/service tomcat7 start
>> DEPLOY ALL = NOPASSWD: /usr/bin/service tomcat7 stop
>> <% end %>
>> ...
>>
>> I've tried with "each @server_roles" too, but still broken.
>> May be enabling the extra features of the parser, puppet tries to do 
>> something else with the word "each", but I'm totally lost here.
>>
>> Is this behavior expected? Is there any way that I can debug any deeper 
>> on this?
>>
>> Again, thanks in advance for any help.
>>
>> Cheers,
>>
>> Martin
>>
>>
>>
>>
>> El martes, 1 de julio de 2014 12:27:16 UTC-3, Henrik Lindberg escribió:
>>>
>>> On 2014-30-06 23:58, martin...@gmail.com wrote: 
>>> > Hi Puppet users! 
>>> > 
>>> > I'm having an issue with "each loop" on puppet, and I just can't 
>>> figure 
>>> > out what am I doing wrong, so any help will be much appreciated. 
>>> > 
>>> > Here is my test.pp example: 
>>> > 
>>> > class mytestclass { 
>>> >$stuff = ["1", "2", "3"] 
>>> > 
>>> >each($stuff) |$x| { 
>>> >  notice { $x: } 
>>>
>>> You probably meant 
>>>
>>> notify { $x: } 
>>>
>>> notice is a logging function, and you can do 
>>>
>>> notice $x 
>>>
>>> >} 
>>> > } 
>>>
>>> For this snippet to work, you must also do 
>>>
>>> include mytestclass 
>>>
>>> outside the scope of that class, otherwise nothing happens. 
>>>
>>> > 
>>> > And here is the output when trying to apply it: /"Error: Could not 
>>> parse 
>>> > for environment production: Could not match |$x| at /tmp/test.pp:10"/ 
>>> > 
>>> Sounds like --parser future is not in effect. 
>>>
>>> > I've "parser = future" inside my puppet.conf, ruby-rgen is installed 
>>> in 
>>> > both client and server. I'm also running it with "--parser future" on 
>>> > the client, but no joy. 
>>> > I've  been playing with variants like "$stuff.each", using hashes, and 
>>> a 
>>> > few more desperate ideas. 
>>> > 
>>> > OS: Ubuntu 12.04 
>>> > Puppet: 3.5.1-1puppetlabs1 
>>> > ruby-rgen: 0.6.5-1puppetlabs1 
>>> > 
>>> > 
>>> > I'm clearly missing something, but can't find what. 
>>> > 
>>>
>>> As another poster suggested, maybe you have the parser=future setting in 
>>> the wrong section. 
>>>
>>> Hope the above helps 
>>>
>>> - henrik 
>>>
>>> -- 
>>>
>>> Visit my Blog "Puppet on the Edge" 
>>> http://puppet-on-the-edge.blogspot.se/ 
>>>
>>>

-- 
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/384b92e8-9287-4685-a76f-e539ae7acf87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet on Openelec

[Thomas Bendler]

That would be a hard task because a lot of prerequisites are not in the
default build. So getting this up and running mean to recompile the base
image which break the automatic upgrade feature. Better would be preparing
the configuration per media box locally and use something like pssh to
distribute the configurations.

Regards Thomas


2014-07-03 3:08 GMT+02:00 Ellick Johnson :

> Anyone ever tried to get puppet on the Openelec OS? I want to keep all my
> XBMC configs updated.
>
> Open Embedded Linux Entertainment Center (OpenELEC) is a small Linux
> distribution built from scratch as a platform to turn your computer into an
> XBMC  media center.
>
> -Ellick
>
> --
> 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/48061eeb-1c64-4beb-98e6-a553e7eff36a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Linux ... enjoy the ride!

-- 
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/CAELoU1MLhr7xrVXjm0He_986JME5XA7qZQG6xbi8_Mk3bjU8ug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: postrun command in windows

[Josh Cooper]

On Wed, Jul 2, 2014 at 11:26 AM, Rakesh Kathpal  wrote:

> Yes.. it works perfectly from commandline..
> On 2 Jul 2014 19:33, "Brahim Dagher"  wrote:
>
>> Do you have success running 'puppet facts upload' from the command line?
>>
>> On Tuesday, July 1, 2014 7:38:40 AM UTC-4, Rakesh K wrote:
>>>
>>> Hi,
>>>
>>> My puppet.conf on windows looks like the following
>>>
>>> [main]
>>> server="mypuppetmaster.com"
>>> pluginsync=true
>>> autoflush=true
>>> environment=production
>>> certname ="mypuppetagent.com"
>>> report=true
>>> postrun_command='puppet facts upload'
>>>
>>> When I am trying the puppet run, I am getting the error below
>>>
>>> *Error: Could not run command from postrun_command: CreateProcess()
>>> failed: The system cannot find the file specified.*
>>>
>>> I even tried using the complete path but still same issue...
>>>
>>> I am using puppet 3.4.2., please let me know if there is any resolution
>>> for this issue..
>>>
>>> Thanks,
>>>
>>> Rakesh K.
>>>
>>  --
>> 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/b8935d03-9dd1-48e4-9efe-c26877624003%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/CAEJrXMW_hshroTEyathLMM%3DiL7kPgn0zZzn5hMfU4zMJ3XDa8g%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

This is https://tickets.puppetlabs.com/browse/PUP-1431. If you use process
monitor, you will likely see puppet is calling CreateProcess with a program
named "puppet facts upload" instead of the "puppet" program with arguments
"facts upload".

Josh

-- 
Josh Cooper
Developer, Puppet Labs

*Join us at PuppetConf 2014 , September
20-24 in San Francisco*
*Register by July 31st to take advantage of the Early Bird discount
 **—**save $249!*

-- 
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/CA%2Bu97u%3D9GDccKZUhbvN8qCOr_m%2BY1rTV84wzXBvWrHgpnE%3D%2Bhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Query puppetdb from puppet manifest

[Nan Liu]

On Thu, Jul 3, 2014 at 12:00 PM, Schofield  wrote:

> What are most people using to query the puppetdb for data from within
> puppet manifest files these days?  Is there any thing official from
> PuppetLabs to do this?
>

Best tool at the moment: https://github.com/dalen/puppet-puppetdbquery

Nan

-- 
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/CACqVBqCE%2BMnDXZnnn5%3DHiXMUaHgUE9d6PcWariU%2BAdB3mVM_JQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Query puppetdb from puppet manifest

[Schofield]

What are most people using to query the puppetdb for data from within 
puppet manifest files these days?  Is there any thing official from 
PuppetLabs to do this?

-- 
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/8dc87e5c-5e4f-4794-b262-dbda45506c79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] "Each" loop issue

[Ellison Marks]

That error means that the @server_roles variable is holding nil, as nil 
does not have an each method to call. Perhaps the new parser is evaluating 
things differently and not setting that variable.

On Tuesday, July 1, 2014 5:25:15 PM UTC-7, martin...@gmail.com wrote:
>
> Henrik, Tristan, thanks for your replies!
>
> I've added "parser = future" on both master and agent, inside [main], and 
> also I'm still using "--parser future", just in case.
> You both were right, and I'd use "notify" instead of "notice" in that 
> snippet.
>
> I think that parser option is working now, but it's breaking a template 
> that was working until now. So here I go again for your help, as I don't 
> think that the parser should be doing this.
>
> Here is the output of the new error:
>
> *Error: Could not retrieve catalog from remote server: Error 400 on 
> SERVER: Failed to parse template sudo/sudoers.erb:*
> *  Filepath: 
> /etc/puppet/environments/integration/modules/sudo/templates/sudoers.erb*
> *  Line: 42*
> *  Detail: undefined method `each' for nil:NilClass*
> * on node test01*
>
> Here is the line 42 of the template file:
>
> ...
> DEPLOY ALL = NOPASSWD: /usr/bin/service apache2 restart
> DEPLOY ALL = NOPASSWD: /usr/bin/service php5-fpm restart
> *<% @server_roles.each do |role| -%>  <== line 42*
> <% if role == "testuser" %>
> DEPLOY ALL = NOPASSWD: /usr/bin/service tomcat7 restart
> DEPLOY ALL = NOPASSWD: /usr/bin/service tomcat7 start
> DEPLOY ALL = NOPASSWD: /usr/bin/service tomcat7 stop
> <% end %>
> ...
>
> I've tried with "each @server_roles" too, but still broken.
> May be enabling the extra features of the parser, puppet tries to do 
> something else with the word "each", but I'm totally lost here.
>
> Is this behavior expected? Is there any way that I can debug any deeper on 
> this?
>
> Again, thanks in advance for any help.
>
> Cheers,
>
> Martin
>
>
>
>
> El martes, 1 de julio de 2014 12:27:16 UTC-3, Henrik Lindberg escribió:
>>
>> On 2014-30-06 23:58, martin...@gmail.com wrote: 
>> > Hi Puppet users! 
>> > 
>> > I'm having an issue with "each loop" on puppet, and I just can't figure 
>> > out what am I doing wrong, so any help will be much appreciated. 
>> > 
>> > Here is my test.pp example: 
>> > 
>> > class mytestclass { 
>> >$stuff = ["1", "2", "3"] 
>> > 
>> >each($stuff) |$x| { 
>> >  notice { $x: } 
>>
>> You probably meant 
>>
>> notify { $x: } 
>>
>> notice is a logging function, and you can do 
>>
>> notice $x 
>>
>> >} 
>> > } 
>>
>> For this snippet to work, you must also do 
>>
>> include mytestclass 
>>
>> outside the scope of that class, otherwise nothing happens. 
>>
>> > 
>> > And here is the output when trying to apply it: /"Error: Could not 
>> parse 
>> > for environment production: Could not match |$x| at /tmp/test.pp:10"/ 
>> > 
>> Sounds like --parser future is not in effect. 
>>
>> > I've "parser = future" inside my puppet.conf, ruby-rgen is installed in 
>> > both client and server. I'm also running it with "--parser future" on 
>> > the client, but no joy. 
>> > I've  been playing with variants like "$stuff.each", using hashes, and 
>> a 
>> > few more desperate ideas. 
>> > 
>> > OS: Ubuntu 12.04 
>> > Puppet: 3.5.1-1puppetlabs1 
>> > ruby-rgen: 0.6.5-1puppetlabs1 
>> > 
>> > 
>> > I'm clearly missing something, but can't find what. 
>> > 
>>
>> As another poster suggested, maybe you have the parser=future setting in 
>> the wrong section. 
>>
>> Hope the above helps 
>>
>> - henrik 
>>
>> -- 
>>
>> Visit my Blog "Puppet on the Edge" 
>> http://puppet-on-the-edge.blogspot.se/ 
>>
>>

-- 
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/6e72c1a9-e6d9-4f88-92e9-9fb4d1624e53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Service start and stop

[jcbollinger]

On Wednesday, July 2, 2014 8:33:08 AM UTC-5, Satish Katuru wrote:
>
>
> Hi,
>
> Please see my init.pp file.
>
> First I am stopping the Jboss server and then deleting few folders,copying 
> files and then trying to start the service.
>
> When I place file copy statements it is not working. With out file copy 
> statements I am able to stop the service and start the service.
>
> I am not sure why it is happening like that.
>
> Can any one give us suggestions?
>
>
> I am using below command for the execution:
>
> *sudo puppet agent -t --waitforcert=60 (with debug)*
>
>

Ok.  Do note that you shouldn't need --waitforcert any more after the first 
successful run, but including it is harmless.

 

>
> Service stop and folder deletion was successfull.But When I Included the 
> file copy statements like below Service is not getting started.
>


What does the Puppet --debug output say?  Does it show 
Service[startjavaservice.sh] being applied successfully?

What do the JBoss logs say?  Is startup failing because JBoss doesn't like 
the contents of the file, for example?

 

> ( 
>
> file 
>
> {
>
>
> "/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/deploy/RulesService-1.0.esb":
>
> ensure => "present",
>
> mode => "0644",
>
> owner => "katusa02",
>
> group => "katusa02",
>
> source => "puppet://$puppetserver/modules/httpd/RulesService-1.0.esb",
>
>  
>
> }
> )
>
>
> *Init.pp*
>
> class httpd
> {
>
>
> service{
> "stopjavaservice.sh":
> ensure =>"stopped",
> }
>
>
>
> file 
>
> {
>
> "/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/tmp":
> ensure => "absent",
> force => "true",
> recurse => "true",
> owner => "katusa02",
>
> }
>
>
> file 
>
> {
>
> "/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/work":
> ensure => "absent",
> force => "true",
> recurse => "true",
> owner => "katusa02",
>
> }
>
>
>
> file 
>
> {
>
> "/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/log":
> ensure => "absent",
> force => "true",
> recurse => "true",
> owner => "katusa02",
>
> }
>
> file 
>
> {
>
> "/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/data":
> ensure => "absent",
> force => "true",
> recurse => "true",
> owner => "katusa02",
>
> }
>
>
> file 
>
> {
>
> "/home/katusa02/JBossRuntime/log":
> ensure => "absent",
> force => "true",
> recurse => "true",
> owner => "katusa02",
>
> }
>
> file 
>
> {
>
> "/home/katusa02/JBossRuntime/data":
> ensure => "absent",
> force => "true",
> recurse => "true",
> owner => "katusa02",
>
> }
>
>
> file 
>
> {
>
> "/home/katusa02/JBossRuntime/server.log":
> ensure => "absent",
> force => "true",
> recurse => "true",
> owner => "katusa02",
>
> }
>
>
> service{
> "startjavaservice.sh":
> ensure =>"running",
> }
>
>
> }
>
>
>
> Am i Missing any thing here? Do I need to wait for some amount of time for 
> each run?
>


Does the command "service startjavaservice.sh start" (or its equivalent for 
your platform) return before all JBoss-hosted components are fully up and 
running?  I think I remember that in days of yore, JBoss's own startup 
script returned after JBoss itself was booted, but without waiting for 
deployment or startup of anything inside.

Additionally, you have a serious issue with order of application.  
Resources are not guaranteed to be applied by the agent in the order that 
they are added to the catalog by the master.  This is what the chaining 
arrows and the 'require' and 'before' metaparameters are for.  Use them.

Furthermore, if you have different "services" to start and stop the same 
JBoss instance, then you are misusing the service management facilities of 
Puppet and your OS.  Use Execs instead if you really just want to run 
different for-purpose scripts.  Or use an Exec to stop JBoss, and a bona 
fide Service to later ensure that it is running.


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/ecaa7e5a-11bb-474e-b8f7-4d92a5b259f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: rpm exits 0 on scriptlet failure

[jcbollinger]

On Wednesday, July 2, 2014 9:51:10 AM UTC-5, Raul Macian wrote:
>
> I have a problem that starts to make me think that puppet is not usable to 
> install packages. I will explain:
>
>

That's a whopper of a claim.  Don't let any of the thousands of people who 
do use Puppet to install packages hear it.  :^)

 

> There is a common situation when you put some code on the %post when 
> creating rpm.
>


Not, it's really not.  I mean %post scriptlets themselves are pretty 
common, but scriptlets exiting nonzero is almost always bad form.  For 
instance, RedHat says, "Except in some really exceptional cases (if any), 
we want all scriptlets to exit with the zero exit status" (Fedora packaging 
guidelines, 
http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Syntax).  The 
Fedora guidelines go into more detail about why, but I'll summarize it as 
"scriptlets exiting nonzero messes you up".

 

> In my case I am executing some db migrations after the installation has 
> been performed. The problems rises when something goes wrong in the 
> scriptlet because the yum command will ignore the failure end exits with a 
> succesful code. To add more complexity the yum provider performs a yum -q 
> command, that means no output on your logs. So you don't know if the 
> installation has ended ok or not.
>
>

It's a Bad Thing if the installation does not end ok on account of a 
scriptlet failing.  Better would be for the scriptlet to record status 
information somewhere on the filesystem if the fact that it did not 
complete the intended work will not otherwise be evident.  If your 
scriptlet did so, then you could test the output via an Exec to feed that 
information back into Puppet.

 

> Here explains some things exposed
>
> https://bugzilla.redhat.com/show_bug.cgi?id=569930
>


The bottom line is that the issue described there is with RPM, therefore so 
is your complaint.  If RPM does not behave as you require, then don't use 
RPM packages.  This is not a Puppet issue.

For what its worth, I tend to agree that RPM ought not to exit with a 
success code if a scriptlet has failed.  On the other hand, RedHat's 
position, to which I subscribe, is that you oughtn't to be packaging 
scriptlets that ever *can* fail.


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/3055029f-69fa-49fc-9f0f-97364a83b0a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Get puppet agents

[Christopher Wood]

Check the list of signed certs and read your puppetmaster logs (or check 
reports in /var/lib/puppet/reports, or check reports in puppetdb) to see when 
they last checked in.

puppet cert list -a

http://docs.puppetlabs.com/guides/reporting.html

On Thu, Jul 03, 2014 at 06:29:19AM -0700, Yugank Pandey wrote:
>Is there any way that all the puppet agents that are connected to a puppet
>master (or any server that they are getting their configuration from) be
>determined from the puppet master ?
> 
>--
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/f1a40ac1-e24d-4bde-86ed-db9b140a202f%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/f1a40ac1-e24d-4bde-86ed-db9b140a202f%40googlegroups.com?utm_medium=email&utm_source=footer
>3. 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/20140703140921.GA15647%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Get puppet agents

[Yugank Pandey]

Is there any way that all the puppet agents that are connected to a puppet 
master (or any server that they are getting their configuration from) be 
determined from the puppet master ?

-- 
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/f1a40ac1-e24d-4bde-86ed-db9b140a202f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Regarding Service elements in init.pp

[Christopher Wood]

In your place I would merge those two into a single init script with the usual 
lsb-ish start+stop+restart+status that puppet's service type/provider expects. 
They both control the same service and thus should be defined in a single 
resource.

On Thu, Jul 03, 2014 at 05:53:01AM -0700, Satish Katuru wrote:
>Hi ,
> 
>My init.pp has two service elements like below:
> 
>class httpd
>{
> 
>service{
>"startjavaservice.sh":
>ensure => "running",
>}
> 
>service{
>"stopjavaservice.sh":
>ensure =>"stopped",
> 
>}
>}
> 
>First one is for starting Java service and the second one is for stopping
>the same service.
> 
>Problem:
> 
>When it has  only one service then it is working fine but when it has two
>services it is not working.
> 
>(If  It has only startjavaservice then java service is getting started
>successfully and if it has only stopjavaservice java service is getting
>stopped.
>If it has both the services first service should start and then it should
>be stopped but here only first thing happened. Java service has started
>but not stopped)
> 
>Can any one help me out on this?
> 
>Regards,
>Sathish.
> 
>--
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/14b889bb-bbdf-4818-baa7-995a8d6afdd8%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/14b889bb-bbdf-4818-baa7-995a8d6afdd8%40googlegroups.com?utm_medium=email&utm_source=footer
>3. 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/20140703131722.GA15275%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: how to force an error

[jcbollinger]

On Thursday, July 3, 2014 5:21:33 AM UTC-5, Jose Luis Ledesma wrote:
>
> Hi,
>
>Does exist some way to force a  error while applying the catalog? We 
> need to check some facts vs configuration and force an error if doesnt' 
> match, so we could have a report from the node in the puppetdb with the 
> failed state. (we cannot use a compilation/evaluation error because it 
> doesn't report to the puppetdb)
>
>   Currently we use this ugly workaround:
>
> exec {'dummy exec to force an error':
>   path => ['/bin'],
> }
>
>   Is there any better solution?
>
>

Not really.  You could write a custom type that always fails, but that 
seems a lot of trouble, and not necessarily any better.  I'd write that 
exec a little prettier, though:

exec { 'Intentional Failure':
  command => '/bin/false'
} 


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/0e1f576b-5ca7-4819-bb82-4eb39b3156f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] schedule module according to certain server

[Andreas Dvorak]

Dear all,

I have a modul to install the apache webserver and I have server with 
different maintainance time frames.
So I can not create a schedule in the apache modul to install it a a 
certain time.
Is it possible to combine the include apache with a schedule.
For example the profile of server a 
include apache schedule 01:00 - 02:00
and profile of server b
include apache schedule 03:00 - 04:00

Or is it possible to use hiera to provide server specific schedule?

Can somebody please help me?

Best regards
Andreas

-- 
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/06e32159-6cb2-4c79-9192-de3935a56329%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Regarding Service elements in init.pp

[Satish Katuru]

Hi ,

My init.pp has two service elements like below:

class httpd
{

service{
"startjavaservice.sh":
ensure => "running",
}

service{
"stopjavaservice.sh":
ensure =>"stopped",

}
}

First one is for starting Java service and the second one is for stopping 
the same service.

*Problem:*

When it has  only one service then it is working fine but when it has two 
services it is not working.

(If  It has only startjavaservice then java service is getting started 
successfully and if it has only stopjavaservice java service is getting 
stopped.
If it has both the services first service should start and then it should 
be stopped but here only first thing happened. Java service has started but 
not stopped)

Can any one help me out on this?


Regards,
Sathish.

-- 
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/14b889bb-bbdf-4818-baa7-995a8d6afdd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] how to force an error

[Ken Barber]

>Does exist some way to force a  error while applying the catalog? We need
> to check some facts vs configuration and force an error if doesnt' match, so
> we could have a report from the node in the puppetdb with the failed state.
> (we cannot use a compilation/evaluation error because it doesn't report to
> the puppetdb)

This is fixed in the next release, 2.1.0.

>   Currently we use this ugly workaround:
>
> exec {'dummy exec to force an error':
>   path => ['/bin'],
> }
>
>   Is there any better solution?

I know its vapourware until its released, but I'd wait for 2.1.0 and
use the fail function,

ken.

-- 
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/CAE4bNTkvx%2BFQKPXVcqp5AURUS8c2s-eOSuVFOLVBYdva_wAc2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] New Puppet book: Extending Puppet

[Thomas Bendler]

​Also from my side, congratulations, I bought the ebook and start reading
it, so far, excellent, even for people with strong puppet knowledge.

Regards Thomas​


2014-07-03 11:23 GMT+02:00 Alessandro Franceschi :

> Thank you Johan and thank you all for the encouraging words.
> This is the first "live" feedback I receive and it's promising.
>
> I just would like to notify that the publisher Packt Publishing has
> promoted a small contest about it:
> whoever tweets something funny or interesting about the book, or why (s)he
> would like to read it, using this link http://bit.ly/extendingpuppet is
> eligible to win one free e-copy.
>
> What's better than a good free e-copy of a Puppet book to read before
> going to sleep? :-)
>
> Al
>
> On Tuesday, July 1, 2014 9:47:48 AM UTC+2, Johan De Wit wrote:
>
>>  Almost half way the book, and indeed, it IS a great book.
>>
>> Thx Allesandro for the great work.
>>
>> Jo
>>
>> On 01/07/14 09:41, Rakesh Kathpal wrote:
>>
>>  Congratulations Alessandro ... just ordered the ebook.. looks promising.
>>
>>  - Rakesh K.
>>
>>
>> On Sat, Jun 28, 2014 at 6:52 AM, Rich Burroughs 
>> wrote:
>>
>>> Yes congrats :) The table of contents looks like it covers a lot of
>>> useful material.
>>>
>>>
>>>  Rich
>>>
>>>
>>> On Thursday, June 26, 2014, Alessandro Franceschi  wrote:
>>>
 Sorry for the shameless promotion, but I suppose this might be of
 interest for the readers of this group.

 After more that 6 months of pain, efforts, frustration and excitement
 it's finally out a book where I tried to pour all my knowledge and
 experience on Puppet.
 It's oriented to people who have already some experience on Puppet (for
 beginners there are definitively more fitting titles around) and I hope it
 can give some useful information also to experienced users.

 Find more about it at:
 http://www.packtpub.com/extending-puppet/book

 You can get a free chapter here: http://bit.ly/1qbxWZy

 I'd take this occasion to thank some members of this group for their
 support, in particular:
 Brice Figureau, who has been a great technical reviewer and has
 prevented me from making some big mistakes. His support and help has been
 decisive.
 Nigel Kersten, who has written the Foreword and has given me very
 useful hints and feedback.
 Joshua Hoblitt, who has reviewed some chapters and has given great
 advices on the language and the contents.
 Daniele Sluijters, who has been a very precise technical reviewer for
 some chapters.
 Jon Forrest, who has slashed the language of my first drafts and opened
 my eyes on what it means to write in proper english (I obviously haven't
 learnt how to do it properly, but thanks to the reviewers the final output
 has been definitively more linguistically appropriate than the first
 drafts).

 I hope this book can help people who work with Puppet and, if you
 happen to get it, please give feedback, in any way you find appropriate.

 Thank you
 Alessandro Franceschi
  --
 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/30744a77-5c0b-4a14-94ff-6fa4cd364b32%
 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...@googlegroups.com.
>>>  To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/puppet-users/CAPGcbtA7KiUNmmJTR3HH0D8rsCzQD
>>> S51OOvOx9FE0-dAQQzV6w%40mail.gmail.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...@googlegroups.com.
>>
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/puppet-users/CAEJrXMXKpmpL2di8pioYqZgF6CgX6mJn%3Dzf_1t9tQJk1hLbNKA%
>> 40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.googl

[Puppet Users] where to configure proxy settings

[robert api]

hi there,

i'm currently trying to setup a automated update deliverysystem for a 
little program we develop.
in order to do that efficiently i was tasked to evaluate possible solutions 
and landed at puppets doorstep.

i wrote a small manifest that should do the trick (and it mostly does) and 
know its time to go through a couple of setup scenarios different customers 
may run.

one of them includes the usage of proxyservers, so i looked up the 
reference guide for the puppet.conf file and was happy to find the options 
"http_proxy_host/port"
i thought sweet, just specify the ip / port in the puppet.conf on the 
client that uses a proxy (c:\programdata\puppetlabs\puppet\etc) and off we 
go.

i my little test setup i run a freeware proxy and setup my gateway of the 
puppet client to that proxy, in troubleshooting why it doesnt work, i found 
that i shouldnt specify the ip rather than the fqdn of the proxy.
i did that, the client was talking to the server (i guess?) but i runs into 
an error, that says it didnt find any node definition for my client.

if i remove the proxy settings/setup the manifest runs smooth.

my initial thoughts would be 2 things i would like advice on:

maybe the puppet.conf on the client isnt the right place to try and specify 
the proxy settings? after a couple of google searches i found hits where 
people adviced to defining those settings environment variable with export? 
and since i'm just starting to puppet, i didnt really found that comment to 
be particulary helpful for me.

the second part may be to nameresolution? i dont run a dns server or domain 
server, just the puppet master in a debian vm and 2 win 7 vms (1 client / 
the other as the proxy server).
since i dont run a domain, i added a dns suffix for the proxy vm and tryed 
addressing it with "proxyserver.local" in the puppet.conf but that 
technicaly doesnt qualify as fdqn (right?) and for caution i added the 
proxy to the hosts file of the puppet client.

any pointers to get that going? i have no idea what else i can try.

any help would be much appreciated
greetings 

robert

-- 
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/1522a178-ce50-4e96-9b9f-fc29aa0a7dec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] how to force an error

[Jose Luis Ledesma]

Hi,

   Does exist some way to force a  error while applying the catalog? We 
need to check some facts vs configuration and force an error if doesnt' 
match, so we could have a report from the node in the puppetdb with the 
failed state. (we cannot use a compilation/evaluation error because it 
doesn't report to the puppetdb)

  Currently we use this ugly workaround:

exec {'dummy exec to force an error':
  path => ['/bin'],
}

  Is there any better solution?

thanks,
 

-- 
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/e4f5da29-aad3-4391-9dcc-ac2f986cf1b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] New Puppet book: Extending Puppet

[Alessandro Franceschi]

Thank you Johan and thank you all for the encouraging words.
This is the first "live" feedback I receive and it's promising.

I just would like to notify that the publisher Packt Publishing has 
promoted a small contest about it:
whoever tweets something funny or interesting about the book, or why (s)he 
would like to read it, using this link http://bit.ly/extendingpuppet is 
eligible to win one free e-copy.

What's better than a good free e-copy of a Puppet book to read before going 
to sleep? :-)

Al

On Tuesday, July 1, 2014 9:47:48 AM UTC+2, Johan De Wit wrote:

>  Almost half way the book, and indeed, it IS a great book.  
>
> Thx Allesandro for the great work.
>
> Jo
>
> On 01/07/14 09:41, Rakesh Kathpal wrote:
>  
>  Congratulations Alessandro ... just ordered the ebook.. looks promising.
>
>  - Rakesh K.
>  
>
> On Sat, Jun 28, 2014 at 6:52 AM, Rich Burroughs  > wrote:
>
>> Yes congrats :) The table of contents looks like it covers a lot of 
>> useful material. 
>>
>>  
>>  Rich 
>>
>>
>> On Thursday, June 26, 2014, Alessandro Franceschi > > wrote:
>>
>>> Sorry for the shameless promotion, but I suppose this might be of 
>>> interest for the readers of this group.
>>>
>>> After more that 6 months of pain, efforts, frustration and excitement 
>>> it's finally out a book where I tried to pour all my knowledge and 
>>> experience on Puppet.
>>> It's oriented to people who have already some experience on Puppet (for 
>>> beginners there are definitively more fitting titles around) and I hope it 
>>> can give some useful information also to experienced users. 
>>>
>>> Find more about it at:
>>> http://www.packtpub.com/extending-puppet/book
>>>  
>>> You can get a free chapter here: http://bit.ly/1qbxWZy
>>>
>>> I'd take this occasion to thank some members of this group for their 
>>> support, in particular:
>>> Brice Figureau, who has been a great technical reviewer and has 
>>> prevented me from making some big mistakes. His support and help has been 
>>> decisive.
>>> Nigel Kersten, who has written the Foreword and has given me very useful 
>>> hints and feedback.
>>> Joshua Hoblitt, who has reviewed some chapters and has given great 
>>> advices on the language and the contents.
>>> Daniele Sluijters, who has been a very precise technical reviewer for 
>>> some chapters.
>>> Jon Forrest, who has slashed the language of my first drafts and opened 
>>> my eyes on what it means to write in proper english (I obviously haven't 
>>> learnt how to do it properly, but thanks to the reviewers the final output 
>>> has been definitively more linguistically appropriate than the first 
>>> drafts).
>>>
>>> I hope this book can help people who work with Puppet and, if you happen 
>>> to get it, please give feedback, in any way you find appropriate.
>>>
>>> Thank you
>>> Alessandro Franceschi
>>>  -- 
>>> 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/30744a77-5c0b-4a14-94ff-6fa4cd364b32%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...@googlegroups.com .
>>  To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/CAPGcbtA7KiUNmmJTR3HH0D8rsCzQDS51OOvOx9FE0-dAQQzV6w%40mail.gmail.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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/CAEJrXMXKpmpL2di8pioYqZgF6CgX6mJn%3Dzf_1t9tQJk1hLbNKA%40mail.gmail.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> -- 
> Johan De Wit
>
> Open Source Consultant
>
> Red Hat Certified Engineer  (805008667232363)
> Puppet Certified Professional 2013/2014 (PCP006)
> _
>  
> Open-Future Ph

Re: [Puppet Users] Re: Forge doesn't work reliably for me

[Jonathan Gazeley]

Thanks Jesse, much appreciated. I'm now following the bug in Jira.

Cheers,
Jonathan


On 02/07/14 21:23, Jesse Scott wrote:
This appears to be a bug with how we report that you already have the 
latest available version for modules that only have a single release. 
I've opened a ticket in our bug tracker which you can follow here:


https://tickets.puppetlabs.com/browse/PUP-2882

If you have any additional information you would like to share related 
to this issue, you can do so on that ticket.



Thanks for the report!

-Jesse


On Tuesday, July 1, 2014 8:04:20 PM UTC-7, Michael Legleux wrote:

I'm also seeing this on:
https://forge.puppetlabs.com/rismoney/windowsnetwork


On Monday, June 30, 2014 5:24:17 AM UTC-7, Jonathan Gazeley wrote:

Recently I have been unable to upgrade some modules (or check for
upgrades) from Puppet Forge using the module tool.

All of my modules were originally installed from the Forge.
This problem
only occurs with some modules but it always occurs.

[jg4461@puppet-prod ~]$ sudo puppet module upgrade
ghoneycutt-sysklogd
Notice: Preparing to upgrade 'ghoneycutt-sysklogd' ...
Notice: Found 'ghoneycutt-sysklogd' (v1.0.0) in
/etc/puppet/modules ...
Notice: Downloading from https://forgeapi.puppetlabs.com
 ...
Error: Could not upgrade 'ghoneycutt-sysklogd' (v1.0.0 -> latest)
   No releases are available from
https://forgeapi.puppetlabs.com 
 Does 'ghoneycutt-sysklogd' have at least one published
release?

Besides ghoneycutt-sysklogd, other modules I am unable to
update are
crayfishx-hiera_mysql and mkrakowitzer-stash.

I heard that this problem may be caused by an incorrect
Modulefile but
these look OK to me. All three modules exist on the Forge and
with the
same name, so I'm not sure what to check next. Any ideas?

Cheers,
Jonathan

--
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/22637edb-6810-437e-a648-f2bc29d704ec%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/53B51FF0.2070107%40bristol.ac.uk.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Hiera variables working only with explicit mode

[Louis Coilliot]

Hello, it's working now on a new test, it must have been a human error on
the previous test because I didn't change anything in the configuration.
Dont acte.

Louis Coilliot


2014-07-02 18:20 GMT+02:00 Louis Coilliot :

> Hello,
>
> with a puppet master version 3.5, I only get hiera override if I set the
> variables if I used the explicit syntax.
>
> Example : $myvar=hiera('mymod::myvar,'failback')
>
> What did I miss to enable implicit override ?
>
> On other platform I set, this is working fine implicitly.
>
> The puppet master is linked to a Foreman, maybe this is related.
>
> Thanks in advance.
>
> Louis Coilliot
>

-- 
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/CAE9jN31Aph1CrOjJS8JX9%2BXhYEYjV_MdZw%2BuVLX-Jgyt3MQ4NQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.