[Puppet Users] puppet openstack

[Shoujin Wang]

Hi,

I got the follow errors while trying to install openstack nova on centos6.3 
through puppet. I am using puppet2.7.14 with puppetdb.
So how to debug this issue and find out the problem?

notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[keystone]: 
Dependency Keystone_service[keystone] has failures: true
warning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[keystone]: 
Skipping because of failed dependencies
err: Could not prefetch keystone_user_role provider 'keystone': undefined 
method `collect' for nil:NilClass
notice: 
/Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: 
Dependency Keystone_user[nova] has failures: true
notice: 
/Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: 
Dependency Keystone_role[admin] has failures: true
warning: 
/Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: 
Skipping because of failed dependencies
err: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Could not 
evaluate: undefined method `collect' for nil:NilClass
err: 
/Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: 
Could not evaluate: undefined method `collect' for nil:NilClass
err: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Could not 
evaluate: undefined method `collect' for nil:NilClass
err: /Stage[main]/Swift::Keystone::Auth/Keystone_service[swift]: Could not 
evaluate: undefined method `collect' for nil:NilClass
err: /Stage[main]/Swift::Keystone::Auth/Keystone_user[swift]: Could not 
evaluate: undefined method `collect' for nil:NilClass
notice: 
/Stage[main]/Swift::Keystone::Auth/Keystone_user_role[swift@services]: 
Dependency Keystone_user[swift] has failures: true
notice: 
/Stage[main]/Swift::Keystone::Auth/Keystone_user_role[swift@services]: 
Dependency Keystone_role[admin] has failures: true

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppetlabs-nova puppetlabs-keystone modules got the following error

[Shoujin Wang]

Hi,

I install the openstack nova on CentOS6.3 through the puppet. I use the 
puppet modules from puppetlabs. Got the following error.
I am using puppet 2.7.14 with puppetdb. 
For this kind of issue, how to debug and how to figure out where the issue 
is?

*err: Could not prefetch keystone_service provider 'keystone': undefined 
method `collect' for nil:NilClass
err: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_volume]: Could 
not evaluate: undefined method `collect' for nil:NilClass
err: Could not prefetch keystone_endpoint provider 'keystone': undefined 
method `collect' for nil:NilClass
err: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: 
Could not evaluate: undefined method `collect' for nil:NilClass
err: Could not prefetch keystone_role provider 'keystone': undefined method 
`collect' for nil:NilClass
err: /Stage[main]/Keystone::Roles::Admin/Keystone_role[Member]: Could not 
evaluate: undefined method `collect' for nil:NilClass
err: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Could 
not evaluate: undefined method `collect' for nil:NilClass
notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[keystone]: 
Dependency Keystone_service[keystone] has failures: true
warning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[keystone]: 
Skipping because of failed dependencies*
err: Could not prefetch keystone_user_role provider 'keystone': undefined 
method `collect' for nil:NilClass
notice: 
/Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: 
Dependency Keystone_user[nova] has failures: true
notice: 
/Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: 
Dependency Keystone_role[admin] has failures: true
warning: 
/Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: 
Skipping because of failed dependencies
err: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Could not 
evaluate: undefined method `collect' for nil:NilClass
err: 
/Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: 
Could not evaluate: undefined method `collect' for nil:NilClass
err: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Could not 
evaluate: undefined method `collect' for nil:NilClass
err: /Stage[main]/Swift::Keystone::Auth/Keystone_service[swift]: Could not 
evaluate: undefined method `collect' for nil:NilClass
err: /Stage[main]/Swift::Keystone::Auth/Keystone_user[swift]: Could not 
evaluate: undefined method `collect' for nil:NilClass
notice: 
/Stage[main]/Swift::Keystone::Auth/Keystone_user_role[swift@services]: 
Dependency Keystone_user[swift] has failures: true
notice: 
/Stage[main]/Swift::Keystone::Auth/Keystone_user_role[swift@services]: 
Dependency Keystone_role[admin] has failures: true


Regards,
Autumn Wang.

err: 
/Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_volume]: 
Could not evaluate: undefined method `collect' for nil:NilClass
err: Could not prefetch keystone_user provider 'keystone': undefined method 
`collect' for nil:NilClass
err: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Could not 
evaluate: undefined method `collect' for nil:NilClass
err: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Could not 
evaluate: undefined method `collect' for nil:NilClass
err: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Could not 
evaluate: undefined method `collect' for nil:NilClass

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Error login

[gustavo]

when I try Logar me no error no puppet acontece browser. Checking os's
you or seguinte error log:

Ticket-granting ticket 'TGC-1360178942r' for user 'ad...@teste.com'
successfully validated.
User 'ad...@teste.com' authenticated based on ticket granting cookie.
Redirecting to service 'https://10.1.0.29/'.
Only the "en" localization is available. Should you run `rake
localization: mo` to compile support for additional languages!

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Cobbler update

[kavitha . c . k2006]

Hello,


I have "cobbler 2.0.X" installed in my system. I want t update it to 
"2.2.3" . 
And I don't want to loose any of the profiles, repos present in my current 
cobbler.
I tried backing up the cobbler, don't know exactly that this will help
Any idea on this?

Thanks 
Kavitha






-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet master processing agent report time is very long, how to optimization

[serwei2014]

 
There is a puppet cluster, composed by nginx,passenger,puppet. The number of 
qps is 1000 currently,
and the processing speed of the whole cluster is pretty good,the average 
processing time for the request is 0.25 seconds.
 But it is a little slow from client report, a lot of processing time is tens 
of seconds.such 
as nginx log:
 
192.168.0.2 puppet  - [07/Feb/2013:15:45:44 +0800] "PUT 
/production/report/123.test.test.cn HTTP/1.1" 200 24 "-" "-" "-" 95.690 
192.168.12.12:8140 200 *95.876*
 
The Normal request:
192.168.0.2 puppet   - [07/Feb/2013:16:03:52 +0800] "GET 
/production/file_metadata/files/123.py HTTP/1.1" 200 324 "-" "-" "-" 0.014 
192.168.12.12:8140 200 0.105
 
puppet version:2.6.11
nginx version:1.0.9
passenger version:3.0.13 and 3.0.17
 
The Server cluster still have not reached the performance bottleneck
 
nginx proxy buffer is large enough
 
passenger conf :
passenger_root /usr/lib/ruby/gems/1.8/gems/passenger-3.0.17;
passenger_ruby /usr/bin/ruby;
passenger_max_pool_size 150;
passenger_use_global_queue on;
passenger_max_requests 4000;
passenger_pool_idle_time 100;
 
how to optimize?

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Is there any other tool other than mcollective for orchestration..

[DreamBig]

Hi,

I guess mcollective supports only linux and similar OS. It does not
have a package for Solaris or even a way to create a package from
standard tar file. Can someone suggest any other tool?

Regards,
Rajeev

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Is there any other tool other than mcollective for orchestration..

[kavitha . c . k2006]

Hi,

There is a tools called "Ansible" , I think it works on solaris


Kavitha


On Thursday, February 7, 2013 2:28:32 PM UTC+5:30, Rajeev Iyer wrote:
>
> Hi, 
>
> I guess mcollective supports only linux and similar OS. It does not 
> have a package for Solaris or even a way to create a package from 
> standard tar file. Can someone suggest any other tool? 
>
> Regards, 
> Rajeev 
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Is there any other tool other than mcollective for orchestration..

[DreamBig]

Thanks..

On Feb 7, 2:31 pm, kavitha.c.k2...@gmail.com wrote:
> Hi,
>
> There is a tools called "Ansible" , I think it works on solaris
>
> Kavitha
>
>
>
>
>
>
>
> On Thursday, February 7, 2013 2:28:32 PM UTC+5:30, Rajeev Iyer wrote:
>
> > Hi,
>
> > I guess mcollective supports only linux and similar OS. It does not
> > have a package for Solaris or even a way to create a package from
> > standard tar file. Can someone suggest any other tool?
>
> > Regards,
> > Rajeev

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Cobbler update

[Stefan Heijmans]

Hi, better try the Cobbler email list @ 
https://lists.fedorahosted.org/mailman/listinfo/cobbler

Op donderdag 7 februari 2013 09:27:05 UTC+1 schreef kavitha...@gmail.com 
het volgende:

> Hello, 
>
>
> I have "cobbler 2.0.X" installed in my system. I want t update it to 
> "2.2.3" . 
> And I don't want to loose any of the profiles, repos present in my current 
> cobbler.
> I tried backing up the cobbler, don't know exactly that this will help
> Any idea on this?
>
> Thanks 
> Kavitha
>
>
>
>
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] service ressource on CentOS 6.3

[GRANIER Bernard (MORPHO)]

Hi,

I have a jboss service running on a Cent0S 6.3 64 bits

I use :

service{'jboss':
   ensure => 'stopped',
   hasstatus => false,
}

To stop the service, but puppet give the following traces :
Error: /Stage[main]/Jbossuninstall/Service[jboss]/ensure: change from running 
to stopped failed: Could not stop Service[jboss]: Execution of '/sbin/service 
jboss stop' returned :

In fact command /sbin/service jboss stop returns 143, is it the error reason ?

And how can I stop a jboss service on CentOS 6.3 ?

Cordialement,

Bernard Granier
CE Plateforme Système
bernard.gran...@morpho.com
01 58 11 32 51

#
" This e-mail and any attached documents may contain confidential or 
proprietary information. If you are not the intended recipient, you are 
notified that any dissemination, copying of this e-mail and any attachments 
thereto or use of their contents by any means whatsoever is strictly 
prohibited. If you have received this e-mail in error, please advise the sender 
immediately and delete this e-mail and all attached documents from your 
computer system."
#

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] New Type/Provider... How to handle cli input???

[Gavin Williams]

Morning all

I'm looking at writing a set of types/providers to handle NetApp SnapDrive 
configuration and usage... 

There's quite a lot to SnapDrive, so initially, I'm just trying to get it 
to manage credentials. 

The challenge I can immediately see is that for me to set a credential, the 
command prompts for a password input twice... Example command run is: 
# snapdrive config set sd-act-star-db05 act-star-nactl01
Password for sd-act-star-db05:
Retype password:
-957 Warning: Optionally, Please set -mgmtpath interface for 
act-star-nactl01 to be used as data interface i.e
snapdrive config set -mgmtpath  act-star-nactl01

Is it possible to cater for this in a provider? 

Cheers
Gavin 

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] IIS / ASP.Net Module for Windows 2003 / windows 2008

[Rakesh Kathpal]

Hi,

I am looking for IIS and asp.net module for windows 2003 & windows 2008,
can anyone please help ?

I came across the module https://github.com/puppetlabs/puppetlabs-dism but
it works only for windows 2008 R2

Also I had a look at the module https://github.com/simondean/puppet-iis but
not sure what should I put it in my nodes.pp for it to work.

Thanks & Regards,

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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet broken in upgrade from 3.0.1 to 3.1.0

[Dominic Cleal]

On 06/02/13 16:46, thinkwell wrote:
> Hello everyone,
> 
> Recently puppet was upgraded from 3.0.1 to 3.1.0 when I did a sudo
> apt-get update on my Kubuntu server.
> 
> Now, I'm getting the following error
> when running puppet. My
> config.ru file is the same as
> the source3.1.0 config.ru file
> .
> 
> So I'm scratching my head. My apache error log only shows:
> 
> [code]
> [Wed Feb 06 11:37:08 2013] [warn] RSA server certificate CommonName (CN)
> `' does NOT match server name!?
> [/code]
> But that apparently didn't prevent puppet from functioning for quite
> some time, since I found I was getting that error months ago.
> [code]
> [Sun Dec 09 07:57:49 2012] [warn] RSA server certificate CommonName (CN)
> `' does NOT match server name!?
> [/code]
> 
> Anybody have some help for me?

Do check syslog, as the puppet master usually logs initialisation
problems there (e.g. permissions).

-- 
Dominic Cleal
Red Hat Engineering

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet master processing agent report time is very long, how to optimization

[Dominic Cleal]

On 07/02/13 08:30, serwei2...@gmail.com wrote:
> There is a puppet cluster, composed by nginx,passenger,puppet. The number of 
> qps is 1000 currently,
> and the processing speed of the whole cluster is pretty good,the average 
> processing time for the request is 0.25 seconds.
>  But it is a little slow from client report, a lot of processing time is tens 
> of seconds.such
> as nginx log:
>  
> 192.168.0.2 puppet  - [07/Feb/2013:15:45:44 +0800] "PUT
> /production/report/123.test.test.cn HTTP/1.1" 200 24 "-" "-" "-" 95.690
> 192.168.12.12:8140 200 _95.876_

Are you using reports for anything?

By default Puppet enables and stores them.  You can disable storage on
your master with:

[master]
reports =

Or you can disable sending them on your agents with:

[agent]
report = false

If you're using disk stored reports for something useful, then look at
PuppetDB 1.1 instead, or improve your storage.  If you're using another
report processor (e.g. Foreman), then you need to optimise that.

-- 
Dominic Cleal
Red Hat Engineering

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] storeconfigs and exported resources?

[Ken Barber]

That hash been changed now on docs.puppetlabs.com Jakov, again ... thanks.

On Wed, Feb 6, 2013 at 8:56 PM, Ken Barber  wrote:
>> Also, please note that puppetmasterd section is still in the official
>> documentation, like for example here:
>>
>> http://docs.puppetlabs.com/guides/exported_resources.html
>>
>> So that's what got me on the wrong track in the first place.
>
> Aaah - righto - well I've raised a pull request on that, our docs team
> just did a quick scan and it looks like the last instance of it:
>
> https://github.com/puppetlabs/puppet-docs/pull/134
>
> Hopefully this should be fixed on the public site soon. Thanks for the
> heads up Jakov :-).
>
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] mcollective-puppet-agent to return status of Puppet execution

[Andriy Yurchuk]

 

I'm using mcollective-puppet-agent (
https://github.com/puppetlabs/mcollective-puppet-agent) to force Puppet 
runs on nodes. When running mco puppet runall is there any way I can get 
back the status of Puppet execution on each node? Currently, even if 
verbosity is enabled, mco does not provide much of information:

2013-02-07 13:29:54: Running all nodes with a concurrency of 10
2013-02-07 13:29:54: Discovering enabled Puppet nodes to manage
Discovering hosts using the mc method for 3 second(s)  5
2013-02-07 13:29:57: Found 5 enabled nodes
Discovering hosts using the mc method for 3 second(s)  0
2013-02-07 13:30:00: oms-753 schedule status: Started a background Puppet run 
using the 'puppet agent --onetime --daemonize --color=false' command
2013-02-07 13:30:01: oms-9421 schedule status: Started a background Puppet run 
using the 'puppet agent --onetime --daemonize --color=false' command
2013-02-07 13:30:03: oms-11728 schedule status: Started a background Puppet run 
using the 'puppet agent --onetime --daemonize --color=false' command
2013-02-07 13:30:04: oms-9812 schedule status: Started a background Puppet run 
using the 'puppet agent --onetime --daemonize --color=false' command
2013-02-07 13:30:05: oms-2787 schedule status: Started a background Puppet run 
using the 'puppet agent --onetime --daemonize --color=false' command


Is there any way to at least report back if Puppet run has succeeded or 
failed?

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet broken in upgrade from 3.0.1 to 3.1.0

[thinkwell]

My problem is now resolved... Thanks for your replies, Dominic and Johan. 

I'm not using puppet to manage the puppet server, but in the course of 
troubleshooting, I tried running puppet agent -t on the puppet server. This 
gave me a certificate mismatch error and when I deleted the old certificate 
and created & signed a new one, everything worked.

Sorta puzzles me. Why would this mismatched agent certificate on 
puppetmaster interfered with other puppet agent runs?


-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet broken in upgrade from 3.0.1 to 3.1.0

[Dominic Cleal]

On 07/02/13 13:46, thinkwell wrote:
> My problem is now resolved... Thanks for your replies, Dominic and Johan.
> 
> I'm not using puppet to manage the puppet server, but in the course of
> troubleshooting, I tried running puppet agent -t on the puppet server.
> This gave me a certificate mismatch error and when I deleted the old
> certificate and created & signed a new one, everything worked.
> 
> Sorta puzzles me. Why would this mismatched agent certificate on
> puppetmaster interfered with other puppet agent runs?

The same certificate that is used for the agent on the master server is
also used for the master process itself (inbound connections).

-- 
Dominic Cleal
Red Hat Engineering

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] mcollective-puppet-agent to return status of Puppet execution

[R.I.Pienaar]

- Original Message -
> From: "Andriy Yurchuk" 
> To: puppet-users@googlegroups.com
> Sent: Thursday, February 7, 2013 2:42:30 PM
> Subject: [Puppet Users] mcollective-puppet-agent to return status of Puppet 
> execution
> 
> 
> 
> I'm using mcollective-puppet-agent (
> https://github.com/puppetlabs/mcollective-puppet-agent) to force Puppet
> runs on nodes. When running mco puppet runall is there any way I can get
> back the status of Puppet execution on each node? Currently, even if
> verbosity is enabled, mco does not provide much of information:
> 
> 2013-02-07 13:29:54: Running all nodes with a concurrency of 10
> 2013-02-07 13:29:54: Discovering enabled Puppet nodes to manage
> Discovering hosts using the mc method for 3 second(s)  5
> 2013-02-07 13:29:57: Found 5 enabled nodes
> Discovering hosts using the mc method for 3 second(s)  0
> 2013-02-07 13:30:00: oms-753 schedule status: Started a background Puppet run
> using the 'puppet agent --onetime --daemonize --color=false' command
> 2013-02-07 13:30:01: oms-9421 schedule status: Started a background Puppet
> run using the 'puppet agent --onetime --daemonize --color=false' command
> 2013-02-07 13:30:03: oms-11728 schedule status: Started a background Puppet
> run using the 'puppet agent --onetime --daemonize --color=false' command
> 2013-02-07 13:30:04: oms-9812 schedule status: Started a background Puppet
> run using the 'puppet agent --onetime --daemonize --color=false' command
> 2013-02-07 13:30:05: oms-2787 schedule status: Started a background Puppet
> run using the 'puppet agent --onetime --daemonize --color=false' command
> 
> 
> Is there any way to at least report back if Puppet run has succeeded or
> failed?
> 


no not in the middle of runall, we just schedule a puppet run to run in the
background - puppet runs can take random periods of time it wouldnt work to 
try and wait for each one to reply done - your reporting infrastructure etc
should be used for that.

you can use the status commands to pull out statusses after the run which would
include details like failed/changed/etc resources

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] mcollective-puppet-agent to return status of Puppet execution

[Andriy Yurchuk]

Do I understand correctly that to forcefully run Puppet agents (without 
daemonizing them to run periodically) on all nodes the runall is not the 
right choice? Should I use runonce?
To clarify, my use case is the following: I change the contents of the file 
that is the source for one of Puppets file resources, then I want all my 
nodes to fetch this change.

On Thursday, February 7, 2013 3:53:57 PM UTC+2, R.I. Pienaar wrote:
>
>
>
> - Original Message - 
> > From: "Andriy Yurchuk" > 
> > To: puppet...@googlegroups.com  
> > Sent: Thursday, February 7, 2013 2:42:30 PM 
> > Subject: [Puppet Users] mcollective-puppet-agent to return status of 
> Puppet execution 
> > 
> > 
> > 
> > I'm using mcollective-puppet-agent ( 
> > https://github.com/puppetlabs/mcollective-puppet-agent) to force Puppet 
> > runs on nodes. When running mco puppet runall is there any way I can get 
> > back the status of Puppet execution on each node? Currently, even if 
> > verbosity is enabled, mco does not provide much of information: 
> > 
> > 2013-02-07 13:29:54: Running all nodes with a concurrency of 10 
> > 2013-02-07 13:29:54: Discovering enabled Puppet nodes to manage 
> > Discovering hosts using the mc method for 3 second(s)  5 
> > 2013-02-07 13:29:57: Found 5 enabled nodes 
> > Discovering hosts using the mc method for 3 second(s)  0 
> > 2013-02-07 13:30:00: oms-753 schedule status: Started a background 
> Puppet run 
> > using the 'puppet agent --onetime --daemonize --color=false' command 
> > 2013-02-07 13:30:01: oms-9421 schedule status: Started a background 
> Puppet 
> > run using the 'puppet agent --onetime --daemonize --color=false' command 
> > 2013-02-07 13:30:03: oms-11728 schedule status: Started a background 
> Puppet 
> > run using the 'puppet agent --onetime --daemonize --color=false' command 
> > 2013-02-07 13:30:04: oms-9812 schedule status: Started a background 
> Puppet 
> > run using the 'puppet agent --onetime --daemonize --color=false' command 
> > 2013-02-07 13:30:05: oms-2787 schedule status: Started a background 
> Puppet 
> > run using the 'puppet agent --onetime --daemonize --color=false' command 
> > 
> > 
> > Is there any way to at least report back if Puppet run has succeeded or 
> > failed? 
> > 
>
>
> no not in the middle of runall, we just schedule a puppet run to run in 
> the 
> background - puppet runs can take random periods of time it wouldnt work 
> to 
> try and wait for each one to reply done - your reporting infrastructure 
> etc 
> should be used for that. 
>
> you can use the status commands to pull out statusses after the run which 
> would 
> include details like failed/changed/etc resources 
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Puppet F5 module

[MrTeleBird]

Yes, the problem was version compatibility with my LTM. I upgrade to 
version 10.2.4 and voila, it works now!!

Cheers

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: service ressource on CentOS 6.3

[jcbollinger]

On Thursday, February 7, 2013 4:49:18 AM UTC-6, bernard...@morpho.com wrote:
>
> Error: /Stage[main]/Jbossuninstall/Service[jboss]/ensure: change from 
> running to stopped failed: Could not stop Service[jboss]: Execution of 
> '/sbin/service jboss stop' returned :
>
>  
>
> In fact command /sbin/service jboss stop returns 143, is it the error 
> reason ?
>
>
Yes.  Linux Standards Base specifications call for initscript actions other 
than 'status' to return 0 on success, and Puppet relies on your services to 
comply.  Supposing that Jboss is in fact stopped successfully in your 
scenario, the initscript is defective on account of returning the wrong 
code.  This is not a CentOS problem, because CentOS did not provide 
whatever Jboss package you are using.

Supposing that you don't want to fix the Jboss init script, you can work 
around its buggy behavior by declaring a custom 'stop' command for the 
Service resource.  You'll have to determine the details to match your 
requirements and the behavior of the initscript.  If you don't care whether 
jboss really does stop then it might be '/bin/bash -c "/sbin/service jboss 
stop || /bin/true"'.


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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: New Type/Provider... How to handle cli input???

[jcbollinger]

On Thursday, February 7, 2013 5:12:41 AM UTC-6, Gavin Williams wrote:
>
> Morning all
>
> I'm looking at writing a set of types/providers to handle NetApp SnapDrive 
> configuration and usage... 
>
> There's quite a lot to SnapDrive, so initially, I'm just trying to get it 
> to manage credentials. 
>
> The challenge I can immediately see is that for me to set a credential, 
> the command prompts for a password input twice... Example command run is: 
> # snapdrive config set sd-act-star-db05 act-star-nactl01
> Password for sd-act-star-db05:
> Retype password:
> -957 Warning: Optionally, Please set -mgmtpath interface for 
> act-star-nactl01 to be used as data interface i.e
> snapdrive config set -mgmtpath  act-star-nactl01
>
> Is it possible to cater for this in a provider? 
>
>

In principle, you can redirect appropriate canned responses into the 
command's standard input. I don't recall offhand whether Puppet's built-in 
executor facilities support that directly, but you can always wrap up 
something like that in a 'bash -c' command.

It would be far better, however, if the configuration program were built to 
be scriptable (i.e. to not require interactive I/O).  For one thing, does 
your installer prompt for a password even when it is run by root (which is 
what the agent will do in the usual configuration)?  Does it support 
command-line options by which you can bypass any other Q&A?


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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet F5: Graceful Server Shutdown

[MrTeleBird]

HI,

How can I gracefully shut down my servers of a given pool member for 
maintenance without disrupting current user sessions using the F5 iControl 
module??...and of course, allowing for enabling and disabling of the server 
for a pool

Has anyone done this before?

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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Windows Service keeps stopping/starting

[jim]

Hello all,

Can anyone please help, every time I push a config to my hosts, the windows 
service I have just defined keeps stopping and starting, and logging in the 
eventlog, 

I only want the service to stop and start, if something has changed, and to 
my knowledge nothing has changed ? so it should stay running ?

Can some one please help or explain 

regards

James

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

RE: [Puppet Users] Re: service ressource on CentOS 6.3

[GRANIER Bernard (MORPHO)]

Hi,

Thanks for your anwser, to solve my problem I write an exec resource with a 
kill ...

That should not be puppet spirit, anyway it runs ...

Cordialement,

Bernard Granier
CE Plateforme Système
bernard.gran...@morpho.com
01 58 11 32 51

From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On 
Behalf Of jcbollinger
Sent: Thursday, February 07, 2013 3:28 PM
To: puppet-users@googlegroups.com
Subject: [Puppet Users] Re: service ressource on CentOS 6.3



On Thursday, February 7, 2013 4:49:18 AM UTC-6, 
bernard...@morpho.com wrote:
Error: /Stage[main]/Jbossuninstall/Service[jboss]/ensure: change from running 
to stopped failed: Could not stop Service[jboss]: Execution of '/sbin/service 
jboss stop' returned :

In fact command /sbin/service jboss stop returns 143, is it the error reason ?


Yes.  Linux Standards Base specifications call for initscript actions other 
than 'status' to return 0 on success, and Puppet relies on your services to 
comply.  Supposing that Jboss is in fact stopped successfully in your scenario, 
the initscript is defective on account of returning the wrong code.  This is 
not a CentOS problem, because CentOS did not provide whatever Jboss package you 
are using.

Supposing that you don't want to fix the Jboss init script, you can work around 
its buggy behavior by declaring a custom 'stop' command for the Service 
resource.  You'll have to determine the details to match your requirements and 
the behavior of the initscript.  If you don't care whether jboss really does 
stop then it might be '/bin/bash -c "/sbin/service jboss stop || /bin/true"'.


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 post to this group, send email to 
puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


#
" This e-mail and any attached documents may contain confidential or 
proprietary information. If you are not the intended recipient, you are 
notified that any dissemination, copying of this e-mail and any attachments 
thereto or use of their contents by any means whatsoever is strictly 
prohibited. If you have received this e-mail in error, please advise the sender 
immediately and delete this e-mail and all attached documents from your 
computer system."
#

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: New Type/Provider... How to handle cli input???

[fatmcgav]

John

Cheers for the response...

Unfortunately SnapDrive is not my program - It's a NetApp program, so I'm
not going to be able to change it :(
Also doesn't look like it's designed to support command line args... :( :(

But in principle, it looks like it's possible, but a bit hacky...

Cheers
Gavin


On 7 February 2013 14:42, jcbollinger  wrote:

>
>
> On Thursday, February 7, 2013 5:12:41 AM UTC-6, Gavin Williams wrote:
>>
>> Morning all
>>
>> I'm looking at writing a set of types/providers to handle NetApp
>> SnapDrive configuration and usage...
>>
>> There's quite a lot to SnapDrive, so initially, I'm just trying to get it
>> to manage credentials.
>>
>> The challenge I can immediately see is that for me to set a credential,
>> the command prompts for a password input twice... Example command run is:
>> # snapdrive config set sd-act-star-db05 act-star-nactl01
>> Password for sd-act-star-db05:
>> Retype password:
>> -957 Warning: Optionally, Please set -mgmtpath interface for
>> act-star-nactl01 to be used as data interface i.e
>> snapdrive config set -mgmtpath  act-star-nactl01
>>
>> Is it possible to cater for this in a provider?
>>
>>
>
> In principle, you can redirect appropriate canned responses into the
> command's standard input. I don't recall offhand whether Puppet's built-in
> executor facilities support that directly, but you can always wrap up
> something like that in a 'bash -c' command.
>
> It would be far better, however, if the configuration program were built
> to be scriptable (i.e. to not require interactive I/O).  For one thing,
> does your installer prompt for a password even when it is run by root
> (which is what the agent will do in the usual configuration)?  Does it
> support command-line options by which you can bypass any other Q&A?
>
>
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: service ressource on CentOS 6.3

[Dan White]

A better way would be, IMHO, to modify the init-script to do the correct things 
for both the JBoss processes and Puppet. 

I am working in that direction with the stuff I have to maintain. 
Stacks running apache, mysql, tomcat and other things. Rather than one 
init-script for each, I'd like to implement an init-script that will start / 
stop / restart / status the entire stack at once as well as individual pieces 
thereof. 


“Sometimes I think the surest sign that intelligent life exists elsewhere in 
the universe is that none of it has tried to contact us.” 
Bill Waterson (Calvin & Hobbes) 

- Original Message -
From: "GRANIER Bernard (MORPHO)"  
To: puppet-users@googlegroups.com 
Sent: Thursday, February 7, 2013 10:17:06 AM 
Subject: RE: [Puppet Users] Re: service ressource on CentOS 6.3 




Hi, 



Thanks for your anwser, to solve my problem I write an exec resource with a 
kill … 



That should not be puppet spirit, anyway it runs … 



Cordialement, 



Bernard Granier 

CE Plateforme Système 

bernard.gran...@morpho.com 

01 58 11 32 51 




From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On 
Behalf Of jcbollinger 
Sent: Thursday, February 07, 2013 3:28 PM 
To: puppet-users@googlegroups.com 
Subject: [Puppet Users] Re: service ressource on CentOS 6.3 





On Thursday, February 7, 2013 4:49:18 AM UTC-6, bernard...@morpho.com wrote: 



Error: /Stage[main]/Jbossuninstall/Service[jboss]/ensure: change from running 
to stopped failed: Could not stop Service[jboss]: Execution of '/sbin/service 
jboss stop' returned : 



In fact command /sbin/service jboss stop returns 143, is it the error reason ? 





Yes. Linux Standards Base specifications call for initscript actions other than 
'status' to return 0 on success, and Puppet relies on your services to comply. 
Supposing that Jboss is in fact stopped successfully in your scenario, the 
initscript is defective on account of returning the wrong code. This is not a 
CentOS problem, because CentOS did not provide whatever Jboss package you are 
using. 

Supposing that you don't want to fix the Jboss init script, you can work around 
its buggy behavior by declaring a custom 'stop' command for the Service 
resource. You'll have to determine the details to match your requirements and 
the behavior of the initscript. If you don't care whether jboss really does 
stop then it might be '/bin/bash -c "/sbin/service jboss stop || /bin/true"'. 


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 post to this group, send email to puppet-users@googlegroups.com . 
Visit this group at http://groups.google.com/group/puppet-users?hl=en . 
For more options, visit https://groups.google.com/groups/opt_out . 



# 
" This e-mail and any attached documents may contain confidential or 
proprietary information. If you are not the intended recipient, you are 
notified that any dissemination, copying of this e-mail and any attachments 
thereto or use of their contents by any means whatsoever is strictly 
prohibited. If you have received this e-mail in error, please advise the sender 
immediately and delete this e-mail and all attached documents from your 
computer system." 
# 

-- 
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 post to this group, send email to puppet-users@googlegroups.com. 
Visit this group at http://groups.google.com/group/puppet-users?hl=en . 
For more options, visit https://groups.google.com/groups/opt_out . 


-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: service ressource on CentOS 6.3

[Johan De Wit]

Hi,

Rewriting the script is indeed a good solution, check
 
http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html

The service resource  has also the "status" and "hasstatus" resource.  
Maybe using one or both of them could also solve your problem


Puppet describe service gives more documention

Grts

Jo

On 02/07/2013 04:28 PM, Dan White wrote:
A better way would be, IMHO, to modify the init-script to do the 
correct things for both the JBoss processes and Puppet.


I am working in that direction with the stuff I have to maintain.
Stacks running apache, mysql, tomcat and other things.  Rather than 
one init-script for each, I'd like to implement an init-script that 
will start / stop / restart / status the entire stack at once as well 
as individual pieces thereof.


“Sometimes I think the surest sign that intelligent life exists 
elsewhere in the universe is that none of it has tried to contact us.”

Bill Waterson (Calvin & Hobbes)


*From: *"GRANIER Bernard (MORPHO)" 
*To: *puppet-users@googlegroups.com
*Sent: *Thursday, February 7, 2013 10:17:06 AM
*Subject: *RE: [Puppet Users] Re: service ressource on CentOS 6.3

Hi,

Thanks for your anwser, to solve my problem I write an exec resource 
with a kill …


That should not be puppet spirit, anyway it runs …

Cordialement,

Bernard Granier

CE Plateforme Système

bernard.gran...@morpho.com 

01 58 11 32 51

*From:*puppet-users@googlegroups.com 
[mailto:puppet-users@googlegroups.com] *On Behalf Of *jcbollinger

*Sent:* Thursday, February 07, 2013 3:28 PM
*To:* puppet-users@googlegroups.com
*Subject:* [Puppet Users] Re: service ressource on CentOS 6.3



On Thursday, February 7, 2013 4:49:18 AM UTC-6, bernard...@morpho.com 
 wrote:


Error: /Stage[main]/Jbossuninstall/Service[jboss]/ensure: change from 
running to stopped failed: Could not stop Service[jboss]: Execution of 
'/sbin/service jboss stop' returned :


In fact command /sbin/service jboss stop returns 143, is it the error 
reason ?



Yes.  Linux Standards Base specifications call for initscript actions 
other than 'status' to return 0 on success, and Puppet relies on your 
services to comply. Supposing that Jboss is in fact stopped 
successfully in your scenario, the initscript is defective on account 
of returning the wrong code.  This is not a CentOS problem, because 
CentOS did not provide whatever Jboss package you are using.


Supposing that you don't want to fix the Jboss init script, you can 
work around its buggy behavior by declaring a custom 'stop' command 
for the Service resource.  You'll have to determine the details to 
match your requirements and the behavior of the initscript.  If you 
don't care whether jboss really does stop then it might be '/bin/bash 
-c "/sbin/service jboss stop || /bin/true"'.



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 post to this group, send email to puppet-users@googlegroups.com 
.

Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

#
" This e-mail and any attached documents may contain confidential or 
proprietary information. If you are not the intended recipient, you 
are notified that any dissemination, copying of this e-mail and any 
attachments thereto or use of their contents by any means whatsoever 
is strictly prohibited. If you have received this e-mail in error, 
please advise the sender immediately and delete this e-mail and all 
attached documents from your computer system."

#

--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.





--
Johan De Wit

Open Source Consultant
Red Hat Certified Engineer(805008667232363)
Puppet Certified Professional 2013 (PCP006)

Re: [Puppet Users] mcollective-puppet-agent to return status of Puppet execution

[R.I.Pienaar]

- Original Message -
> From: "Andriy Yurchuk" 
> To: puppet-users@googlegroups.com
> Sent: Thursday, February 7, 2013 3:05:22 PM
> Subject: Re: [Puppet Users] mcollective-puppet-agent to return status of 
> Puppet execution
> 
> Do I understand correctly that to forcefully run Puppet agents (without
> daemonizing them to run periodically) on all nodes the runall is not the
> right choice? Should I use runonce?
> To clarify, my use case is the following: I change the contents of the file
> that is the source for one of Puppets file resources, then I want all my
> nodes to fetch this change.

runall does that, runonce too.  Underneath runall does a runonce but it manages
how many machines does the run at the same time

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Windows Service keeps stopping/starting

[Josh Cooper]

Hi Jim,

On Thu, Feb 7, 2013 at 7:15 AM, jim  wrote:
> Hello all,
>
> Can anyone please help, every time I push a config to my hosts, the windows
> service I have just defined keeps stopping and starting, and logging in the
> eventlog,
>
> I only want the service to stop and start, if something has changed, and to
> my knowledge nothing has changed ? so it should stay running ?
>
> Can some one please help or explain
>
> regards
>
> James
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

>From http://docs.puppetlabs.com/references/latest/type.html#service,
"Note that if a service receives an event from another resource, the
service will get restarted."

Can you post your manifest? Sounds like your service is subscribed to
some other resource, perhaps a package whose name doesn't match its
name in Add/Remove Programs?

Josh

--
Josh Cooper
Developer, Puppet Labs

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] storeconfigs and exported resources?

[Jakov Sosic]

On 02/07/2013 02:35 PM, Ken Barber wrote:
> That hash been changed now on docs.puppetlabs.com Jakov, again ... thanks.

No problem, always glad to help back :)

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: New Type/Provider... How to handle cli input???

[Justin Stoller]

There's a completely undocumented (outside of the Pickaxe book) Ruby STDLIB
module called 'expect' that you could use in 1.8.7, open up irb and give it
a whirl. You can find other expect like gems (or at least crib how they're
using the pty)[1]. I think you'll want something like expect4r[2] extended
for NetApp.


HTH,
Justin

1. https://rubygems.org/search?utf8=%E2%9C%93&query=expect
2. https://github.com/jesnault/expect4r


On Thu, Feb 7, 2013 at 7:18 AM, fatmcgav  wrote:

> John
>
> Cheers for the response...
>
> Unfortunately SnapDrive is not my program - It's a NetApp program, so I'm
> not going to be able to change it :(
> Also doesn't look like it's designed to support command line args... :( :(
>
> But in principle, it looks like it's possible, but a bit hacky...
>
> Cheers
> Gavin
>
>
> On 7 February 2013 14:42, jcbollinger  wrote:
>
>>
>>
>> On Thursday, February 7, 2013 5:12:41 AM UTC-6, Gavin Williams wrote:
>>>
>>> Morning all
>>>
>>> I'm looking at writing a set of types/providers to handle NetApp
>>> SnapDrive configuration and usage...
>>>
>>> There's quite a lot to SnapDrive, so initially, I'm just trying to get
>>> it to manage credentials.
>>>
>>> The challenge I can immediately see is that for me to set a credential,
>>> the command prompts for a password input twice... Example command run is:
>>> # snapdrive config set sd-act-star-db05 act-star-nactl01
>>> Password for sd-act-star-db05:
>>> Retype password:
>>> -957 Warning: Optionally, Please set -mgmtpath interface for
>>> act-star-nactl01 to be used as data interface i.e
>>> snapdrive config set -mgmtpath  act-star-nactl01
>>>
>>> Is it possible to cater for this in a provider?
>>>
>>>
>>
>> In principle, you can redirect appropriate canned responses into the
>> command's standard input. I don't recall offhand whether Puppet's built-in
>> executor facilities support that directly, but you can always wrap up
>> something like that in a 'bash -c' command.
>>
>> It would be far better, however, if the configuration program were built
>> to be scriptable (i.e. to not require interactive I/O).  For one thing,
>> does your installer prompt for a password even when it is run by root
>> (which is what the agent will do in the usual configuration)?  Does it
>> support command-line options by which you can bypass any other Q&A?
>>
>>
>> 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 post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] stdlib::member "support for strings and hashes" todo

[greg . poirier]

I am curious as to how support for strings would work. To me, it seems 
there are two possibile use-cases for support for strings. Take the 
following example:

Assume:
  - extdata exists, identified by 'array'
  - extlookup('array') may return an array or a single string (in the case 
that the "array" only has one member)

Case 1: 
$array = extlookup("array") -> extlookup returns a string
member($array, 'some_string') -> returns true if $array is the string 
'some_string'

Case 2:
$array = extlookup("array") -> extlookup returns an array
member returns true if array.includes?('some_string')

The alternative, I suppose, would be substring matching, but in that case 
wouldn't "member" be a misnomer and shouldn't the more common substr() be 
added?

For hash membership, we would want to look for key membership, yes?

Anyway, came across an instance of when this kind of behavior would be 
useful, and was wondering if this behavior was the intent behind this 
particular TODO. If so, I will submit a patch.

Thanks,

Greg

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet F5: Graceful Server Shutdown

[Nan Liu]

On Thu, Feb 7, 2013 at 6:46 AM, MrTeleBird  wrote:

> How can I gracefully shut down my servers of a given pool member for
> maintenance without disrupting current user sessions using the F5 iControl
> module??...and of course, allowing for enabling and disabling of the server
> for a pool
>
> Has anyone done this before?
>

The short version is F5 have an API call, but I'm not sure it's actually
usable. The good news is you have other options.

The v11 API [1] was extended to support this functionality, but the module
was written specifically for v10 [2]. I don't know the f5-icontrol 10.2
gem compatibility with v11 API, and F5 haven't released v11.2.1 gem yet
[3]. I think setting a poolmember connection limit would simulate the
behavior. The other solution is setup monitoring to watch a service
availability and drain stop (not the actual service but a service
availability indicator). This is actually quite helpful as it gives the
server admin the ability to start maintenance, monitor user traffic drain,
all without any load balancer changes [4].

If you are on v11 and willing to work with the provider, you can look at
updating this section:
https://github.com/puppetlabs/puppetlabs-f5/blob/master/lib/puppet/provider/f5_pool/f5_pool.rb#L66-L74
https://github.com/puppetlabs/puppetlabs-f5/blob/master/lib/puppet/provider/f5_pool/f5_pool.rb#L123-L131

Change the WSDL to LocalLB.Pool, add enabled state property, and change to
the appropriate get_member_*, set_member_* methods.

HTH,

Nan

1.
https://devcentral.f5.com/wiki/iControl.GlobalLB__Pool__set_member_enabled_state.ashx
2. https://devcentral.f5.com/wiki/iControl.GlobalLB__PoolMember.ashx
3.
https://devcentral.f5.com/tech-tips/articles/getting-started-with-ruby-and-icontrol
4. https://devcentral.f5.com/community/group/aft/2161534/asg/50

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: New Type/Provider... How to handle cli input???

[fatmcgav]

Justin

Cheers for that. Will have a read and see what I can come up with :)

Cheers
Gav


On 7 February 2013 17:32, Justin Stoller  wrote:

> There's a completely undocumented (outside of the Pickaxe book) Ruby
> STDLIB module called 'expect' that you could use in 1.8.7, open up irb and
> give it a whirl. You can find other expect like gems (or at least crib how
> they're using the pty)[1]. I think you'll want something like expect4r[2]
> extended for NetApp.
>
>
> HTH,
> Justin
>
> 1. https://rubygems.org/search?utf8=%E2%9C%93&query=expect
> 2. https://github.com/jesnault/expect4r
>
>
> On Thu, Feb 7, 2013 at 7:18 AM, fatmcgav  wrote:
>
>> John
>>
>> Cheers for the response...
>>
>> Unfortunately SnapDrive is not my program - It's a NetApp program, so I'm
>> not going to be able to change it :(
>> Also doesn't look like it's designed to support command line args... :(
>> :(
>>
>> But in principle, it looks like it's possible, but a bit hacky...
>>
>> Cheers
>> Gavin
>>
>>
>> On 7 February 2013 14:42, jcbollinger  wrote:
>>
>>>
>>>
>>> On Thursday, February 7, 2013 5:12:41 AM UTC-6, Gavin Williams wrote:

 Morning all

 I'm looking at writing a set of types/providers to handle NetApp
 SnapDrive configuration and usage...

 There's quite a lot to SnapDrive, so initially, I'm just trying to get
 it to manage credentials.

 The challenge I can immediately see is that for me to set a credential,
 the command prompts for a password input twice... Example command run is:
 # snapdrive config set sd-act-star-db05 act-star-nactl01
 Password for sd-act-star-db05:
 Retype password:
 -957 Warning: Optionally, Please set -mgmtpath interface for
 act-star-nactl01 to be used as data interface i.e
 snapdrive config set -mgmtpath  act-star-nactl01

 Is it possible to cater for this in a provider?


>>>
>>> In principle, you can redirect appropriate canned responses into the
>>> command's standard input. I don't recall offhand whether Puppet's built-in
>>> executor facilities support that directly, but you can always wrap up
>>> something like that in a 'bash -c' command.
>>>
>>> It would be far better, however, if the configuration program were built
>>> to be scriptable (i.e. to not require interactive I/O).  For one thing,
>>> does your installer prompt for a password even when it is run by root
>>> (which is what the agent will do in the usual configuration)?  Does it
>>> support command-line options by which you can bypass any other Q&A?
>>>
>>>
>>> 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 post to this group, send email to puppet-users@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>  --
>> 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 post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: All Hosts Shown as Unresponsive. Worker Restart Fails. Clients Seem Happy?

[Mike Beauchamp]

I was able to fix this by going into the 
/etc/init.d/pe-puppet-dashboard-workers and editing the CPU line in the 
start section.

Previously it had {CPU:-2}, and I changed that to 4.   Instantly cleared 
the queue, and nodes showed up.  


On Tuesday, December 11, 2012 6:55:56 PM UTC-7, Dave Mankoff wrote:
>
> [On my dev server] For the past 3 days, my puppet master has shown all of 
> the hosts as unresponsive. However, when I log into one of the hosts and 
> run "puppet agent --test" everything seems to run without complaint. 
> Meanwhile the master shows an ever increasing number of pending tasks.
>
> When I try to restart the dashboard workers, I get the following:
>
> # /etc/init.d/pe-puppet-dashboard-workers restart
>  * Restarting PE Puppet Dashboard Workers
> ERROR: there is already one or more instance(s) of the program running
> ERROR: there is already one or more instance(s) of the program running
>  * PE Puppet Dashboard Worker (pid ) is not running
>   
> [fail]
>
> Rebooting the computer does not seem to help. For that matter, I think 
> this problem started after a recent system update and reboot. It is running 
> Ubuntu 12.04. I can not seem to find anything meaningful in the logs, 
> though perhaps I am looking in the wrong places. Any advice? Things worked 
> fine just a few days ago, and I have not touched 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Announce: Puppet 3.1.0 Available

[Jakov Sosic]

On 02/04/2013 09:07 PM, Matthaus Owens wrote:


* `create_resources` can now create virtual and exported resources (#15081)


*thumbs up* ! I can stop patching my master now :D


--
Jakov Sosic
www.srce.unizg.hr

--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Is there any other tool other than mcollective for orchestration..

[Derek Olsen]

Rajeev.

We run mcollective in a 100% Solaris shop.  We have not encountered
any Solaris specific issues.   Email me if you want the steps we use
to build the Solaris packages.

Thanks. Derek.


On Feb 7, 2:01 am, DreamBig  wrote:
> Thanks..
>
> On Feb 7, 2:31 pm, kavitha.c.k2...@gmail.com wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > There is a tools called "Ansible" , I think it works on solaris
>
> > Kavitha
>
> > On Thursday, February 7, 2013 2:28:32 PM UTC+5:30, Rajeev Iyer wrote:
>
> > > Hi,
>
> > > I guess mcollective supports only linux and similar OS. It does not
> > > have a package for Solaris or even a way to create a package from
> > > standard tar file. Can someone suggest any other tool?
>
> > > Regards,
> > > Rajeev

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Unable to send puppet reports to foreman

[Jagga Soorma]

Hi Guys,

I am a new puppet user and trying to see the different options for 
reporting.  I was able to setup and use puppet-dashboard just fine but 
can't seem to now get reports sent to foreman.  Here is what my setup looks 
like:

puppet server: ssfpuppetd01
foreman server: ssftmand01

I have copied foreman-report.rb to the 
/usr/lib/ruby/site_ruby/1.8/puppet/reports directory on my puppet server 
ssfpuppetd01.  The only thing that I changed in the foreman-report.rb file 
is the url:

$foreman_url='http://ssftmand01:3000'

Here is my puppet.conf on my puppet server:

[main]
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl

[agent]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig

[master]
reports = log, foreman

On my foreman server ssftmand01 I installed foreman and mysql db.  I have 
updated the /etc/foreman/settings.yaml and /etc/foreman/database.yaml 
files.  Here is my settings.yaml file:

:unattended: false
:login: false
:require_ssl: false
:locations_enabled: false
:organizations_enabled: false
:support_jsonp: false
:puppet_server: ssfpuppetd01
:email_reply_address: foreman-nore...@gene.com

I have started the foreman services on ssftmand01 but it has not puppet 
services running.  Not sure if that is also needed.  With this setup I 
still can't seem to get any reports in foreman.  I am pretty sure that I am 
missing something here and would really appreciate some help to get this to 
work.  I want to use foreman just as a reporting tool for puppet and would 
not like to use the provisioning options.

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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Unable to send puppet reports to foreman

[Jagga Soorma]

Hi Guys,

I am a new puppet user and trying to see the different options for 
reporting.  I was able to setup and use puppet-dashboard just fine but 
can't seem to now get reports sent to foreman.  Here is what my setup looks 
like:

puppet server: ssfpuppetd01
foreman server: ssftmand01

I have copied foreman-report.rb to the /usr/lib/ruby/site_ruby/1.8/
puppet/reports directory on my puppet server ssfpuppetd01.  The only thing 
that I changed in the foreman-report.rb file is the url:

$foreman_url='http://ssftmand01:3000'

Here is my puppet.conf on my puppet server:

[main]
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl

[agent]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig

[master]
reports = log, foreman

On my foreman server ssftmand01 I installed foreman and mysql db.  I have 
updated the /etc/foreman/settings.yaml and /etc/foreman/database.yaml 
files.  Here is my settings.yaml file:

:unattended: false
:login: false
:require_ssl: false
:locations_enabled: false
:organizations_enabled: false
:support_jsonp: false
:puppet_server: ssfpuppetd01
:email_reply_address: foreman-nore...@xyz.com 

I have started the foreman services on ssftmand01 but it has not puppet 
services running.  Not sure if that is also needed.  With this setup I 
still can't seem to get any reports in foreman.  I am pretty sure that I am 
missing something here and would really appreciate some help to get this to 
work.  I want to use foreman just as a reporting tool for puppet and would 
not like to use the provisioning options.

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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] I can't get a custom fact to work in Windows

[Dan McManus]

Hello all!

I am using open source puppet 3.0.1 on both the client and master. The 
issue I am having is that I cannot get a simple custom fact to be 
recognized in my manifest. Hopefully I am missing something. 

I am trying to have a custom fact that will tell me whether the nsclient++ 
directory exists or not.
Here's the custom fact, which is located at 
/etc/puppet/environments/windows/modules/nscp-test/lib/facter

Facter.add(:nsclient) do
setcode do
if File.exists?("c:/program files/nsclient++")
  puts ''nsclient installed'
else
  puts 'no such directory'
end
end
end


my init.pp is dead simple:

class nscp-test {
notify{$nsclient :}
}


Here's what happens when I run puppet agent --test on the client (windows 
2003):

C:\Documents and Settings\All Users\Application 
Data\PuppetLabs\puppet\var\lib\facter>puppet agent --test
Info: Retrieving plugin
Info: Loading facts in C:/Documents and Settings/All Users/Application 
Data/PuppetLabs/puppet/var/lib/facter/nsclient.rb
no such directory
no such directory
Info: Caching catalog for 
Info: Applying configuration version '1360274145'
Notice: undef
Notice: /Stage[main]/Nscp-test/Notify[undef]/message: defined 'message' as 
'undef'
Notice: Finished catalog run in 0.42 seconds


from the command line,  facter --puppet nsclient works just fine.

So am I missing something dead simple, or what? This is my first time doing 
custom facts.

Thanks,

Dan

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] available built-in variables

[roadtest]

This is very useful! Thanks for sharing!

On Friday, June 24, 2011 3:03:34 AM UTC-4, Nan Liu wrote:
>
> On Thu, Jun 23, 2011 at 7:46 AM, Patrick > 
> wrote:
> > Is there anywhere that lists the available built-in variables aside
> > from facter and 
> http://docs.puppetlabs.com/guides/faq.html#are-there-variables-available-other-than-those-provided-by-facter
> > ?
>
> Pretty sure that's it. You can dump all variables in scope via:
> notice(inline_template("<%= scope.to_hash %>"))
>
> This isn't perfect, but should give you the subset: (since facter
> value such as uptime changes, and in agent/master mode this is totally
> wrong unless it's on the same system)
> notice(inline_template("<%= (scope.to_hash.to_a -
> Facter.to_hash.to_a).to_yaml %>")
>
> This obviously will be different if the notice is in a module, a
> class, a define, $caller_module, $module_name would only be present if
> the notice is in the appropriate location.
>
> > I'm referring to variables like $title and $name, which are mentioned
> > by 
> http://docs.puppetlabs.com/guides/language_guide.html#defined-resource-types
> ,
> > but are there any others?
> >
>
> Anyhow this is what I got back using puppet apply (trimming some extras):
>
>   - - clientversion
> - 2.6.4 (Puppet Enterprise 1.0)
>   - - clientcert
> - pe-master.localdomain
>   - - title
> - main
>   - - name
> - main
>   - - environment
> - production
>
> Thanks,
>
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] I can't get a custom fact to work in Windows

[Justin Stoller]

On Thu, Feb 7, 2013 at 2:04 PM, Dan McManus  wrote:

> Hello all!
>
> I am using open source puppet 3.0.1 on both the client and master. The
> issue I am having is that I cannot get a simple custom fact to be
> recognized in my manifest. Hopefully I am missing something.
>
> I am trying to have a custom fact that will tell me whether the nsclient++
> directory exists or not.
> Here's the custom fact, which is located at
> /etc/puppet/environments/windows/modules/nscp-test/lib/facter
>
> Facter.add(:nsclient) do
> setcode do
> if File.exists?("c:/program files/nsclient++")
>   puts ''nsclient installed'
> else
>   puts 'no such directory'
>
>
`puts` sends the string to stdout, you want to return the string. Ruby will
implicitly return the last statement in a block. Which is how the examples
in http://docs.puppetlabs.com/guides/custom_facts.html  works.

HTH,
Justin

end
> end
> end
>
>
> my init.pp is dead simple:
>
> class nscp-test {
> notify{$nsclient :}
> }
>
>
> Here's what happens when I run puppet agent --test on the client (windows
> 2003):
>
> C:\Documents and Settings\All Users\Application
> Data\PuppetLabs\puppet\var\lib\facter>puppet agent --test
> Info: Retrieving plugin
> Info: Loading facts in C:/Documents and Settings/All Users/Application
> Data/PuppetLabs/puppet/var/lib/facter/nsclient.rb
> no such directory
> no such directory
> Info: Caching catalog for 
> Info: Applying configuration version '1360274145'
> Notice: undef
> Notice: /Stage[main]/Nscp-test/Notify[undef]/message: defined 'message' as
> 'undef'
> Notice: Finished catalog run in 0.42 seconds
>
>
> from the command line,  facter --puppet nsclient works just fine.
>
> So am I missing something dead simple, or what? This is my first time
> doing custom facts.
>
> Thanks,
>
> Dan
>
>  --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] I can't get a custom fact to work in Windows

[Dan McManus]

Hah, yet, just removing the "puts" worked. Many thanks.

On Thu, Feb 7, 2013 at 3:28 PM, Justin Stoller wrote:

>
>
>
> On Thu, Feb 7, 2013 at 2:04 PM, Dan McManus  wrote:
>
>> Hello all!
>>
>> I am using open source puppet 3.0.1 on both the client and master. The
>> issue I am having is that I cannot get a simple custom fact to be
>> recognized in my manifest. Hopefully I am missing something.
>>
>> I am trying to have a custom fact that will tell me whether the
>> nsclient++ directory exists or not.
>> Here's the custom fact, which is located at
>> /etc/puppet/environments/windows/modules/nscp-test/lib/facter
>>
>> Facter.add(:nsclient) do
>> setcode do
>>  if File.exists?("c:/program files/nsclient++")
>>   puts ''nsclient installed'
>>  else
>>   puts 'no such directory'
>>
>>
> `puts` sends the string to stdout, you want to return the string. Ruby
> will implicitly return the last statement in a block. Which is how the
> examples in http://docs.puppetlabs.com/guides/custom_facts.html  works.
>
> HTH,
> Justin
>
>  end
>> end
>> end
>>
>>
>> my init.pp is dead simple:
>>
>> class nscp-test {
>> notify{$nsclient :}
>> }
>>
>>
>> Here's what happens when I run puppet agent --test on the client (windows
>> 2003):
>>
>> C:\Documents and Settings\All Users\Application
>> Data\PuppetLabs\puppet\var\lib\facter>puppet agent --test
>> Info: Retrieving plugin
>> Info: Loading facts in C:/Documents and Settings/All Users/Application
>> Data/PuppetLabs/puppet/var/lib/facter/nsclient.rb
>> no such directory
>> no such directory
>> Info: Caching catalog for 
>> Info: Applying configuration version '1360274145'
>> Notice: undef
>> Notice: /Stage[main]/Nscp-test/Notify[undef]/message: defined 'message'
>> as 'undef'
>> Notice: Finished catalog run in 0.42 seconds
>>
>>
>> from the command line,  facter --puppet nsclient works just fine.
>>
>> So am I missing something dead simple, or what? This is my first time
>> doing custom facts.
>>
>> Thanks,
>>
>> Dan
>>
>>  --
>> 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 post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Applying a resource only if not within a schedule

[ad]

I have a custom resource type that upgrades a MSI and kicks off a reboot. 
It uses a schedule parameter (configurable through an  ENC) so we can 
control when the node is allowed to reboot. I'd like to add a notify (or 
call warn()) if not within the schedule, e.g. "Skipping ensure version of 
MSI x, not within allowed schedule".

Any easy way to do this? If not any tips on getting started with a custom 
function are appreciated.

Adam

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] I can't get a custom fact to work in Windows

[ad]

Note that you can also use Puppet.notice to help debug and such. 

Adam

On Thursday, February 7, 2013 4:39:42 PM UTC-6, Dan McManus wrote:
>
> Hah, yet, just removing the "puts" worked. Many thanks.
>
> On Thu, Feb 7, 2013 at 3:28 PM, Justin Stoller 
> 
> > wrote:
>
>>
>>
>>
>> On Thu, Feb 7, 2013 at 2:04 PM, Dan McManus 
>> > wrote:
>>
>>> Hello all!
>>>
>>> I am using open source puppet 3.0.1 on both the client and master. The 
>>> issue I am having is that I cannot get a simple custom fact to be 
>>> recognized in my manifest. Hopefully I am missing something. 
>>>
>>> I am trying to have a custom fact that will tell me whether the 
>>> nsclient++ directory exists or not.
>>> Here's the custom fact, which is located at 
>>> /etc/puppet/environments/windows/modules/nscp-test/lib/facter
>>>
>>> Facter.add(:nsclient) do
>>> setcode do
>>>  if File.exists?("c:/program files/nsclient++")
>>>   puts ''nsclient installed'
>>>  else
>>>   puts 'no such directory'
>>>
>>>
>> `puts` sends the string to stdout, you want to return the string. Ruby 
>> will implicitly return the last statement in a block. Which is how the 
>> examples in http://docs.puppetlabs.com/guides/custom_facts.html  works.
>>
>> HTH,
>> Justin
>>
>>  end
>>> end
>>> end
>>>
>>>
>>> my init.pp is dead simple:
>>>
>>> class nscp-test {
>>> notify{$nsclient :}
>>> }
>>>
>>>
>>> Here's what happens when I run puppet agent --test on the client 
>>> (windows 2003):
>>>
>>> C:\Documents and Settings\All Users\Application 
>>> Data\PuppetLabs\puppet\var\lib\facter>puppet agent --test
>>> Info: Retrieving plugin
>>> Info: Loading facts in C:/Documents and Settings/All Users/Application 
>>> Data/PuppetLabs/puppet/var/lib/facter/nsclient.rb
>>> no such directory
>>> no such directory
>>> Info: Caching catalog for 
>>> Info: Applying configuration version '1360274145'
>>> Notice: undef
>>> Notice: /Stage[main]/Nscp-test/Notify[undef]/message: defined 'message' 
>>> as 'undef'
>>> Notice: Finished catalog run in 0.42 seconds
>>>
>>>
>>> from the command line,  facter --puppet nsclient works just fine.
>>>
>>> So am I missing something dead simple, or what? This is my first time 
>>> doing custom facts.
>>>
>>> Thanks,
>>>
>>> Dan
>>>
>>>  -- 
>>> 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 post to this group, send email to puppet...@googlegroups.com
>>> .
>>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>
>>  -- 
>> 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 post to this group, send email to puppet...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Unable to send puppet reports to foreman

[Jagga Soorma]

Nevermind, got it to work.  Looks like I messed up the renaming of that 
file.  I moved it to foreman.rb instead of foreman-report.rb and seems to 
be working now.  Will try some other things and see how this works.

Thanks.

On Thursday, February 7, 2013 1:52:18 PM UTC-8, Jagga Soorma wrote:
>
> Hi Guys,
>
> I am a new puppet user and trying to see the different options for 
> reporting.  I was able to setup and use puppet-dashboard just fine but 
> can't seem to now get reports sent to foreman.  Here is what my setup looks 
> like:
>
> puppet server: ssfpuppetd01
> foreman server: ssftmand01
>
> I have copied foreman-report.rb to the /usr/lib/ruby/site_ruby/1.8/
> puppet/reports directory on my puppet server ssfpuppetd01.  The only thing 
> that I changed in the foreman-report.rb file is the url:
>
> $foreman_url='http://ssftmand01:3000'
>
> Here is my puppet.conf on my puppet server:
>
> [main]
> logdir = /var/log/puppet
> rundir = /var/run/puppet
> ssldir = $vardir/ssl
>
> [agent]
> classfile = $vardir/classes.txt
> localconfig = $vardir/localconfig
>
> [master]
> reports = log, foreman
>
> On my foreman server ssftmand01 I installed foreman and mysql db.  I have 
> updated the /etc/foreman/settings.yaml and /etc/foreman/database.yaml 
> files.  Here is my settings.yaml file:
>
> :unattended: false
> :login: false
> :require_ssl: false
> :locations_enabled: false
> :organizations_enabled: false
> :support_jsonp: false
> :puppet_server: ssfpuppetd01
> :email_reply_address: foreman-nore...@xyz.com 
>
> I have started the foreman services on ssftmand01 but it has not puppet 
> services running.  Not sure if that is also needed.  With this setup I 
> still can't seem to get any reports in foreman.  I am pretty sure that I am 
> missing something here and would really appreciate some help to get this to 
> work.  I want to use foreman just as a reporting tool for puppet and would 
> not like to use the provisioning options.
>
> 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] RFC: Default File Permissions

[Josh Cooper]

Recently, the issue of copying file modes from remote sources was discussed 
on the puppet-users mailing list[1], although it equally applies to owner 
and group.

One issue is what permissions to apply to newly created files when none are 
specified? Historically, Puppet has always copied the permissions from the 
file source to the newly created one. However, this causes problems on 
Windows[2] agents due to the way that Puppet emulates POSIX permissions. We 
break NTFS access control inheritance to ensure the effective permissions 
are not greater than what Puppet has granted. It also causes problems on 
*nix agents, when the files' source is remote and uid/gids are not 
synchronized.

A second, but related issue, is that Puppet applies the same 
copy-permissions logic to files that already exist. This goes against what 
jcbollinger said, "unmanaged resources and resource properties should not 
be modified by Puppet"[3], and what Nigel said, "A core principle of Puppet 
is that you can choose to only manage the attributes of a resource that you 
care about, and can leave the rest unmanaged."[4] However, this "bug" has 
been around so long, at least 0.24.8, that we can't change behaviors in a 
minor release.[5]

Patrick and I talked about this and would like to propose adding a file 
parameter, something like `use_source_permissions`. If true and permissions 
are unspecified, Puppet would continue copying source permissions as it 
does today, for both newly created and existing files. This would be the 
default.

If false and permission are unspecified, Puppet would never copy them from 
the source. Instead the permission defaults for newly created files would 
be based on the user that Puppet is running as. And the permissions for 
existing files would be unmodified.

Doing so would provide a mechanism for resolving both #5240 and #18931.

Comments and feedback welcome.

Josh

[1] 
https://groups.google.com/forum/#!msg/puppet-users/CI7pEUHknm4/x-hCGJn6Ms8J
[2] https://projects.puppetlabs.com/issues/18931
[3] https://groups.google.com/d/msg/puppet-users/CI7pEUHknm4/VtCl9YmeIS0J
[4] http://projects.puppetlabs.com/issues/5240#note-16
[5] https://projects.puppetlabs.com/issues/5240

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet master processing agent report time is very long, how to optimization

[serwei2014]

The puppet conf:
master:
reports = log,foreman 
 
agent:
 report = true
 
So  The foreman is  the bottleneck?  How to optimise?
 

On Thursday, February 7, 2013 10:59:02 AM UTC, Dominic Cleal wrote:

> On 07/02/13 08:30, serwe...@gmail.com  wrote: 
> > There is a puppet cluster, composed by nginx,passenger,puppet. The 
> number of qps is 1000 currently, 
> > and the processing speed of the whole cluster is pretty good,the average 
> processing time for the request is 0.25 seconds. 
> >  But it is a little slow from client report, a lot of processing time is 
> tens of seconds.such 
> > as nginx log: 
> >   
> > 192.168.0.2 puppet  - [07/Feb/2013:15:45:44 +0800] "PUT 
> > /production/report/123.test.test.cn HTTP/1.1" 200 24 "-" "-" "-" 95.690 
> > 192.168.12.12:8140 200 _95.876_ 
>
> Are you using reports for anything? 
>
> By default Puppet enables and stores them.  You can disable storage on 
> your master with: 
>
> [master] 
> reports = 
>
> Or you can disable sending them on your agents with: 
>
> [agent] 
> report = false 
>
> If you're using disk stored reports for something useful, then look at 
> PuppetDB 1.1 instead, or improve your storage.  If you're using another 
> report processor (e.g. Foreman), then you need to optimise that. 
>
> -- 
> Dominic Cleal 
> Red Hat Engineering 
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.