[Puppet Users] Re: Can Puppet interact with perl script user input fields?

[Jon Skarpeteig]

The script is several thousand lines of code. Definitely not easier
than Guzman Braso's suggestion :-)

Although I'm surprised that Puppet doesn't have any supported way of
shell interaction with scripts?

On Oct 5, 4:01 am, Peter Brown  wrote:
> It's probably easier in the long run to work out what that script does
> and replicate those settings in your samba puppet class.
>
> On 4 October 2012 19:34, Jon Skarpeteig  wrote:
>
>
>
>
>
>
>
> > I'm trying to automate deployment of centrify-samba, which has a
> > adbindproxy.pl setup script attached. This script expects user input
> > (where 9 out of 10 options can be defaulted). Is there any way for
> > Puppet to preconfigure the inputs for this scripts, and mimic user
> > behavior by supplying this information?
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Custom ruby gem continuously updates

[Peter Brown]

Awesome!

Happy to help.

On 5 October 2012 13:03, jmadtech  wrote:
> Pure genius!  That did it Pete.
>
> Thanks so much!
>
>
> On Monday, October 1, 2012 10:03:31 PM UTC-4, Pete wrote:
>>
>> Considering the source you have seems to have a version in it already
>> have you tried it without the version number in the name?
>> as in
>> package { "sapnwrfc":
>> ensure => 'installed',
>> provider => 'gem',
>> source => "/export/admin_scripts/sapnwrfc-0.24",
>> }
>>
>> On 2 October 2012 06:51, jmadtech  wrote:
>> > The gem is there and installed.  I didn't install it by hand, so it did
>> > get
>> > installed by puppet at some point.  I'm assuming it's because the gem
>> > source
>> > file is local so it has no way to verify the file version versus the
>> > installed version.
>> >
>> >
>> > On Monday, October 1, 2012 4:42:46 PM UTC-4, Pete wrote:
>> >>
>> >> Does it actually install?
>> >> I find if package resources try to install on each run it means they
>> >> don't get installed correctly.
>> >>
>> >> On 28 September 2012 13:22, jmadtech 
>> >> wrote:
>> >> > Hey all,
>> >> >
>> >> > I'm not sure if there's a real issue or if I'm doing something
>> >> > incorrectly.
>> >> >
>> >> > I have a custom compiled gem that I'm installing via:
>> >> >
>> >> > package { "sapnwrfc-0.24":
>> >> > ensure => 'installed',
>> >> > provider => 'gem',
>> >> > source => "/export/admin_scripts/sapnwrfc-0.24",
>> >> > }
>> >> >
>> >> > On first run, it installs correctly.  A 'gem list' shows it as:
>> >> >
>> >> > sapnwrfc (0.24 x86_64-linux)
>> >> >
>> >> > However, every subsequent checkin with the master results in:
>> >> >
>> >> > Thu Sep 27 20:07:34 -0700 2012 Puppet (notice): Starting Puppet
>> >> > client
>> >> > version 2.7.19
>> >> > Thu Sep 27 20:07:49 -0700 2012
>> >> > /Stage[main]/my_app/Package[sapnwrfc-0.24]/ensure (notice): created
>> >> > Thu Sep 27 20:07:53 -0700 2012 Puppet (notice): Finished catalog run
>> >> > in
>> >> > 12.90 seconds
>> >> >
>> >> > I've tried changing the ensure from 'installed' to '0.24', '0.24
>> >> > x86_64-linux', etc. to no avail... it keeps registering a change.
>> >> >
>> >> > what am I doing wrong?
>> >> >
>> >> > Thanks in advance!
>> >> >
>> >> > --
>> >> > You received this message because you are subscribed to the Google
>> >> > Groups
>> >> > "Puppet Users" group.
>> >> > To view this discussion on the web visit
>> >> > https://groups.google.com/d/msg/puppet-users/-/I_o9G1NySfUJ.
>> >> > To post to this group, send email to puppet...@googlegroups.com.
>> >> > To unsubscribe from this group, send email to
>> >> > puppet-users...@googlegroups.com.
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/puppet-users?hl=en.
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Puppet Users" group.
>> > To view this discussion on the web visit
>> > https://groups.google.com/d/msg/puppet-users/-/2-aZE0n23ewJ.
>> >
>> > To post to this group, send email to puppet...@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > puppet-users...@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/puppet-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/jqqn9qug6voJ.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Custom ruby gem continuously updates

[jmadtech]

Pure genius!  That did it Pete.

Thanks so much!

On Monday, October 1, 2012 10:03:31 PM UTC-4, Pete wrote:
>
> Considering the source you have seems to have a version in it already 
> have you tried it without the version number in the name? 
> as in 
> package { "sapnwrfc": 
> ensure => 'installed', 
> provider => 'gem', 
> source => "/export/admin_scripts/sapnwrfc-0.24", 
> } 
>
> On 2 October 2012 06:51, jmadtech > 
> wrote: 
> > The gem is there and installed.  I didn't install it by hand, so it did 
> get 
> > installed by puppet at some point.  I'm assuming it's because the gem 
> source 
> > file is local so it has no way to verify the file version versus the 
> > installed version. 
> > 
> > 
> > On Monday, October 1, 2012 4:42:46 PM UTC-4, Pete wrote: 
> >> 
> >> Does it actually install? 
> >> I find if package resources try to install on each run it means they 
> >> don't get installed correctly. 
> >> 
> >> On 28 September 2012 13:22, jmadtech  
> wrote: 
> >> > Hey all, 
> >> > 
> >> > I'm not sure if there's a real issue or if I'm doing something 
> >> > incorrectly. 
> >> > 
> >> > I have a custom compiled gem that I'm installing via: 
> >> > 
> >> > package { "sapnwrfc-0.24": 
> >> > ensure => 'installed', 
> >> > provider => 'gem', 
> >> > source => "/export/admin_scripts/sapnwrfc-0.24", 
> >> > } 
> >> > 
> >> > On first run, it installs correctly.  A 'gem list' shows it as: 
> >> > 
> >> > sapnwrfc (0.24 x86_64-linux) 
> >> > 
> >> > However, every subsequent checkin with the master results in: 
> >> > 
> >> > Thu Sep 27 20:07:34 -0700 2012 Puppet (notice): Starting Puppet 
> client 
> >> > version 2.7.19 
> >> > Thu Sep 27 20:07:49 -0700 2012 
> >> > /Stage[main]/my_app/Package[sapnwrfc-0.24]/ensure (notice): created 
> >> > Thu Sep 27 20:07:53 -0700 2012 Puppet (notice): Finished catalog run 
> in 
> >> > 12.90 seconds 
> >> > 
> >> > I've tried changing the ensure from 'installed' to '0.24', '0.24 
> >> > x86_64-linux', etc. to no avail... it keeps registering a change. 
> >> > 
> >> > what am I doing wrong? 
> >> > 
> >> > Thanks in advance! 
> >> > 
> >> > -- 
> >> > You received this message because you are subscribed to the Google 
> >> > Groups 
> >> > "Puppet Users" group. 
> >> > To view this discussion on the web visit 
> >> > https://groups.google.com/d/msg/puppet-users/-/I_o9G1NySfUJ. 
> >> > To post to this group, send email to puppet...@googlegroups.com. 
> >> > To unsubscribe from this group, send email to 
> >> > puppet-users...@googlegroups.com. 
> >> > For more options, visit this group at 
> >> > http://groups.google.com/group/puppet-users?hl=en. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Puppet Users" group. 
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msg/puppet-users/-/2-aZE0n23ewJ. 
> > 
> > To post to this group, send email to 
> > puppet...@googlegroups.com. 
>
> > To unsubscribe from this group, send email to 
> > puppet-users...@googlegroups.com . 
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/jqqn9qug6voJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Can Puppet interact with perl script user input fields?

[Peter Brown]

It's probably easier in the long run to work out what that script does
and replicate those settings in your samba puppet class.

On 4 October 2012 19:34, Jon Skarpeteig  wrote:
> I'm trying to automate deployment of centrify-samba, which has a
> adbindproxy.pl setup script attached. This script expects user input
> (where 9 out of 10 options can be defaulted). Is there any way for
> Puppet to preconfigure the inputs for this scripts, and mimic user
> behavior by supplying this information?
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Testing exported resources

[Peter Brown]

I had this issue a few years ago.
You can actually define a host_group in nagios without it having any
hosts assigned to it.
I set the hostgroup in the host definition instead of the hostgroup
definition to get around it.

On 4 October 2012 01:01, Pete  wrote:
> Hello,
>
> Is there any way to test if a resources has been exported (without realising
> it)?  The reason being - I don't want to realise a nagios_service that's
> associated with a nagios_hostgroup until at least one nagios_host belonging
> to that hostgroup exists (otherwise nagios will refuse to start).
>
> Any ideas?
>
> Pete
>
> 
> This email was sent by a company owned by Pearson plc, registered office at
> 80 Strand, London WC2R 0RL.  Registered in England and Wales with company
> number 53723.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/7g4gHwSXefQJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Attention Stockholm/Sweden puppet users

[Henrik Lindberg]

On October 24, James Turnbull from Puppetlabs is visiting Stockholm and 
there will be a meetup at Spotify's office - talks, and opportunity to 
network with fellow devops people.


Details posted here: http://www.meetup.com/DevOps-Stockholm/events/85307662/

Looking forward to seeing you there!
Regards
- henrik

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet warning error messages after upgrading to version 3

[Henrik Lindberg]

On 2012-03-10 20:29, Brent Clark wrote:

Good day

I seem to have a problem whereby, I get the following message when I do
a puppet run.

Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Could not intern from pson: source '"#http://projects.puppetlabs.com/issues/3160#note-7

I did make the mistake of first upgrading the client to version 3 on one
of my test hosts. But then after seeing the above message, I upgraded
the puppet master.
But the above error message is still present.

If someone could shed some light, it would gratefully be appreciated.

Kind regards
Brent Clark

A wild guess here - the client is in broken state. Did you try 
downgrading the client, make a run and then upgrade it.


What did you upgrade from?

Regards
- henrik

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Announce: Puppet Dashboard 1.2.12 Available

[Walter Heck - OlinData.com]

May I ask what the future plans are for Puppet Dashboard? Will there
be more feature development? I see that 1.2.0 came out August last
year. Together with the fact that it seems like new dashboard
development is focused on Puppet Enterprise Console, I'm wondering how
the Puppet Dashboard fits in the roadmap?
The github commit log doesn't show much feature development:
https://github.com/puppetlabs/puppet-dashboard/commits/master

Would be nice to know wether or not this can be recommended to users
looking for an Open Source dashboard.

kind regards,

Walter

On Fri, Oct 5, 2012 at 8:52 AM, Moses Mendoza  wrote:
> Puppet Dashboard 1.2.12 is a maintenance and bugfix release of Puppet 
> Dashboard.
>
> This release is available for download at:
> https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.12.tar.gz
>
> Debian packages are available at
> https://apt.puppetlabs.com
>
> RPM packages are available at
> https://yum.puppetlabs.com
>
> See the Verifying Puppet Download section at:
> http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet
>
> Please report feedback via the Puppet Labs Redmine site, using an
> affected version of 1.2.12:
> http://projects.puppetlabs.com/projects/dashboard
>
> Documentation is available at:
> http://docs.puppetlabs.com/dashboard/index.html
>
> =
> ## Puppet Dashboard 1.2.12 Highlights ##
> =
>
> (#16428) more accurate CONTRIBUTING.md
> This just updates the docs to indicate what I needed to do to get
> tests running.
>   Modulo any actual inaccuracies, I think having something here is
> better than nothing.
>   If there are simplifications or other fixes to make on top of this,
> those can come later.
>
> Specify the location of the favicon in error pages
> Prior to this commit, rendering an error page would itself result
> in an error if the
>   default favicon.ico file is protected by an authentication system
> that has a whitelist
>   of allowed routes.
>
> ==
> ## Puppet Dashboard 1.2.12 Changelog ##
> ==
>
> Dustin J. Mitchell (1):
>   6c0c8e0 (#16428) more accurate CONTRIBUTING.md
>
> Joshua Harlan Lifton (1):
>   9fea666 Specify the location of the favicon in error pages
>
> Matthaus Litteken (2):
>   5ac77d0 Update default cows and mocks
>   8759c5c Updating CHANGELOG for Puppet Dashboard 1.2.12-rc1
>
> Moses Mendoza (1):
>   83e926b fail better in package repo rake tasks
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
Walter Heck
CEO and Founder @ OlinData (http://olindata.com)
Puppet training and consulting
--
Follow @olindata on Twitter and/or 'Like' our Facebook page at
http://www.facebook.com/olindata

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Announce: Puppet Dashboard 1.2.12 Available

[Moses Mendoza]

Puppet Dashboard 1.2.12 is a maintenance and bugfix release of Puppet Dashboard.

This release is available for download at:
https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.12.tar.gz

Debian packages are available at
https://apt.puppetlabs.com

RPM packages are available at
https://yum.puppetlabs.com

See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.2.12:
http://projects.puppetlabs.com/projects/dashboard

Documentation is available at:
http://docs.puppetlabs.com/dashboard/index.html

=
## Puppet Dashboard 1.2.12 Highlights ##
=

(#16428) more accurate CONTRIBUTING.md
This just updates the docs to indicate what I needed to do to get
tests running.
  Modulo any actual inaccuracies, I think having something here is
better than nothing.
  If there are simplifications or other fixes to make on top of this,
those can come later.

Specify the location of the favicon in error pages
Prior to this commit, rendering an error page would itself result
in an error if the
  default favicon.ico file is protected by an authentication system
that has a whitelist
  of allowed routes.

==
## Puppet Dashboard 1.2.12 Changelog ##
==

Dustin J. Mitchell (1):
  6c0c8e0 (#16428) more accurate CONTRIBUTING.md

Joshua Harlan Lifton (1):
  9fea666 Specify the location of the favicon in error pages

Matthaus Litteken (2):
  5ac77d0 Update default cows and mocks
  8759c5c Updating CHANGELOG for Puppet Dashboard 1.2.12-rc1

Moses Mendoza (1):
  83e926b fail better in package repo rake tasks

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Announce: Hiera 1.1.0 Available

[Moses Mendoza]

Hiera 1.1.0 is a release in the 1.x branch with bug fixes and features.

Downloads are available at:
 * Source: https://downloads.puppetlabs.com/hiera/hiera-1.1.0.tar.gz

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Rubygem available at http://rubygems.org/gems/hiera

Debs are available at https://apt.puppetlabs.com

Mac package is available at https://downloads.puppetlabs.com/mac/hiera-1.1.0.dmg

See the Verifying Puppet Download section at:
 
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.1.0:
 http://projects.puppetlabs.com/projects/hiera/

===
## Hiera 1.1.0 Highlights ##
===

(#16427) Fix inaccurate usage hint in help

Usage in help was provided as "Usage: hiera [options]", which is inaccurate.
This commit uses opts.banner in the option parser to override that, as well
as provide some context about the arguments.

 Add json backend to hiera.

This commit brings the json backend and corresponding spec test
from hiera-json
into hiera. The spec test has been updated to move some of its
requires into the
spec_helper in a previous commit. This commit also updates the
project_data.yaml
to add a json dependency to hiera to the gem, deb and rpm packages.

Edit example hiera.yaml to fix bogus variable and include default datadir

A Puppet scope has no $certname variable, and we don't do anything
to add one.
Instead, Puppet has the following two variables:

- $settings::certname - the puppet master's certname
- $clientcert - the agent node's certname

Of the two, we want $clientcert.

This commit also calls out the location of the default datadir.

Clarify help for some options

This commit clarifies the function of the -a and -h flags, and improves the
wording of the MCollective and inventory options.


===
## Hiera 1.1.0 Changelog ##
===

Andrew Parker (1):
  f0f89ca (Maint) Lenient checks for looked up data

Daniel Pittman (1):
  580d39e Fix expect/should for RSpec 3 compatibility

Matthaus Litteken (8):
  66fc90e Refactor specs, remove spec.opts
  d36e0f5 Add json backend to hiera.
  f3f4653 (maint) Fixup hiera.spec for el5 oddities, rpmlint issues
  a9aa024 (maint) Fixup json dependency for redhat
  114944d (maint) Config=>RbConfig in hiera.spec.erb
  5253f39 (maint) Remove CHANGELOG from Hiera
  fe5f8b9 Update default cows and mock targets
  db60ecc Update VERSION for Hiera 1.1.0-rc1

Mitchell Hashimoto (1):
  c895013 Additional logging when finding keys in the YAML backend

Moses Mendoza (3):
  f7334ba Fixup apple package plist for use with packaging repo
  3a37348 fail better in package repo rake tasks
  d1c175b Update debian packaging for ruby 1.9

Will Hopper (1):
  ff2bbc6 Update Debian packaging rake task to correctly create
the orig.tar.gz

nfagerlund (3):
  b4e6e2f Edit example hiera.yaml to fix bogus variable and
include default datadir
  c56ff30 (#16427) Fix inaccurate usage hint in help
  562a7cc Clarify help for some options

rahul (1):
  8e7c748 (packaging) provider IPS packaging tasks

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Hadoop format using puppet

[fsalum]

I did my hadoop manifest as below:

  exec { "Namenode - Format dfs.name.dir":
path=> '/usr/bin:/usr/sbin:/bin',
command => 'echo "Y" | hadoop namenode -format',
user=> 'hdfs',
unless  => "test -d $dfs_name_dir/image",
require => Exec['Namenode - Create dfs.name.dir'],
  }

Regards,
Felipe

On Wednesday, September 19, 2012 11:30:39 AM UTC-7, Bai Shen wrote:
>
> I'm using puppet to automate the creation and maintenance of my hadoop 
> cluster.  However, I'm not sure how to handle this next step.  In order for 
> the cluster to run, the namenode needs to be formatted.
>
> su hdfs -c "/usr/bin/hadoop namenode -format"
>
> I'm not sure what the best method to handle this is.  Do I just add an 
> exec command?  How do I make sure that it only gets run during the initial 
> setup?
>
> Thanks.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/4k7KjLhocQ0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Need help with dashboad configuration..

[fsalum]

I have configured Puppet Dashboard, Inventory Service and Reports correctly 
but I do agree the Dashboard/Inventory/Reports installation and 
configuration is very confuse on the site.

Any chance Puppetlabs will organize those docs and make they less confuse 
to follow ? :)

On Wednesday, October 3, 2012 4:10:20 AM UTC-7, Rajeev Iyer wrote:
>
> Hi,
>
>   I am new to this.
>
> Can someone lead me to a step by step configuration for dashboard. The 
> ones on the web is too confusing.
> Like, it says we need to have an entry for puppet-dashboard in 
> /etc/passwd. So how does that look like?
>
> Rajeev
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/6nnqRWuLVIcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet cron job class stamps file with date-time. How?

[Stefan Schulte]

In case of the cron type it is easy for puppet to savely add a header
because puppet knows the purpose of a cronfile and knows that # is
treated as a comment.

If you use the filetype puppet does not know what your file is for. If
you ship a *.tar.gz file you certainly don't want puppet to put a header
in front of it.

So to add a static header puppet has to know what kind of file you are
shipping and if adding a header is safe. In my opinion this is rather
complicated, e.g. a shellscript is a textfile but #!/bin/sh has to
remain the first line, so puppet now has to add the header after line 1.

Adding a date is a bit complicated because puppet has to strip the
header from the source and target file before calculating any checksums,
otherwise puppet would always treat the target out of sync.

While you may be able to implement that I never thought that the date in
the file was of any help. I'd just look at the mtime. This can change
because of two reasons:

a) puppet changed the file because the source file on the server
   changed. Now mtime is the time you want to have in the header
b) some user changed the targetfile. This should not last long
   because puppet will reset the file soon and I have case a) again

-Stefan

On Thu, Oct 04, 2012 at 03:56:06PM -0400, Christopher Wood wrote:
> You may as well port the code from the cron provider into your environment.
> 
> For the generic string I was thinking of something as simple as "Don't touch 
> this file."
> 
> On Thu, Oct 04, 2012 at 12:46:09PM -0700, Jo Rhett wrote:
> >I'm not sure it's that easy. The original question about how to include
> >the date would cause some issues.. If the hiera lookup generated the date
> >each time, the file would be different each time and be overwritten each
> >time, which is probably not desirableable especially if a notify or
> >subscribe caused a service to restart.
> >On Oct 4, 2012, at 12:19 PM, Christopher Wood wrote:
> > 
> >  In this case the text appears to be a hardcode in a couple of 
> > providers:
> > 
> >  $ grep -r managed\ manually `pwd`
> >  /usr/lib/ruby/1.8/puppet/provider/parsedfile.rb:# HEADER: by puppet.
> >   While it can still be managed manually, it
> >  /usr/lib/ruby/1.8/puppet/provider/cron/crontab.rb:# HEADER: While it 
> > can
> >  still be managed manually, it is definitely not recommended.
> > 
> >  But this sounds like a great string for an environment-wide variable
> >  (hiera lookup) that all your templates can use.
> > 
> >  On Thu, Oct 04, 2012 at 12:08:39PM -0700, Jo Rhett wrote:
> > 
> >  I would also like to know this. I keep hacking the same text into
> >our
> > 
> >  templates. If there is a tag we could put in a template to get this
> >output
> > 
> >  I'd like to know it.
> > 
> >  On Oct 1, 2012, at 12:05 PM, Brian Dunbar wrote:
> > 
> >New puppet user.  I see that the cron class creates a cronjob 
> > with
> >a
> > 
> >date-time in the header, which is cool.
> > 
> ># HEADER: This file was autogenerated at Mon Oct 01 11:43:25 
> > -0500
> >2012
> > 
> >by puppet.
> > 
> ># HEADER: While it can still be managed manually, it is 
> > definitely
> >not
> > 
> >recommended.
> > 
> >1. How does it do that? 
> > 
> >2. I'd like to be able to edit the text, customize it.
> > 
> >3. More particularly, how can I put a date/time stamp in other
> >managed
> > 
> >files?  
> > 
> >I tried to do so with a template but that was not working out so
> >well.
> > 
> >Regards,
> > 
> >~brian
> > 
> >--
> > 
> >You received this message because you are subscribed to the 
> > Google
> > 
> >Groups "Puppet Users" group.
> > 
> >To view this discussion on the web visit
> > 
> >
> > [1][1]https://groups.google.com/d/msg/puppet-users/-/Wsckx5euwRgJ.
> > 
> >To post to this group, send email to
> >[2][2]puppet-users@googlegroups.com.
> > 
> >To unsubscribe from this group, send email to
> > 
> >[3][3]puppet-users+unsubscr...@googlegroups.com.
> > 
> >For more options, visit this group at
> > 
> >[4][4]http://groups.google.com/group/puppet-users?hl=en.
> > 
> >  -- 
> > 
> >  Jo Rhett
> > 
> >  Net Consonance : net philanthropy to improve open source and
> >internet
> > 
> >  projects.
> > 
> >  --
> > 
> >  You received this message because you are subscribed to the Google
> >Groups
> > 
> >  "Puppet Users" group.
> > 
> >  To post to this group, send email to
> >[5]puppet-users@googlegroups.com.
> > 
> >  To unsubscribe from this group, send email to
> > 
> >  [6]puppet-users

Re: [Puppet Users] environment set by client issues on nodes running 3.0.0

[Matthew Nicholson]

https://projects.puppetlabs.com/issues/16789

On Thu, Oct 4, 2012 at 2:58 PM, Jeff McCune  wrote:
> On Thu, Oct 4, 2012 at 11:12 AM, Matthew Nicholson
>  wrote:
>> File a bug report ? or is this an already tracked issue?
>
> If you could file a bug report and then reply here with the ticket
> number, that will help tremendously.  In the meantime I'm going to
> start investigating and try to reproduce the issue here.
>
> Thanks for reporting this,
> -Jeff
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>



-- 
Matthew Nicholson

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: redmine verification emails not working?

[Matthew Nicholson]

Thanks!

On Thu, Oct 4, 2012 at 4:57 PM, Eric Sorenson
 wrote:
> Hi Matthew -- I manually activated the 'nichols2' account in redmine, and
> forwarded your mail to the ops team to see where the emails went.
>
>
> On Thursday, October 4, 2012 1:27:20 PM UTC-7, Matt wrote:
>>
>> been waiting (and checking spam filters) on 2 accounts i've tried to
>> create in redmine for opening an issue, but yet to see any
>> verification emails. thought I'd give you guys the heads up as I'm
>> sure the dev's don't register accounts too often!
>>
>> just eager to open the 3.0 environment issue I'm seeing.
>>
>> Thanks!
>>
>>
>> --
>> Matthew Nicholson
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/VjjucKlaiZ8J.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.



-- 
Matthew Nicholson

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: redmine verification emails not working?

[Eric Sorenson]

Hi Matthew -- I manually activated the 'nichols2' account in redmine, and 
forwarded your mail to the ops team to see where the emails went. 

On Thursday, October 4, 2012 1:27:20 PM UTC-7, Matt wrote:
>
> been waiting (and checking spam filters) on 2 accounts i've tried to 
> create in redmine for opening an issue, but yet to see any 
> verification emails. thought I'd give you guys the heads up as I'm 
> sure the dev's don't register accounts too often! 
>
> just eager to open the 3.0 environment issue I'm seeing. 
>
> Thanks! 
>
>
> -- 
> Matthew Nicholson 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/VjjucKlaiZ8J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

RE: [Puppet Users] Re: activerecord and puppet-3.0.0

[Jennings, Jared L CTR USAF AFMC 96 SK/CCI]

> I encountered this issue yesterday when trying to reproduce another
> issue. I discovered that you need to be using activerecord 3.0.11.
> Later versions don't seem to work (error with a "stack too deep") and
> earlier versions don't seem to work (error with "uninitialized
constant
> ActiveRecord").

About "stack too deep" with later activerecord versions:


-- Jared Jennings, RHCE, Network Admin, SURVICE Engineering Co.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Announce: Facter 1.6.13 Available

[Moses Mendoza]

Facter 1.6.13 is a maintenance release in the 1.6.x branch with bug fixes.

Downloads are available at:
 * Source: https://downloads.puppetlabs.com/facter/facter-1.6.13.tar.gz

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Rubygem available at http://rubygems.org/gems/facter

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/facter-1.6.13.dmg

See the Verifying Puppet Download section at:
 
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.6.13:
 http://projects.puppetlabs.com/projects/facter/

Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki



## Facter 1.6.13 Release Notes ##


(#1415) Added case for Linux/IB to get correct IB address or fail predictably.

Originally, facter displayed a truncated infiniband MAC
address.

Now, If the interface starts with ib, use one of two methods
to get the infiniband MAC address or fails with a MAC address
of all FF otherwise.

(#16005) Puppet agent generates ifconfig warnings on InfiniBand systems fix

Whenever ifconfig was called on systems with Ib interfaces, it
would echo direcly to STDERR.

This commit suppresses ifconfig STDERR messages.

Improve rubysitedir fact

With ruby-1.9.3 -- at least on Fedora 17 -- trawling through the library
paths looking for the directory does not work.  Using RbConfig seems
more reliable and much simpler.

(#5205) Update facter manpage

This commit doesn't handle the request in the ticket of
dynamically generated
manpage, but it does update the man page to have updated flags and help,
correct license, copyright holder and copyright year. It also
fills in the name
of the program for the manpage so that the header doesn't look quite so
mysterious.

=
## Facter 1.6.13 Changelog ##
=

Daniel Pittman (1):
  b5fe6d0 Update copyright years in LICENSE

Garrett Honeycutt (4):
  5f64f45 removes trailing whitespace
  561c156 fixes formatting bug in man page
  53b7ecc removes generator comments
  ce581f8 fixes spacing on puppet option to be in line

Matthaus Litteken (13):
  41fc7e0 (#5205) Update facter manpage
  eb87175 (maint) Replace deprecated Config with RbConfig in debian/rules
  8697472 Remove sbin references from install.rb
  efe976b Remove RbConfig=>Config monkey_patch
  008a8d7 Add --ruby flag to install.rb
  29af0cd Remove svn specific code from install.rb
  d008d35 (maint) Update debian/rules to use new --ruby flag
  43d3e68 Update default cows
  4cb1030 Remove asc file a source for RPM builds
  903b298 Spec file cleanup
  25cb69f Remove INSTALL from Facter
  cc2015d Remove CHANGELOG from Facter
  e81b3ab Updating FACTERVERSION for facter 1.6.13-rc1

Matthaus Owens (1):
  8083990 Update facter debian packaging for 1.9 support

Michael Renz (10):
  262ef6a (#1415) Added case for Linux/IB to get correct IB
address or fail predictably.
  240dfac (#1415) ifconfig should not run twice for Linux.
  d4d0b80 (#1415) Handles ruby hanging of File.read of /sys/class/ with cat.
  1c43b91 (#16005) Puppet agent generates ifconfig warnings on
InfiniBand systems fix
  6c8f5f5 (#1415) ip_spec.rb test added for linux_ifconfig_ib0
  1d82907 (#1415) added two methods and spec tests
  f0858de (#1415) ifconfig_interface should output its output
  d413e93 (#1415) fixed the regex map
  a81469e (#1415) ifconfig_interface change.
  593c1e2 (#16005) updated ipaddress6_spec.rb and
macaddress_spec.rb to reflect updated ifconfig STDERR redirect

Moses Mendoza (3):
  1b4226c Fixup apple package plist for use with packaging repo
  0b85564 (#16341) return epoch to 1.6.x branch
  0f15e41 fail better in package repo rake tasks

Todd Zullinger (1):
  caed72f Improve rubysitedir fact

rahul (3):
  b713596 (maint) add packaging artifacts
  bffa03a (packaging) add ips support
  7b51f4a (packaging) ips: add shipping and signing support

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] How to prevent puppet clients from updating to version 3?

[Jo Rhett]

On Oct 4, 2012, at 1:04 PM, llowder wrote:
> On Thursday, October 4, 2012 2:49:03 PM UTC-5, Jo wrote:
> On Oct 4, 2012, at 12:39 PM, Jeff McCune wrote:
>>> Either just use installed, or a specific version, and then you can upgrade
>>> when you are ready to.
>> 
>> Even if you use ensure => installed, newly provisioned nodes will get
>> the latest available version at the time Puppet first runs, which will
>> cause issues unless you're also running a compatible Puppet master.
> 
> 
> We have solved this here by only copying down the RPMs to a local repository 
> after they have been tested. We've had too many puppet and facter versions 
> cause major problems to take anything without a full testing cycle.
> 
> That said, it's a lot of work. I'd love to see the yum/etc resources updated 
> to allow for < and <= versions.
> 
> 
> Having that allowed as an option for all package providers would be nice.
> 
> You should open a ticket for that if you haven't already.
> 
> If you don't want to, let me know and I will open one.

There are a couple dozen open tickets regarding packages and repos to allow 
stuff like this. Probably more important would be to group all of those 
together and clean them up.

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] redmine verification emails not working?

[Matthew Nicholson]

been waiting (and checking spam filters) on 2 accounts i've tried to
create in redmine for opening an issue, but yet to see any
verification emails. thought I'd give you guys the heads up as I'm
sure the dev's don't register accounts too often!

just eager to open the 3.0 environment issue I'm seeing.

Thanks!


-- 
Matthew Nicholson

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: How to prevent puppet clients from updating to version 3?

[llowder]

On Thursday, October 4, 2012 2:49:03 PM UTC-5, Jo wrote:
>
> On Oct 4, 2012, at 12:39 PM, Jeff McCune wrote:
>
> Either just use installed, or a specific version, and then you can upgrade
>
> when you are ready to.
>
>
> Even if you use ensure => installed, newly provisioned nodes will get
> the latest available version at the time Puppet first runs, which will
> cause issues unless you're also running a compatible Puppet master.
>
>
> We have solved this here by only copying down the RPMs to a local 
> repository after they have been tested. We've had too many puppet and 
> facter versions cause major problems to take anything without a full 
> testing cycle.
>
> That said, it's a lot of work. I'd love to see the yum/etc resources 
> updated to allow for < and <= versions.
>
>
Having that allowed as an option for all package providers would be nice.

You should open a ticket for that if you haven't already.

If you don't want to, let me know and I will open one.
 

> -- 
> Jo Rhett
> Net Consonance : net philanthropy to improve open source and internet 
> projects.
>
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/KTaGJ1f9TZgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet doc no longer producing documentation

[Jeff McCune]

On Wed, Oct 3, 2012 at 6:31 AM, Hugh Cole-Baker  wrote:
> After upgrading to Puppet 3.0.0 it seems that puppet doc is no longer
> producing documentation from my modules / manifests.
> I have a setup with two environments in
> /etc/puppet/environments/[production, testing], and I'm running the
> following command to generate the docs:
>
> puppet doc --all --mode rdoc --environment production --outputdir doc
>
> After running this it creates the 'doc' directory but there are no files in
> it.
> The same command was working OK on 2.7.19.
>
> Has anything changed in the required format of doc comments in the
> manifests?

This is likely a bug.  Could you please file an issue at
http://projects.puppetlabs.com/projects/puppet describing the problem
and snippets of commands showing how to reproduce the issue?  If you
follow up to this conversation with the ticket number, I'll start
watching the ticket and work to reproduce the issue.  With some effort
we might be able to fix this for the 3.0.1 release.

Thanks,
-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet cron job class stamps file with date-time. How?

[Christopher Wood]

You may as well port the code from the cron provider into your environment.

For the generic string I was thinking of something as simple as "Don't touch 
this file."

On Thu, Oct 04, 2012 at 12:46:09PM -0700, Jo Rhett wrote:
>I'm not sure it's that easy. The original question about how to include
>the date would cause some issues.. If the hiera lookup generated the date
>each time, the file would be different each time and be overwritten each
>time, which is probably not desirableable especially if a notify or
>subscribe caused a service to restart.
>On Oct 4, 2012, at 12:19 PM, Christopher Wood wrote:
> 
>  In this case the text appears to be a hardcode in a couple of providers:
> 
>  $ grep -r managed\ manually `pwd`
>  /usr/lib/ruby/1.8/puppet/provider/parsedfile.rb:# HEADER: by puppet.
>   While it can still be managed manually, it
>  /usr/lib/ruby/1.8/puppet/provider/cron/crontab.rb:# HEADER: While it can
>  still be managed manually, it is definitely not recommended.
> 
>  But this sounds like a great string for an environment-wide variable
>  (hiera lookup) that all your templates can use.
> 
>  On Thu, Oct 04, 2012 at 12:08:39PM -0700, Jo Rhett wrote:
> 
>  I would also like to know this. I keep hacking the same text into
>our
> 
>  templates. If there is a tag we could put in a template to get this
>output
> 
>  I'd like to know it.
> 
>  On Oct 1, 2012, at 12:05 PM, Brian Dunbar wrote:
> 
>New puppet user.  I see that the cron class creates a cronjob with
>a
> 
>date-time in the header, which is cool.
> 
># HEADER: This file was autogenerated at Mon Oct 01 11:43:25 -0500
>2012
> 
>by puppet.
> 
># HEADER: While it can still be managed manually, it is definitely
>not
> 
>recommended.
> 
>1. How does it do that? 
> 
>2. I'd like to be able to edit the text, customize it.
> 
>3. More particularly, how can I put a date/time stamp in other
>managed
> 
>files?  
> 
>I tried to do so with a template but that was not working out so
>well.
> 
>Regards,
> 
>~brian
> 
>--
> 
>You received this message because you are subscribed to the Google
> 
>Groups "Puppet Users" group.
> 
>To view this discussion on the web visit
> 
>[1][1]https://groups.google.com/d/msg/puppet-users/-/Wsckx5euwRgJ.
> 
>To post to this group, send email to
>[2][2]puppet-users@googlegroups.com.
> 
>To unsubscribe from this group, send email to
> 
>[3][3]puppet-users+unsubscr...@googlegroups.com.
> 
>For more options, visit this group at
> 
>[4][4]http://groups.google.com/group/puppet-users?hl=en.
> 
>  -- 
> 
>  Jo Rhett
> 
>  Net Consonance : net philanthropy to improve open source and
>internet
> 
>  projects.
> 
>  --
> 
>  You received this message because you are subscribed to the Google
>Groups
> 
>  "Puppet Users" group.
> 
>  To post to this group, send email to
>[5]puppet-users@googlegroups.com.
> 
>  To unsubscribe from this group, send email to
> 
>  [6]puppet-users+unsubscr...@googlegroups.com.
> 
>  For more options, visit this group at
> 
>  [7]http://groups.google.com/group/puppet-users?hl=en.
> 
>References
> 
>  Visible links
> 
>  1. [8]https://groups.google.com/d/msg/puppet-users/-/Wsckx5euwRgJ
> 
>  2. [9]mailto:puppet-users@googlegroups.com
> 
>  3. [10]mailto:puppet-users+unsubscr...@googlegroups.com
> 
>  4. [11]http://groups.google.com/group/puppet-users?hl=en
> 
>  --
>  You received this message because you are subscribed to the Google
>  Groups "Puppet Users" group.
>  To post to this group, send email to [12]puppet-users@googlegroups.com.
>  To unsubscribe from this group, send email to
>  [13]puppet-users+unsubscr...@googlegroups.com.
>  For more options, visit this group at
>  [14]http://groups.google.com/group/puppet-users?hl=en.
> 
>-- 
>Jo Rhett
>Net Consonance : net philanthropy to improve open source and internet
>projects.
> 
>--
>You received this message because you are subscribed to the Google Groups
>"Puppet Users" group.
>To post to this group, send email to puppet-users@googlegroups.com.
>To unsubscribe from this group, send email to
>puppet-users+unsubscr...@googlegroups.com.
>For more options, visit this group at
>http://groups.google.com/group/puppet-users?hl=en.
> 
> References
> 
>Visible links
>1. https://groups.google.com/d/msg/puppet-users/-/Wsckx5euwRgJ
>2. mailto:puppet-users@googlegroups.com
>3. mailt

[Puppet Users] Re: Puppet 3 docs are live

[Nick Fagerlund]

Ah, and the explicit --confdir is to accommodate a new behavior, too. Will 
update to be a little more concise and comprehensive.

On Thursday, October 4, 2012 2:26:37 AM UTC-7, Stefan Heijmans wrote:
>
>
> http://docs.puppetlabs.com/puppet/3/reference/release_notes.html#puppet-master-web-server-changes
> >>This needs to be changed to Puppet::Util::CommandLine
> but also the require seems to have changed 
> from require 'puppet/application/master'
> to   require 'puppet/util/command_line'
>  
> Op donderdag 4 oktober 2012 03:14:12 UTC+2 schreef Nick Fagerlund het 
> volgende:
>
>> Puppet 3 docs are now posted at 
>> http://docs.puppetlabs.com/puppet/3/reference/ . We apologize for the 
>> delay! This update adds release notes and a Puppet 3 language reference 
>> with all of the relevant updated. Next on deck is improved Hiera 
>> documentation. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/6KfAyJIcXZsJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: How to prevent puppet clients from updating to version 3?

[Jo Rhett]

On Oct 4, 2012, at 12:39 PM, Jeff McCune wrote:
>> Either just use installed, or a specific version, and then you can upgrade
>> when you are ready to.
> 
> Even if you use ensure => installed, newly provisioned nodes will get
> the latest available version at the time Puppet first runs, which will
> cause issues unless you're also running a compatible Puppet master.


We have solved this here by only copying down the RPMs to a local repository 
after they have been tested. We've had too many puppet and facter versions 
cause major problems to take anything without a full testing cycle.

That said, it's a lot of work. I'd love to see the yum/etc resources updated to 
allow for < and <= versions.

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet cron job class stamps file with date-time. How?

[Jo Rhett]

I'm not sure it's that easy. The original question about how to include the 
date would cause some issues.. If the hiera lookup generated the date each 
time, the file would be different each time and be overwritten each time, which 
is probably not desirableable especially if a notify or subscribe caused a 
service to restart.

On Oct 4, 2012, at 12:19 PM, Christopher Wood wrote:
> In this case the text appears to be a hardcode in a couple of providers:
> 
> $ grep -r managed\ manually `pwd`
> /usr/lib/ruby/1.8/puppet/provider/parsedfile.rb:# HEADER: by puppet.  While 
> it can still be managed manually, it
> /usr/lib/ruby/1.8/puppet/provider/cron/crontab.rb:# HEADER: While it can 
> still be managed manually, it is definitely not recommended.
> 
> But this sounds like a great string for an environment-wide variable (hiera 
> lookup) that all your templates can use.
> 
> On Thu, Oct 04, 2012 at 12:08:39PM -0700, Jo Rhett wrote:
>>   I would also like to know this. I keep hacking the same text into our
>>   templates. If there is a tag we could put in a template to get this output
>>   I'd like to know it.
>>   On Oct 1, 2012, at 12:05 PM, Brian Dunbar wrote:
>> 
>> New puppet user.  I see that the cron class creates a cronjob with a
>> date-time in the header, which is cool.
>> # HEADER: This file was autogenerated at Mon Oct 01 11:43:25 -0500 2012
>> by puppet.
>> # HEADER: While it can still be managed manually, it is definitely not
>> recommended.
>> 1. How does it do that? 
>> 2. I'd like to be able to edit the text, customize it.
>> 3. More particularly, how can I put a date/time stamp in other managed
>> files?  
>> I tried to do so with a template but that was not working out so well.
>> Regards,
>> ~brian
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Puppet Users" group.
>> To view this discussion on the web visit
>> [1]https://groups.google.com/d/msg/puppet-users/-/Wsckx5euwRgJ.
>> To post to this group, send email to [2]puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> [3]puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> [4]http://groups.google.com/group/puppet-users?hl=en.
>> 
>>   -- 
>>   Jo Rhett
>>   Net Consonance : net philanthropy to improve open source and internet
>>   projects.
>> 
>>   --
>>   You received this message because you are subscribed to the Google Groups
>>   "Puppet Users" group.
>>   To post to this group, send email to puppet-users@googlegroups.com.
>>   To unsubscribe from this group, send email to
>>   puppet-users+unsubscr...@googlegroups.com.
>>   For more options, visit this group at
>>   http://groups.google.com/group/puppet-users?hl=en.
>> 
>> References
>> 
>>   Visible links
>>   1. https://groups.google.com/d/msg/puppet-users/-/Wsckx5euwRgJ
>>   2. mailto:puppet-users@googlegroups.com
>>   3. mailto:puppet-users+unsubscr...@googlegroups.com
>>   4. http://groups.google.com/group/puppet-users?hl=en
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
> 

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet cron job class stamps file with date-time. How?

[Jo Rhett]

On Oct 4, 2012, at 12:17 PM, Stephen Gran wrote:
> Templates can take more than one source of data, so a trivial way to do this 
> is something like:
> 
> content => template('site/header.erb', $template, 'site/footer.erb'),


You know, the inconsistency between source=> and content=> caught me here. I 
thought that listing multiple templates used the first one found, like source. 
But checking the docs shows that you are right: these would be concatenated.

That said, it doesn't solve the original question about how to include the 
date. If the template generated the date each time, the file would be different 
each time and be overwritten each time, which is probably not desirableable 
especially if a notify or subscribe caused a service to restart.

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: How to prevent puppet clients from updating to version 3?

[Jeff McCune]

On Wed, Oct 3, 2012 at 7:45 AM, llowder  wrote:
>
>
> On Wednesday, October 3, 2012 9:37:01 AM UTC-5, Mister Guru wrote:
>>
>> I'm sending this email to start this thread, feel free to comment as
>> appropriate. I'm going to assume that it's going to take a while for most
>> people to actually realise that the puppet update may be giving them some
>> issues, so, comments and suggestion please!
>
>
> Don't use ensure => latest.
>
> Either just use installed, or a specific version, and then you can upgrade
> when you are ready to.

Even if you use ensure => installed, newly provisioned nodes will get
the latest available version at the time Puppet first runs, which will
cause issues unless you're also running a compatible Puppet master.

-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet cron job class stamps file with date-time. How?

[Christopher Wood]

In this case the text appears to be a hardcode in a couple of providers:

$ grep -r managed\ manually `pwd`
/usr/lib/ruby/1.8/puppet/provider/parsedfile.rb:# HEADER: by puppet.  While it 
can still be managed manually, it
/usr/lib/ruby/1.8/puppet/provider/cron/crontab.rb:# HEADER: While it can still 
be managed manually, it is definitely not recommended.

But this sounds like a great string for an environment-wide variable (hiera 
lookup) that all your templates can use.

On Thu, Oct 04, 2012 at 12:08:39PM -0700, Jo Rhett wrote:
>I would also like to know this. I keep hacking the same text into our
>templates. If there is a tag we could put in a template to get this output
>I'd like to know it.
>On Oct 1, 2012, at 12:05 PM, Brian Dunbar wrote:
> 
>  New puppet user.  I see that the cron class creates a cronjob with a
>  date-time in the header, which is cool.
>  # HEADER: This file was autogenerated at Mon Oct 01 11:43:25 -0500 2012
>  by puppet.
>  # HEADER: While it can still be managed manually, it is definitely not
>  recommended.
>  1. How does it do that? 
>  2. I'd like to be able to edit the text, customize it.
>  3. More particularly, how can I put a date/time stamp in other managed
>  files?  
>  I tried to do so with a template but that was not working out so well.
>  Regards,
>  ~brian
>  --
>  You received this message because you are subscribed to the Google
>  Groups "Puppet Users" group.
>  To view this discussion on the web visit
>  [1]https://groups.google.com/d/msg/puppet-users/-/Wsckx5euwRgJ.
>  To post to this group, send email to [2]puppet-users@googlegroups.com.
>  To unsubscribe from this group, send email to
>  [3]puppet-users+unsubscr...@googlegroups.com.
>  For more options, visit this group at
>  [4]http://groups.google.com/group/puppet-users?hl=en.
> 
>-- 
>Jo Rhett
>Net Consonance : net philanthropy to improve open source and internet
>projects.
> 
>--
>You received this message because you are subscribed to the Google Groups
>"Puppet Users" group.
>To post to this group, send email to puppet-users@googlegroups.com.
>To unsubscribe from this group, send email to
>puppet-users+unsubscr...@googlegroups.com.
>For more options, visit this group at
>http://groups.google.com/group/puppet-users?hl=en.
> 
> References
> 
>Visible links
>1. https://groups.google.com/d/msg/puppet-users/-/Wsckx5euwRgJ
>2. mailto:puppet-users@googlegroups.com
>3. mailto:puppet-users+unsubscr...@googlegroups.com
>4. http://groups.google.com/group/puppet-users?hl=en

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet cron job class stamps file with date-time. How?

[Stephen Gran]

Hi,

On Thu, 2012-10-04 at 12:08 -0700, Jo Rhett wrote:

> I would also like to know this. I keep hacking the same text into our
> templates. If there is a tag we could put in a template to get this
> output I'd like to know it.
> 

Templates can take more than one source of data, so a trivial way to do
this is something like:

define my_template(
$fname,
$template,
$owner=root,
$group=$::root_group,
...
) {

file { $fname:
content => template('site/header.erb', $template, 
'site/footer.erb'),
owner   => $owner,
group   => $group
...
}
}

See the templating docs.

Cheers,
-- 
Stephen Gran
Senior Systems Integrator - guardian.co.uk

Please consider the environment before printing this email.
--
Visit guardian.co.uk - newspaper of the year

www.guardian.co.ukwww.observer.co.uk www.guardiannews.com 

On your mobile, visit m.guardian.co.uk or download the Guardian
iPhone app www.guardian.co.uk/iphone and iPad edition www.guardian.co.uk/iPad 
 
Save up to 37% by subscribing to the Guardian and Observer - choose the papers 
you want and get full digital access. 
Visit guardian.co.uk/subscribe 

-
This e-mail and all attachments are confidential and may also
be privileged. If you are not the named recipient, please notify
the sender and delete the e-mail and all attachments immediately.
Do not disclose the contents to another person. You may not use
the information for any purpose, or store, or copy, it in any way.
 
Guardian News & Media Limited is not liable for any computer
viruses or other material transmitted with or as part of this
e-mail. You should employ virus checking software.

Guardian News & Media Limited

A member of Guardian Media Group plc
Registered Office
PO Box 68164
Kings Place
90 York Way
London
N1P 2AP

Registered in England Number 908396

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet cron job class stamps file with date-time. How?

[Jo Rhett]

I would also like to know this. I keep hacking the same text into our 
templates. If there is a tag we could put in a template to get this output I'd 
like to know it.

On Oct 1, 2012, at 12:05 PM, Brian Dunbar wrote:
> New puppet user.  I see that the cron class creates a cronjob with a 
> date-time in the header, which is cool.
> 
> # HEADER: This file was autogenerated at Mon Oct 01 11:43:25 -0500 2012 by 
> puppet.
> # HEADER: While it can still be managed manually, it is definitely not 
> recommended.
> 
> 1. How does it do that? 
> 2. I'd like to be able to edit the text, customize it.
> 3. More particularly, how can I put a date/time stamp in other managed files? 
>  
> 
> I tried to do so with a template but that was not working out so well.
> 
> Regards,
> 
> ~brian
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/puppet-users/-/Wsckx5euwRgJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] RHEL 5: Stuck on Puppet 2.7

[Jo Rhett]

On Oct 4, 2012, at 5:56 AM, jcbollinger wrote:
> On Wednesday, October 3, 2012 8:19:59 AM UTC-5, Ygor wrote:
> [...]
> 1:rubygem-passenger-native-libs-3.0.12-1.el5.centos_1.8.5.x86_64 from 
> installed has depsolving problems 
>   --> Missing Dependency: ruby = 1.8.5 is needed by package 
> 1:rubygem-passenger-native-libs-3.0.12-1.el5.centos_1.8.5.x86_64 (installed) 
> Error: Missing Dependency: ruby = 1.8.5 is needed by package 
> 1:rubygem-passenger-native-libs-3.0.12-1.el5.centos_1.8.5.x86_64 (installed) 
> 
> OK, a bit of Google-ing says that Passenger 3.0.14 was released in July 
> http://blog.phusion.nl/2012/07/22/phusion-passenger-3-0-14-released/#.UGsb6-c547w
>  
> 
> But the latest RPM on 
> http://passenger.stealthymonkeys.com/rhel/5Server/x86_64/ 
> is rubygem-passenger-native-libs-3.0.12-1.el5.centos_1.8.5.x86_64.rpm -- 
> which is what I currently have. 
> 
> Suggestions ?  I sent an email to Erik Ogan, owner of Stealth Monkeys, but 
> have not received a response. 
> 
> 
> Download the source RPM, modify the requirement to, for example, ruby >= 
> 1.8.7, increment the release number, and rebuild.  Probably no other changes 
> are needed.


Actually, it's not specified in the source RPM. And just recompiling the source 
RPM solves the problem. I ran into the same thing, just grabbed the SRPMs and 
built them and it worked fine.  Something weird about dependancies encoded in 
the RPM details *shrug*

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] environment set by client issues on nodes running 3.0.0

[Jeff McCune]

On Thu, Oct 4, 2012 at 11:12 AM, Matthew Nicholson
 wrote:
> File a bug report ? or is this an already tracked issue?

If you could file a bug report and then reply here with the ticket
number, that will help tremendously.  In the meantime I'm going to
start investigating and try to reproduce the issue here.

Thanks for reporting this,
-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] anchor pattern and class containment status

[Tim Mooney]

In regard to: Re: [Puppet Users] anchor pattern and class containment...:


On Wed, Oct 3, 2012 at 2:57 PM, Tim Mooney  wrote:

I thought I understood why 'anchor' is part of stdlib, but after
re-reading both


I suspect Dan & John have covered this well enough for you but I
wanted to point out a nice piece of the Puppet reference manual that
covers this. 
http://docs.puppetlabs.com/puppet/2.7/reference/lang_containment.html#known-issues


Thanks Ryan, and thanks especially for the rewritten reference.  I haven't
been through all of it yet, but the parts I've seen are excellent.


It explains things better than I ever could. If it's still not clear
enough, please consider filing a ticket against our docs for
improvement: https://projects.puppetlabs.com/projects/puppet-docs


I created

  https://projects.puppetlabs.com/issues/16783

which mentions what I think might be a bug in the second example on that
page and also asks for a little clarification.

Thanks again for the pointer to the docs!

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Puppet caught TERM; calling stop - error

[Will S. G.]

One other thing I noticed, /etc/sysconfig/puppet was rewritten with default 
values on the hosts that are experiencing this issue. I killed the proc, 
then wrote the values that I use on the working agents, but I continue to 
get the same error message. Is there anyone else that has seen this? I've 
been at it for a while, I cannot figure this out.

On Wednesday, October 3, 2012 11:32:48 PM UTC-7, Will S. G. wrote:
>
> I'm running puppet on CentOS 6.3 x86_64: 
>
>- facter.i386   1:1.6.12-2.el6@puppet
>- puppet.noarch 2.7.19-1.el6  @puppet
>- ruby-shadow.x86_641.4.1-13.el6  @puppet
>
> Puppetmaster: 
>
>- facter.x86_64 1:1.6.12-2.el6@puppet
>- hiera.noarch  1.0.0-2.el6   @puppet
>- puppet.noarch 2.7.19-1.el6  @puppet
>- puppet-dashboard.noarch 1.2.11-1.el6  @puppet
>- puppet-server.noarch  2.7.19-1.el6  @puppet
>- ruby-mysql.x86_64 2.8.2-1.el6   @puppet
>- ruby-shadow.x86_641.4.1-13.el6  @puppet
>
> I keep getting seeing the following error on my puppet agent: 
>
> Wed Oct 03 23:25:43 -0700 2012 Puppet (notice): Starting Puppet client 
> version 2.7.19
> Wed Oct 03 23:26:11 -0700 2012 Puppet (notice): Caught TERM; calling stop
> Wed Oct 03 23:26:16 -0700 2012 Puppet (notice): Reopening log files
> Wed Oct 03 23:26:55 -0700 2012 Puppet (err): Could not retrieve catalog 
> from remote server: Error 400 on SERVER: could not obtain a database 
> connection within 5 seconds.  The max pool size is currently 5; consider 
> increasing it.
>
> I can't seem to figure out what's wrong. What's even more weird is that 
> only some of the agents are displaying this error. 
>
> Any suggestions? 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/YgPRAfFabIMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] puppetlabs code repositories and issues integration

[Shantanu]

Thanks for the reply Ryan. 

I am looking for an option that will help discuss code changes effectively 
by referencing a code snippet or a commit specific file revision in project 
issues. For example, here is an 
issueopened in my 
forked puppetlabs-apache repository. Likewise, if someone 
wants to get feedback on proposed code changes, then it's helpful to put 
code snippets or commit ids within the issue discussion rather than 
pointing them to an external URL. Also, the github markup makes it easier 
to reference commit IDs and users. 

In addition, I think github issues will help in making issue assignment 
better as user accounts on both systems - issues and code repository - will 
be the same. I think this can be done by using github credentials on the 
project site as well.

Also, +1 for new updates to the forge site!
 
--
Regards,
Shantanu


On Thursday, October 4, 2012 10:28:51 AM UTC-5, Ryan Coleman wrote:
>
> Hi Shantanu, 
>
> I don't quite understand what you're asking for. Could you elaborate? 
> It sounds like you're looking for more than just pasting a URL into 
> the branch field of a ticket on our projects site. 
>
> I have been toying with the idea of enabling GitHub issues for some of 
> the Puppet Labs modules. Which module were you working on and what 
> would GitHub issues help you do better? 
>
> Cheers! 
> --Ryan 
>
> On Thu, Oct 4, 2012 at 7:57 AM, Shantanu > 
> wrote: 
> > 
> > I was wondering if it's possible to cross-reference a puppetlabs module 
> code 
> > on github while creating an issue or discussion on puppetlabs projects 
> site. 
> > It would be helpful if users could cross-reference code on the project 
> site 
> > or puppetlabs github repositories have issues enabled. 
> > 
> > Thanks, 
> > Shantanu 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Puppet Users" group. 
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msg/puppet-users/-/JAvCqkZNXs4J. 
> > To post to this group, send email to 
> > puppet...@googlegroups.com. 
>
> > To unsubscribe from this group, send email to 
> > puppet-users...@googlegroups.com . 
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/3ovg1bFMSZ8J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] environment set by client issues on nodes running 3.0.0

[Matthew Nicholson]

File a bug report ? or is this an already tracked issue?

On Thu, Oct 4, 2012 at 12:39 PM, Matthew Nicholson
 wrote:
> correct, no enc, just nodes.pp (node_terminus=plain)(ugh, yes, i know).
>
> previously had the following in puppet.conf on our master(s):
>
> environment = production
> manifest = /etc/puppet/environments/$environment/manifests/site.pp
> modulepath=/etc/puppet/environments/$environment/modules
>
>
> so things would always default to production unless specified. i
> commented out the environment = production line just to test, and
> there were no changes.
>
>
> On Thu, Oct 4, 2012 at 12:31 PM, Jeff McCune  wrote:
>> On Thu, Oct 4, 2012 at 8:46 AM, Matthew Nicholson
>>  wrote:
>>> So, we use dynamic environments based off of git branches. Thus, for
>>> the 3.0 upgrade, i've got a puppet3 branch. So far, on the change in
>>> there is to have nodes running from it upgrade to puppet 3.0.0,
>>>
>>> so, I can take a node, and do:
>>>
>>> puppet agent --test --environment=puppet3
>>> and this will install 3.0.0, as well as edit the environment in
>>> /etc/puppet/puppet.conf on the node to be "puppet3"
>>>
>>> However, subsequent runs, with with --environment=puppet3 passed, or
>>> relying on the puppet.conf setting, of the now 3.0.0 node, results in:
>>>
>>> Warning: Local environment: "puppet3" doesn't match server specified
>>> node environment "production", switching agent to "production".
>>
>> This definitely looks like a bug in 3.0.0.  The behavior we intend is
>> that an ENC can override the client specified environment, but it
>> sounds like you are not using an ENC.  Is that correct?  If you are
>> using an ENC, could you verify that the ENC is not setting the
>> environment parameter?
>>
>> -Jeff
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
>
>
> --
> Matthew Nicholson



-- 
Matthew Nicholson

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet 3.0: Not authorized to call find on /file_metadata, more issues?

[Forrie]

Jeff, 

Thanks for the reply.  This is the first Puppet distribution that I've 
upgraded to that required a lot of manual changes.  But that comes with the 
territory :-)

What I think would be very useful is to not only include sample *.conf 
files, init scripts, and such, but also example usage of new features in 
common scenarios.  For example, Eric S. referred to the config 
file https://github.com/puppetlabs/puppet/blob/master/conf/auth.conf which 
does state allow_ip in the top portion, but there's no usage example in the 
content.   I sometimes find it easier to grok changes when I see contextual 
examples :-)   That might be a bad example, as it's pretty simple -- but I 
think you get the gist of what I mean.

Thanks again!
Forrest



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/78NYNBHDZ94J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Puppet 3.0 + Inventory search

[Nathan Flynn]

Ah thank you.

Yes it appear I am hit with bug 16769. I did see the bug but thought it was 
not related as puppet ca seemed to be working, only the inventory search 
functions seem to be affected.

Disabling "+ExportCertData" has resolved the problem. Looking forward to 
3.0.1.



On Thursday, 4 October 2012 10:00:34 UTC+1, Nathan Flynn wrote:


Hello,
>
> I am having problems with Puppet since upgrading to 3.0.0.
>
> When I call an inventory search I get a Error 400. I have used dashboard + 
> Perl
>
> Oct  4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET 
> /production/facts_search/search?facts.lsbdistcodename.eq=lenny
> Oct  4 08:58:43 puppet01 puppet-master[7008]: header too long
>
>
> ii  facter  1.6.12-1puppetlabs2  Ruby 
> module for collecting simple facts about a host operating system
> ii  hiera   1.0.0-1puppetlabs2   A 
> simple pluggable Hierarchical Database.
> ii  puppet  3.0.0-1puppetlabs1   
> Centralized configuration management - agent startup and compatibility 
> scripts
> ii  puppet-common   3.0.0-1puppetlabs1   
> Centralized configuration management
> ii  puppet-dashboard1.2.11-1puppetlabs1  
> Dashboard for Puppet
> ii  puppetdb1.0.0-1puppetlabs1   
> PuppetDB Centralized Storage.
> ii  puppetdb-terminus   1.0.0-1puppetlabs1   
> Connect Puppet to PuppetDB by setting up a terminus for PuppetDB.
> ii  puppetmaster3.0.0-1puppetlabs1   
> Centralized configuration management - master startup and compatibility 
> scripts
> ii  puppetmaster-common 3.0.0-1puppetlabs1   
> Puppet master common scripts
> ii  puppetmaster-passenger  3.0.0-1puppetlabs1   
> Centralised configuration management - master setup to run under mod 
> passenger
> ii  vim-puppet  3.0.0-1puppetlabs1   
> syntax highlighting for puppet manifests in vim
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Sg_EhfBIgicJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet 3.0 + Inventory search

[Justin Stoller]

Are you using +ExportCertData in your configuration?

Have a look at: http://projects.puppetlabs.com/issues/16769

and let us know if you think this is what is affecting you.

 HTH,
Justin

On Thu, Oct 4, 2012 at 9:47 AM, Jeff McCune  wrote:
> On Thu, Oct 4, 2012 at 2:00 AM, Nathan Flynn  wrote:
>> Hello,
>>
>> I am having problems with Puppet since upgrading to 3.0.0.
>
> I'm sorry to hear you're running into issues with 3.0.0.
>
>> When I call an inventory search I get a Error 400. I have used dashboard +
>> Perl
>
> I'd like to try and reproduce this error here.  What operating system
> are you running the puppetmaster on?
>
>> Oct  4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET
>> /production/facts_search/search?facts.lsbdistcodename.eq=lenny
>> Oct  4 08:58:43 puppet01 puppet-master[7008]: header too long
>>
>>
>> ii  facter  1.6.12-1puppetlabs2  Ruby
>> module for collecting simple facts about a host operating system
>> ii  hiera   1.0.0-1puppetlabs2   A
>> simple pluggable Hierarchical Database.
>> ii  puppet  3.0.0-1puppetlabs1
>> Centralized configuration management - agent startup and compatibility
>> scripts
>> ii  puppet-common   3.0.0-1puppetlabs1
>> Centralized configuration management
>> ii  puppet-dashboard1.2.11-1puppetlabs1
>> Dashboard for Puppet
>> ii  puppetdb1.0.0-1puppetlabs1
>> PuppetDB Centralized Storage.
>> ii  puppetdb-terminus   1.0.0-1puppetlabs1   Connect
>> Puppet to PuppetDB by setting up a terminus for PuppetDB.
>> ii  puppetmaster3.0.0-1puppetlabs1
>> Centralized configuration management - master startup and compatibility
>> scripts
>> ii  puppetmaster-common 3.0.0-1puppetlabs1   Puppet
>> master common scripts
>> ii  puppetmaster-passenger  3.0.0-1puppetlabs1
>> Centralised configuration management - master setup to run under mod
>> passenger
>> ii  vim-puppet  3.0.0-1puppetlabs1   syntax
>> highlighting for puppet manifests in vim
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/puppet-users/-/QNQWubob8lYJ.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: activerecord and puppet-3.0.0

[Joe Hillenbrand]

Installing 3.0.11 (and removing all the old versions manually, fucking
ruby gems!) didn't help for me:

~$ sudo gem list

*** LOCAL GEMS ***

activemodel (3.0.11)
activerecord (3.0.11)
activesupport (3.0.11)
arel (2.0.10)
bigdecimal (1.1.0)
builder (2.1.2)
bundler (1.1.5)
charlock_holmes (0.6.8)
i18n (0.5.0)
io-console (0.3)
json (1.5.4)
minitest (2.5.1)
multi_json (1.3.6)
puppet-lint (0.2.1)
rake (0.9.2.2)
rdoc (3.9.4)
tzinfo (0.3.33)


I think there used to be an ubuntu package for activerecord but it's
not there anymore.

On Thu, Oct 4, 2012 at 9:30 AM, Andy Parker  wrote:
> I encountered this issue yesterday when trying to reproduce another
> issue. I discovered that you need to be using activerecord 3.0.11.
> Later versions don't seem to work (error with a "stack too deep") and
> earlier versions don't seem to work (error with "uninitialized
> constant ActiveRecord").
>
> On Thu, Oct 4, 2012 at 7:55 AM, Jonathan Gazeley
>  wrote:
>> I managed to set up a fresh virtual machine with puppet 3 on it. Using the
>> same server config and certs and a demo puppet 3 client, the system worked.
>> So I wasn't able to run any debugging.
>>
>> Therefore, I am forced to conclude that the problem lies not with puppet 3
>> itself, but probably with some old gems that are left lying around on my old
>> system.
>>
>> So I have a new plan: rather than upgrade my old puppetmaster from 2.7 to
>> 3.0, I'll create a new puppet 3 server and migrate to that. Then I'll
>> re-upgrade my old 2.7 puppetmaster and run the debugs... if you are still
>> interested in them by then.
>>
>> Cheers,
>> Jonathan
>>
>>
>>
>> On 04/10/12 12:34, Jonathan Gazeley wrote:
>>>
>>> Hi Eric,
>>>
>>> Thanks for your attention on this.
>>>
>>> Right now I'm not able to run any tests on my puppet master because we
>>> were forced to roll it back to 2.7 to restore service. I work at a
>>> university, this week is freshers' week and we totally need our config
>>> management to work at this busy time!
>>>
>>> Hopefully in the next few days I'll try to set up a second puppet master
>>> with puppet 3 and see if I can recreate the problem without breaking all
>>> of my infrastructure ;)
>>>
>>> Cheers,
>>> Jonathan
>>>
>>>
>>> On 04/10/12 00:20, Eric Sorenson wrote:

 Thanks for reporting this, we're looking into it.  I've made a ticket
 for your issue: https://projects.puppetlabs.com/issues/16770

 If you can do so, could you please run the puppet master with the
 '--trace' option ( either on the command line or with a `ARGV <<
 '--trace'` line in config.ru if you are starting from passenger, and
 update the ticket with the output? Thanks!!

 eric0

 On Wednesday, October 3, 2012 2:26:42 AM UTC-7, Jonathan Gazeley wrote:

 Yesterday my puppetmaster and nodes got upgraded to puppet-3.0.0.

 Since then, all puppet runs have been failing with this error:

 Error: Could not retrieve catalog from remote server: Error 400 on
 SERVER: Could not autoload puppet/indirector/node/active_record:
 uninitialized constant ActiveRecord


 My colleague and I have put a few hours into trying to work out
 what's
 wrong. rubygem-activerecord-2.1.1-2.el6.noarch is installed from the
 puppetlabs RPM repo. We've reinstalled all components but made no
 progress.

 I found this thread which seems to describe the same behaviour, but
 there are no replies:



 https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/D85TsZ70LKQ



 



 Anyone got any ideas?

 Thanks,
 Jonathan

 --
 You received this message because you are subscribed to the Google
 Groups "Puppet Users" group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/puppet-users/-/KPQEZyWqezMJ.
 To post to this group, send email to puppet-users@googlegroups.com.
 To unsubscribe from this group, send email to
 puppet-users+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/puppet-users?hl=en.
>>>
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.g

Re: [Puppet Users] Puppet 3.0 + Inventory search

[Jeff McCune]

On Thu, Oct 4, 2012 at 2:00 AM, Nathan Flynn  wrote:
> Hello,
>
> I am having problems with Puppet since upgrading to 3.0.0.

I'm sorry to hear you're running into issues with 3.0.0.

> When I call an inventory search I get a Error 400. I have used dashboard +
> Perl

I'd like to try and reproduce this error here.  What operating system
are you running the puppetmaster on?

> Oct  4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET
> /production/facts_search/search?facts.lsbdistcodename.eq=lenny
> Oct  4 08:58:43 puppet01 puppet-master[7008]: header too long
>
>
> ii  facter  1.6.12-1puppetlabs2  Ruby
> module for collecting simple facts about a host operating system
> ii  hiera   1.0.0-1puppetlabs2   A
> simple pluggable Hierarchical Database.
> ii  puppet  3.0.0-1puppetlabs1
> Centralized configuration management - agent startup and compatibility
> scripts
> ii  puppet-common   3.0.0-1puppetlabs1
> Centralized configuration management
> ii  puppet-dashboard1.2.11-1puppetlabs1
> Dashboard for Puppet
> ii  puppetdb1.0.0-1puppetlabs1
> PuppetDB Centralized Storage.
> ii  puppetdb-terminus   1.0.0-1puppetlabs1   Connect
> Puppet to PuppetDB by setting up a terminus for PuppetDB.
> ii  puppetmaster3.0.0-1puppetlabs1
> Centralized configuration management - master startup and compatibility
> scripts
> ii  puppetmaster-common 3.0.0-1puppetlabs1   Puppet
> master common scripts
> ii  puppetmaster-passenger  3.0.0-1puppetlabs1
> Centralised configuration management - master setup to run under mod
> passenger
> ii  vim-puppet  3.0.0-1puppetlabs1   syntax
> highlighting for puppet manifests in vim
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/QNQWubob8lYJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] anchor pattern and class containment status

[Tim Mooney]

In regard to: Re: [Puppet Users] anchor pattern and class containment...:


On Wed, Oct 3, 2012 at 2:57 PM, Tim Mooney  wrote:



All-

We're currently using puppet 2.7.14 on master and all clients.

I thought I understood why 'anchor' is part of stdlib, but after
re-reading both

http://projects.puppetlabs.**com/projects/puppet/wiki/**
Anchor_Pattern

and


http://projects.puppetlabs.**com/issues/8040

yesterday in preparation for trying to explain it to one of our team
that's coming up to speed on puppet, now I'm not so certain I really
understand.



yep, its probably the most confusing part of Puppet :(


:-)  I think I would vote for create_resources() in that competition.


Specifically, is it necessary to use the anchor pattern if your module
only defines resources and doesn't require or include any other classes?



you only have to use the anchor pattern when you need to depend on a class
that has classes defined in it. The example below does not need the anchor
pattern.


Thanks Dan!  The info from you & John & Ryan has been very helpful.

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet 3 killed my environment variables

[Jeff McCune]

On Wed, Oct 3, 2012 at 5:45 AM, Daniele Sluijters
 wrote:
> Hello,
>
> In Puppet 3 Puppet does its absolute best to make sure $HOME, $USER and
> $LOGNAME environment variables are unset and nowhere to be found. I realise
> this change was necessary because it caused some weird start-up issues with
> Puppet but this also killed our RabbitMQ module.

This shouldn't be the case.  Puppet should respect the values of
environment variables.  A related change that I'm aware of is that
Puppet goes out of the way to ensure HOME is _set_ rather than unset.

Could you refer me to the information you found that indicates this
change of unsetting HOME USER and LOGNAME is necessary?  I'm not sure
I'm up to speed on this information and would like to review it.

Thanks,
-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] environment set by client issues on nodes running 3.0.0

[Matthew Nicholson]

correct, no enc, just nodes.pp (node_terminus=plain)(ugh, yes, i know).

previously had the following in puppet.conf on our master(s):

environment = production
manifest = /etc/puppet/environments/$environment/manifests/site.pp
modulepath=/etc/puppet/environments/$environment/modules


so things would always default to production unless specified. i
commented out the environment = production line just to test, and
there were no changes.


On Thu, Oct 4, 2012 at 12:31 PM, Jeff McCune  wrote:
> On Thu, Oct 4, 2012 at 8:46 AM, Matthew Nicholson
>  wrote:
>> So, we use dynamic environments based off of git branches. Thus, for
>> the 3.0 upgrade, i've got a puppet3 branch. So far, on the change in
>> there is to have nodes running from it upgrade to puppet 3.0.0,
>>
>> so, I can take a node, and do:
>>
>> puppet agent --test --environment=puppet3
>> and this will install 3.0.0, as well as edit the environment in
>> /etc/puppet/puppet.conf on the node to be "puppet3"
>>
>> However, subsequent runs, with with --environment=puppet3 passed, or
>> relying on the puppet.conf setting, of the now 3.0.0 node, results in:
>>
>> Warning: Local environment: "puppet3" doesn't match server specified
>> node environment "production", switching agent to "production".
>
> This definitely looks like a bug in 3.0.0.  The behavior we intend is
> that an ENC can override the client specified environment, but it
> sounds like you are not using an ENC.  Is that correct?  If you are
> using an ENC, could you verify that the ENC is not setting the
> environment parameter?
>
> -Jeff
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>



-- 
Matthew Nicholson

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet 3 killed my environment variables

[Andy Parker]

On Thu, Oct 4, 2012 at 7:24 AM, jcbollinger  wrote:
>
>
> Puppet's guts have code for setting a custom environment for commands, but
> the 'command' and 'commands' functions don't provide an interface to it.
> I'm working from the code here, not actual experience, but it looks like you
> can use the has_command() function instead, something like:
>
> has_command(:my_command, '/usr/sbin') do
>   environment({ 'HOME' => '/some/homedir' })
> end
>
> I don't remember seeing that documented anywhere, so it probably qualifies
> as an internal interface -- use at your own risk.  Since you'll probably
> want to look at the code yourself, you can find that function in
> puppet/lib/puppet/provider.rb.  In particular, you can examine how it is
> used by the documented 'command' and 'commands' functions.
>

It is an oversight that that isn't documented. That should be
considered public interface and the way to solve this.

I've filed https://projects.puppetlabs.com/issues/16779 to get this in the docs.

>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/K3laepFVKggJ.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] environment set by client issues on nodes running 3.0.0

[Jeff McCune]

On Thu, Oct 4, 2012 at 8:46 AM, Matthew Nicholson
 wrote:
> So, we use dynamic environments based off of git branches. Thus, for
> the 3.0 upgrade, i've got a puppet3 branch. So far, on the change in
> there is to have nodes running from it upgrade to puppet 3.0.0,
>
> so, I can take a node, and do:
>
> puppet agent --test --environment=puppet3
> and this will install 3.0.0, as well as edit the environment in
> /etc/puppet/puppet.conf on the node to be "puppet3"
>
> However, subsequent runs, with with --environment=puppet3 passed, or
> relying on the puppet.conf setting, of the now 3.0.0 node, results in:
>
> Warning: Local environment: "puppet3" doesn't match server specified
> node environment "production", switching agent to "production".

This definitely looks like a bug in 3.0.0.  The behavior we intend is
that an ENC can override the client specified environment, but it
sounds like you are not using an ENC.  Is that correct?  If you are
using an ENC, could you verify that the ENC is not setting the
environment parameter?

-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: activerecord and puppet-3.0.0

[Andy Parker]

I encountered this issue yesterday when trying to reproduce another
issue. I discovered that you need to be using activerecord 3.0.11.
Later versions don't seem to work (error with a "stack too deep") and
earlier versions don't seem to work (error with "uninitialized
constant ActiveRecord").

On Thu, Oct 4, 2012 at 7:55 AM, Jonathan Gazeley
 wrote:
> I managed to set up a fresh virtual machine with puppet 3 on it. Using the
> same server config and certs and a demo puppet 3 client, the system worked.
> So I wasn't able to run any debugging.
>
> Therefore, I am forced to conclude that the problem lies not with puppet 3
> itself, but probably with some old gems that are left lying around on my old
> system.
>
> So I have a new plan: rather than upgrade my old puppetmaster from 2.7 to
> 3.0, I'll create a new puppet 3 server and migrate to that. Then I'll
> re-upgrade my old 2.7 puppetmaster and run the debugs... if you are still
> interested in them by then.
>
> Cheers,
> Jonathan
>
>
>
> On 04/10/12 12:34, Jonathan Gazeley wrote:
>>
>> Hi Eric,
>>
>> Thanks for your attention on this.
>>
>> Right now I'm not able to run any tests on my puppet master because we
>> were forced to roll it back to 2.7 to restore service. I work at a
>> university, this week is freshers' week and we totally need our config
>> management to work at this busy time!
>>
>> Hopefully in the next few days I'll try to set up a second puppet master
>> with puppet 3 and see if I can recreate the problem without breaking all
>> of my infrastructure ;)
>>
>> Cheers,
>> Jonathan
>>
>>
>> On 04/10/12 00:20, Eric Sorenson wrote:
>>>
>>> Thanks for reporting this, we're looking into it.  I've made a ticket
>>> for your issue: https://projects.puppetlabs.com/issues/16770
>>>
>>> If you can do so, could you please run the puppet master with the
>>> '--trace' option ( either on the command line or with a `ARGV <<
>>> '--trace'` line in config.ru if you are starting from passenger, and
>>> update the ticket with the output? Thanks!!
>>>
>>> eric0
>>>
>>> On Wednesday, October 3, 2012 2:26:42 AM UTC-7, Jonathan Gazeley wrote:
>>>
>>> Yesterday my puppetmaster and nodes got upgraded to puppet-3.0.0.
>>>
>>> Since then, all puppet runs have been failing with this error:
>>>
>>> Error: Could not retrieve catalog from remote server: Error 400 on
>>> SERVER: Could not autoload puppet/indirector/node/active_record:
>>> uninitialized constant ActiveRecord
>>>
>>>
>>> My colleague and I have put a few hours into trying to work out
>>> what's
>>> wrong. rubygem-activerecord-2.1.1-2.el6.noarch is installed from the
>>> puppetlabs RPM repo. We've reinstalled all components but made no
>>> progress.
>>>
>>> I found this thread which seems to describe the same behaviour, but
>>> there are no replies:
>>>
>>>
>>>
>>> https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/D85TsZ70LKQ
>>>
>>>
>>>
>>> 
>>>
>>>
>>>
>>> Anyone got any ideas?
>>>
>>> Thanks,
>>> Jonathan
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msg/puppet-users/-/KPQEZyWqezMJ.
>>> To post to this group, send email to puppet-users@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> puppet-users+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/puppet-users?hl=en.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Operating system conflict?

[Mike]

Thank you for your help John.

I was expecting top level declaration may cause problems, and tried to 
avoid it even before my problem raised, but didn't realize I did such one 
;-)

On Thursday, October 4, 2012 3:23:32 PM UTC+2, jcbollinger wrote:
>
>
>
> On Thursday, October 4, 2012 4:00:53 AM UTC-5, Mike wrote:
>>
>> Thanks for your answer.
>>
>> I think I've found my problem
>>
>> I had an include in the ubuntu base.pp
>> modules/ubuntu-common/manifests/base.pp:
>>
>> include ubuntu-something
>>
>> class ubuntu-common::base {
>> file { "/etc/openntpd/ntpd.conf":
>> ensure => file,
>> owner  => root,
>> group  => root,
>> mode   => 644,
>> content => 
>> template("ubuntu-common/$operatingsystemrelease/etc-openntpd-ntpd.conf.erb"),
>>   }
>> }
>>
>> If I understand it right, OpenBSD works until this file is included in 
>> cache, when an Ubuntu agent connects this file is loaded and as the 
>> "include" is outside the class it will be included for OpenBSD too, am I 
>> right? At least moving the include inside the ubuntu-common::base class 
>> fixed my issue.
>>
>
>
> That's conceivable.  Any declaration at top-level in any manifest applies, 
> in principle, to all nodes.  Depending on the manifest in which it appears, 
> however, it may or may not actually be parsed.  This is an excellent reason 
> to avoid such declarations except in site.pp and any files directly or 
> indirectly 'import'ed by site.pp.  I cannot confirm the specifics of 
> Puppet's caching strategy with respect to such declarations, but I can 
> definitely say that the declaration was placed incorrectly.
>
>  
>
>> I find it a bit annoying that something may fail depending on which agent 
>> connects, is there something I can do (like a puppet master option) so that 
>> in my example OpenBSD would fail directly and not only once an Ubuntu agent 
>> connects
>
>
>
> There may be master-side cache management directives you could use, but 
> something like that would have just kept the error in your manifests 
> hidden, rather than revealing it.  Meanwhile, you would suffer a 
> performance penalty and concomitant reduction in capacity at your 
> puppetmaster.
>
> Although it's not exactly what you were looking for, I think you can avoid 
> a recurrence of this sort of problem by ensuring that all your declarations 
> are inside classes or nodes, or possibly in site.pp.  That should avoid 
> flip flops with respect to which declarations Puppet sees for each client.
>
>
> John
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Qcq1KeW9uj0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] environment set by client issues on nodes running 3.0.0

[Matthew Nicholson]

So, we use dynamic environments based off of git branches. Thus, for
the 3.0 upgrade, i've got a puppet3 branch. So far, on the change in
there is to have nodes running from it upgrade to puppet 3.0.0,

so, I can take a node, and do:

puppet agent --test --environment=puppet3
and this will install 3.0.0, as well as edit the environment in
/etc/puppet/puppet.conf on the node to be "puppet3"

However, subsequent runs, with with --environment=puppet3 passed, or
relying on the puppet.conf setting, of the now 3.0.0 node, results in:

Warning: Local environment: "puppet3" doesn't match server specified
node environment "production", switching agent to "production".

at which point it re-write the puppet.conf and downgrades back to
2.7.19 (which, is cool that is WORKS, isn't what i want).

Now, I don't HAVE the environment defined sever side for this node.
with 2.7.x clients, everything is production unless the client
specifies otherwise. Is this a new behavior on 3.0?

all looks like:

http://projects.puppetlabs.com/issues/3910#note-82

https://github.com/puppetlabs/puppet/commit/43e15f57c0f3866423a8bd67d3cdb5b2e06b31cc

http://projects.puppetlabs.com/issues/16275

but has this not been merged to the release 3.0.0 code yet?

Thanks!

-- 
Matthew Nicholson

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] anchor pattern and class containment status

[Ryan Coleman]

On Wed, Oct 3, 2012 at 2:57 PM, Tim Mooney  wrote:
> I thought I understood why 'anchor' is part of stdlib, but after
> re-reading both

I suspect Dan & John have covered this well enough for you but I
wanted to point out a nice piece of the Puppet reference manual that
covers this. 
http://docs.puppetlabs.com/puppet/2.7/reference/lang_containment.html#known-issues

It explains things better than I ever could. If it's still not clear
enough, please consider filing a ticket against our docs for
improvement: https://projects.puppetlabs.com/projects/puppet-docs

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] puppetlabs code repositories and issues integration

[Ryan Coleman]

Hi Shantanu,

I don't quite understand what you're asking for. Could you elaborate?
It sounds like you're looking for more than just pasting a URL into
the branch field of a ticket on our projects site.

I have been toying with the idea of enabling GitHub issues for some of
the Puppet Labs modules. Which module were you working on and what
would GitHub issues help you do better?

Cheers!
--Ryan

On Thu, Oct 4, 2012 at 7:57 AM, Shantanu  wrote:
>
> I was wondering if it's possible to cross-reference a puppetlabs module code
> on github while creating an issue or discussion on puppetlabs projects site.
> It would be helpful if users could cross-reference code on the project site
> or puppetlabs github repositories have issues enabled.
>
> Thanks,
> Shantanu
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/JAvCqkZNXs4J.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] puppetlabs code repositories and issues integration

[Shantanu]

I was wondering if it's possible to cross-reference a puppetlabs module 
code on github while creating an issue or discussion on puppetlabs projects 
site. It would be helpful if users could cross-reference code on the 
project site or puppetlabs github repositories have issues enabled.

Thanks,
Shantanu

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/JAvCqkZNXs4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: activerecord and puppet-3.0.0

[Jonathan Gazeley]

I managed to set up a fresh virtual machine with puppet 3 on it. Using 
the same server config and certs and a demo puppet 3 client, the system 
worked. So I wasn't able to run any debugging.


Therefore, I am forced to conclude that the problem lies not with puppet 
3 itself, but probably with some old gems that are left lying around on 
my old system.


So I have a new plan: rather than upgrade my old puppetmaster from 2.7 
to 3.0, I'll create a new puppet 3 server and migrate to that. Then I'll 
re-upgrade my old 2.7 puppetmaster and run the debugs... if you are 
still interested in them by then.


Cheers,
Jonathan


On 04/10/12 12:34, Jonathan Gazeley wrote:

Hi Eric,

Thanks for your attention on this.

Right now I'm not able to run any tests on my puppet master because we
were forced to roll it back to 2.7 to restore service. I work at a
university, this week is freshers' week and we totally need our config
management to work at this busy time!

Hopefully in the next few days I'll try to set up a second puppet master
with puppet 3 and see if I can recreate the problem without breaking all
of my infrastructure ;)

Cheers,
Jonathan


On 04/10/12 00:20, Eric Sorenson wrote:

Thanks for reporting this, we're looking into it.  I've made a ticket
for your issue: https://projects.puppetlabs.com/issues/16770

If you can do so, could you please run the puppet master with the
'--trace' option ( either on the command line or with a `ARGV <<
'--trace'` line in config.ru if you are starting from passenger, and
update the ticket with the output? Thanks!!

eric0

On Wednesday, October 3, 2012 2:26:42 AM UTC-7, Jonathan Gazeley wrote:

Yesterday my puppetmaster and nodes got upgraded to puppet-3.0.0.

Since then, all puppet runs have been failing with this error:

Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not autoload puppet/indirector/node/active_record:
uninitialized constant ActiveRecord


My colleague and I have put a few hours into trying to work out
what's
wrong. rubygem-activerecord-2.1.1-2.el6.noarch is installed from the
puppetlabs RPM repo. We've reinstalled all components but made no
progress.

I found this thread which seems to describe the same behaviour, but
there are no replies:


https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/D85TsZ70LKQ






Anyone got any ideas?

Thanks,
Jonathan

--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/KPQEZyWqezMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.




--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet 3 killed my environment variables

[jcbollinger]

On Wednesday, October 3, 2012 8:11:55 AM UTC-5, Daniele Sluijters wrote:
>
> Hi,
>
> Sorry, I got confused between two things. It's not the actual Exec type. 
> it's when a provider executes a command that the environment cannot be set.
>
>
Puppet's guts have code for setting a custom environment for commands, but 
the 'command' and 'commands' functions don't provide an interface to it.  
I'm working from the code here, not actual experience, but it looks like 
you can use the has_command() function instead, something like:

has_command(:my_command, '/usr/sbin') do
  environment({ 'HOME' => '/some/homedir' })
end

I don't remember seeing that documented anywhere, so it probably qualifies 
as an internal interface -- use at your own risk.  Since you'll probably 
want to look at the code yourself, you can find that function in 
puppet/lib/puppet/provider.rb.  In particular, you can examine how it is 
used by the documented 'command' and 'commands' functions.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/K3laepFVKggJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: anchor pattern and class containment status

[jcbollinger]

On Wednesday, October 3, 2012 4:59:58 PM UTC-5, Tim Mooney wrote:
>
>
> All- 
>
> We're currently using puppet 2.7.14 on master and all clients. 
>
> I thought I understood why 'anchor' is part of stdlib, but after 
> re-reading both 
>
>  
> http://projects.puppetlabs.com/projects/puppet/wiki/Anchor_Pattern 
>
> and 
>
>  http://projects.puppetlabs.com/issues/8040 
>
> yesterday in preparation for trying to explain it to one of our team 
> that's coming up to speed on puppet, now I'm not so certain I really 
> understand. 
>
> Specifically, is it necessary to use the anchor pattern if your module 
> only defines resources and doesn't require or include any other classes? 
>


No, not as I understand it.  The problem is that in Puppet 2.6 and maybe 
2.7, classes are not directly represented in the relationship graph.  
Therefore, if you declare a relationship where one end is a class, it 
appears in the graph as a collection of relationships with the resources 
declared by that class.  If both ends are classes then you get n x m 
relationships, where n and m are the numbers of resources declared by the 
two classes.

The need for the anchor pattern arises because the generated relationships 
to a class Foo's resources do not include relationships to resources 
declared by classes declared in the body of Foo, and because declaring a 
class (except via the 'require' function) does not create a relationship 
between the declaring and declared classes.

The anchor pattern involves using relationships to resources declared 
directly by Foo to bound the application order of classes declared by Foo.  
Anchors are not needed for resources declared directly by Foo (else the 
anchor pattern wouldn't work in the first place).  The stdlib provides the 
special 'anchor' resource type specifically for this purpose, but resources 
of any other type could be used as well.

If Foo does not declare any other classes, then it gains no advantage from 
the anchor pattern.  If the needed ordering of interclass relationships is 
declared some other way, then the anchor pattern is unneeded.  If and when 
classes gain direct representation in the relationship graph (maybe it's 
happened already?), with (optional?) relationships to their included 
classes, the anchor pattern will no longer be needed.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/ADbfiab83rMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Puppet 3.0 + Inventory search

[Nathan Flynn]

Error from puppet master trace;

Oct  4 13:51:42 puppet01 puppet-master[1893]: Handling request: GET 
/production/facts_search/search?facts.lsbdistcodename.eq=lenny
Oct  4 13:51:42 puppet01 puppet-master[1893]: header too long
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/vendor_ruby/puppet/network/http/rack/rest.rb:86:in 
`initialize'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/vendor_ruby/puppet/network/http/rack/rest.rb:86:in `new'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/vendor_ruby/puppet/network/http/rack/rest.rb:86:in 
`client_cert'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:69:in `process'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/vendor_ruby/puppet/network/http/rack.rb:21:in `call'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/rack/request_handler.rb:92:in 
`process_request'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/abstract_request_handler.rb:207:in 
`main_loop'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/rack/application_spawner.rb:118:in `run'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/rack/application_spawner.rb:65:in 
`spawn_application'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/utils.rb:184:in `safe_fork'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/rack/application_spawner.rb:58:in 
`spawn_application'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/rack/application_spawner.rb:41:in 
`spawn_application'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:159:in 
`spawn_application'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:287:in 
`handle_spawn_application'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `__send__'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `main_loop'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in 
`start_synchronously'
Oct  4 13:51:42 puppet01 puppet-master[1893]: 
/usr/lib/phusion_passenger/passenger-spawn-server:61

On Thursday, 4 October 2012 10:00:34 UTC+1, Nathan Flynn wrote:
>
> Hello,
>
> I am having problems with Puppet since upgrading to 3.0.0.
>
> When I call an inventory search I get a Error 400. I have used dashboard + 
> Perl
>
> Oct  4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET 
> /production/facts_search/search?facts.lsbdistcodename.eq=lenny
> Oct  4 08:58:43 puppet01 puppet-master[7008]: header too long
>
>
> ii  facter  1.6.12-1puppetlabs2  Ruby 
> module for collecting simple facts about a host operating system
> ii  hiera   1.0.0-1puppetlabs2   A 
> simple pluggable Hierarchical Database.
> ii  puppet  3.0.0-1puppetlabs1   
> Centralized configuration management - agent startup and compatibility 
> scripts
> ii  puppet-common   3.0.0-1puppetlabs1   
> Centralized configuration management
> ii  puppet-dashboard1.2.11-1puppetlabs1  
> Dashboard for Puppet
> ii  puppetdb1.0.0-1puppetlabs1   
> PuppetDB Centralized Storage.
> ii  puppetdb-terminus   1.0.0-1puppetlabs1   
> Connect Puppet to PuppetDB by setting up a terminus for PuppetDB.
> ii  puppetmaster3.0.0-1puppetlabs1   
> Centralized configuration management - master startup and compatibility 
> scripts
> ii  puppetmaster-common 3.0.0-1puppetlabs1   
> Puppet master common scripts
> ii  puppetmaster-passenger  3.0.0-1puppetlabs1   
> Centralised configuration management - master setup to run under mod 
> passenger
> ii  vim-puppet  3.0.0-1puppetlabs1   
> syntax highlighting for puppet manifests in vim
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/3t16LS_D0pcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Operating system conflict?

[jcbollinger]

On Thursday, October 4, 2012 4:00:53 AM UTC-5, Mike wrote:
>
> Thanks for your answer.
>
> I think I've found my problem
>
> I had an include in the ubuntu base.pp
> modules/ubuntu-common/manifests/base.pp:
>
> include ubuntu-something
>
> class ubuntu-common::base {
> file { "/etc/openntpd/ntpd.conf":
> ensure => file,
> owner  => root,
> group  => root,
> mode   => 644,
> content => 
> template("ubuntu-common/$operatingsystemrelease/etc-openntpd-ntpd.conf.erb"),
>   }
> }
>
> If I understand it right, OpenBSD works until this file is included in 
> cache, when an Ubuntu agent connects this file is loaded and as the 
> "include" is outside the class it will be included for OpenBSD too, am I 
> right? At least moving the include inside the ubuntu-common::base class 
> fixed my issue.
>


That's conceivable.  Any declaration at top-level in any manifest applies, 
in principle, to all nodes.  Depending on the manifest in which it appears, 
however, it may or may not actually be parsed.  This is an excellent reason 
to avoid such declarations except in site.pp and any files directly or 
indirectly 'import'ed by site.pp.  I cannot confirm the specifics of 
Puppet's caching strategy with respect to such declarations, but I can 
definitely say that the declaration was placed incorrectly.

 

> I find it a bit annoying that something may fail depending on which agent 
> connects, is there something I can do (like a puppet master option) so that 
> in my example OpenBSD would fail directly and not only once an Ubuntu agent 
> connects



There may be master-side cache management directives you could use, but 
something like that would have just kept the error in your manifests 
hidden, rather than revealing it.  Meanwhile, you would suffer a 
performance penalty and concomitant reduction in capacity at your 
puppetmaster.

Although it's not exactly what you were looking for, I think you can avoid 
a recurrence of this sort of problem by ensuring that all your declarations 
are inside classes or nodes, or possibly in site.pp.  That should avoid 
flip flops with respect to which declarations Puppet sees for each client.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/IhZ5dk2TDVUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: RHEL 5: Stuck on Puppet 2.7

[jcbollinger]

On Wednesday, October 3, 2012 8:19:59 AM UTC-5, Ygor wrote:
>
> [...]
> 1:rubygem-passenger-native-libs-3.0.12-1.el5.centos_1.8.5.x86_64 from 
> installed has depsolving problems 
>   --> Missing Dependency: ruby = 1.8.5 is needed by package 
> 1:rubygem-passenger-native-libs-3.0.12-1.el5.centos_1.8.5.x86_64 
> (installed) 
> Error: Missing Dependency: ruby = 1.8.5 is needed by package 
> 1:rubygem-passenger-native-libs-3.0.12-1.el5.centos_1.8.5.x86_64 
> (installed) 
>
> OK, a bit of Google-ing says that Passenger 3.0.14 was released in July 
>
> http://blog.phusion.nl/2012/07/22/phusion-passenger-3-0-14-released/#.UGsb6-c547w
>  
>
> But the latest RPM on 
> http://passenger.stealthymonkeys.com/rhel/5Server/x86_64/ 
> is rubygem-passenger-native-libs-3.0.12-1.el5.centos_1.8.5.x86_64.rpm -- 
> which is what I currently have. 
>
> Suggestions ?  I sent an email to Erik Ogan, owner of Stealth Monkeys, but 
> have not received a response. 
>
>
Download the source RPM, modify the requirement to, for example, ruby >= 
1.8.7, increment the release number, and rebuild.  Probably no other 
changes are needed.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/WPdzCTfP02cJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Can Puppet interact with perl script user input fields?

[Guzman Braso]

Hi,

Please, be warn that I'm not a puppet guru, and very likely what I'm going
to tell you it's not recommended at all.

I've deal with the same issue with fdisk because sfdisk did not allow me to
do some stuff and needed to align some extra ssd drives from puppet.

exec { "run_abindproxy.pl":
  logoutput => on_failure,
  command => adbindproxy.pl < 
}

That will provide two carrier return on the expected input of
abbdindproxy.pl
If you have 4 questions, two should be hit carrier return to set default,
third should set 2 and four "on", would be:
exec { "run_abindproxy.pl":
  logoutput => on_failure,
  command => adbindproxy.pl < 
}

This works like a charm in puppet 2.7, dunno other versions. And again: I
don't believe this is a recommended way.

Cheers

Guzman
On Thu, Oct 4, 2012 at 6:34 AM, Jon Skarpeteig wrote:

> I'm trying to automate deployment of centrify-samba, which has a
> adbindproxy.pl setup script attached. This script expects user input
> (where 9 out of 10 options can be defaulted). Is there any way for
> Puppet to preconfigure the inputs for this scripts, and mimic user
> behavior by supplying this information?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
GuruHub - Guzmán Brasó
http://www.guruhub.com.uy - +59898674020
Rivera 3565 - CP11400 - Montevideo, Uruguay

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: activerecord and puppet-3.0.0

[Jonathan Gazeley]

Hi Eric,

Thanks for your attention on this.

Right now I'm not able to run any tests on my puppet master because we 
were forced to roll it back to 2.7 to restore service. I work at a 
university, this week is freshers' week and we totally need our config 
management to work at this busy time!


Hopefully in the next few days I'll try to set up a second puppet master 
with puppet 3 and see if I can recreate the problem without breaking all 
of my infrastructure ;)


Cheers,
Jonathan


On 04/10/12 00:20, Eric Sorenson wrote:

Thanks for reporting this, we're looking into it.  I've made a ticket
for your issue: https://projects.puppetlabs.com/issues/16770

If you can do so, could you please run the puppet master with the
'--trace' option ( either on the command line or with a `ARGV <<
'--trace'` line in config.ru if you are starting from passenger, and
update the ticket with the output? Thanks!!

eric0

On Wednesday, October 3, 2012 2:26:42 AM UTC-7, Jonathan Gazeley wrote:

Yesterday my puppetmaster and nodes got upgraded to puppet-3.0.0.

Since then, all puppet runs have been failing with this error:

Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not autoload puppet/indirector/node/active_record:
uninitialized constant ActiveRecord


My colleague and I have put a few hours into trying to work out what's
wrong. rubygem-activerecord-2.1.1-2.el6.noarch is installed from the
puppetlabs RPM repo. We've reinstalled all components but made no
progress.

I found this thread which seems to describe the same behaviour, but
there are no replies:

https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/D85TsZ70LKQ



Anyone got any ideas?

Thanks,
Jonathan

--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/KPQEZyWqezMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.


--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Puppet 2.7, hiera 1.0 and hiera as an ENC

[Guillem Liarte]

John,

Many thanks for your long reply, it is much appreciated. You have assured 
me in teh conclusions and course of action and i am glad that my 
appreciation of teh problem I have was not so far from the reality. 

Thanks again.

Guillem 

On Wednesday, 26 September 2012 16:52:19 UTC+1, Guillem Liarte wrote:
>
> This is the situation I have:
>
> All my hosts are the* same OS.*
> All my host are in the* same puppet environment,* so I cannot use 
> %{environment}
>
> I have a module that sets all the *basic* functionality for the OS, 
> resolution, authentication, security, packages, etc
> I have a module for each application hosted.
>
> At the moment all the 'data' is in Puppet, mostly in parametrised classes 
> in site.pp.
>
> What I want to get is a hiera set-up that allows me to use this structure:
>
> :hierarchy:
>   - global # source of application names (classes? modules?) and 
> environments list
>   - basic # data for the basic class
>   - prod/%{application}/%{hostname}# hostname files for specific 
> data
>   - prod/%{application}/%{env} # environmental data for 
> each application (module)
>   - prod/%{application}/default # default data for an 
> application
>   - nonprod/%{sysclass}/%{hostname}
>   - nonprod/%{sysclass}/%{env}
>   - nonprod/%{sysclass}/default 
>   
>
> Then to have something like this under the datadir:
>
>
> #├── global.yaml
> #├── basic.yaml
> #├── nonprod
> #│   ├── app1
> #│   │   ├── common-integration.yaml   << Alfresco common 
> integration
> #│   │   ├── continuous-integration.yaml   
> #│   │   ├── dev.yaml
> #│   │   ├── default.yaml
> #│   │   ├── host1.yaml   
> #│   │   ├── host2.yaml
> #│   │   ├── performance.yaml
> #│   │   ├── qa.yaml
> #│   │   ├── test.yaml
> #│   │   └── uat.yaml
> #│   └── app2
> #└── prod
> #├── app1
> #└── app2
> # 
> # etc.
>
> In global.yaml
>
> ---
> :classes:
>   basic:
>   app1:
>   app2:
>   app3:
>   app4:
> :env:
>   test:
>   dev:
>   commonint:
>   continuousint:
>   dev:
>   performance:
>   qa:
>   test:
>   uat:
>
>
> in app1 default.yaml:
>
> ---
> classes:
>   app1:
>
> app1_version:  'latest'
>
>
>
> in app1 dev.yaml:
> ---
> app1_version:  '3.0'
>
> If I wanted host1 and host2 to be part of dev for app1:
>
>
> host1.yaml:
> ---
> classes:
>   basic:
>   app1:
> env:
>   dev:
>
> maybe in host2 I want to override version too:
>
> host2.yaml
> ---
> classes:
>   basic:
>   app1:
> env:
>   dev:
> app1_version: '3.1'
>
>
> So in short, I would like hiera to be a source of facts, where I can get 
> information that feeds Puppet in order to classify the nodes and to feed 
> the parametrised classes.
>
> I recently found this blog entry:
>
> http://garyhetzel.com/2012/04/12/hiera_as_a_puppet_enc
>
> Gary has been very helpful and I have got an idea of what needs doing. I 
> can query all the data the way I want using the hiera command. Something 
> like these:
>
> hiera app1_version sysclass=app1 env=dev
>
> Returns the expected '3.0' and if I query by adding teh host:
>
> hiera app1_version sysclass=app1 env=dev hostname=host1
>
> I get 3.1. Cool!
>
>
> Example using Gary's approach:
>
> /opt/puppet-data/nonprod/hieratest/default.yaml 
> ---
> classes: hieratest
> env: hieratest_default
>
> /opt/puppet-data/nonprod/hieratest/host1.yaml 
> ---
> classes: 
>   hieratest:
> env: 'hieratest_performance'
>
>
> # hiera env sysclass=hieratest --debug
> DEBUG: Wed Sep 26 16:40:46 +0100 2012: Hiera YAML backend starting
> DEBUG: Wed Sep 26 16:40:46 +0100 2012: Looking up type in YAML backend
> DEBUG: Wed Sep 26 16:40:46 +0100 2012: Looking for data source global
> DEBUG: Wed Sep 26 16:40:46 +0100 2012: Looking for data source basic
> DEBUG: Wed Sep 26 16:40:46 +0100 2012: Looking for data source 
> nonprod/hieratest/default
> DEBUG: Wed Sep 26 16:40:46 +0100 2012: Found env in 
> nonprod/hieratest/default
> hieratest_default
>
> # hiera type sysclass=hieratest hostname=host1 --debug
> DEBUG: Wed Sep 26 16:40:57 +0100 2012: Hiera YAML backend starting
> DEBUG: Wed Sep 26 16:40:57 +0100 2012: Looking up type in YAML backend
> DEBUG: Wed Sep 26 16:40:57 +0100 2012: Looking for data source global
> DEBUG: Wed Sep 26 16:40:57 +0100 2012: Looking for data source basic
> DEBUG: Wed Sep 26 16:40:57 +0100 2012: Looking for data source 
> nonprod/hieratest/host1
> DEBUG: Wed Sep 26 16:40:57 +0100 2012: Found env in nonprod/hieratest/host1
> hieratest_performance
>
>
> But when it comes to use this in Puppet the results are not as I expect, 
> nothing happens, it just does a run no classes are used. I see that the 
> basic class custom facts are loaded, but nothing gets executed, as if the 
> catalogue for host1 would not include it.
>
>
> In Puppet  I expect to just have:
>
> in site.pp:
> node default {}
>
> And then in each application’s init.pp:
>
> $env = hiera("env")  << this allows me to get the right config  files 
> (with are maintaine

[Puppet Users] Can Puppet interact with perl script user input fields?

[Jon Skarpeteig]

I'm trying to automate deployment of centrify-samba, which has a
adbindproxy.pl setup script attached. This script expects user input
(where 9 out of 10 options can be defaulted). Is there any way for
Puppet to preconfigure the inputs for this scripts, and mimic user
behavior by supplying this information?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Puppet 3 docs are live

[Stefan Heijmans]

http://docs.puppetlabs.com/puppet/3/reference/release_notes.html#puppet-master-web-server-changes
>>This needs to be changed to Puppet::Util::CommandLine
but also the require seems to have changed 
from require 'puppet/application/master'
to   require 'puppet/util/command_line'
 
Op donderdag 4 oktober 2012 03:14:12 UTC+2 schreef Nick Fagerlund het 
volgende:

> Puppet 3 docs are now posted at 
> http://docs.puppetlabs.com/puppet/3/reference/ . We apologize for the 
> delay! This update adds release notes and a Puppet 3 language reference 
> with all of the relevant updated. Next on deck is improved Hiera 
> documentation. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/cfJfM1EnZC0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Operating system conflict?

[Mike]

Thanks for your answer.

I think I've found my problem

I had an include in the ubuntu base.pp
modules/ubuntu-common/manifests/base.pp:

include ubuntu-something

class ubuntu-common::base {
file { "/etc/openntpd/ntpd.conf":
ensure => file,
owner  => root,
group  => root,
mode   => 644,
content => 
template("ubuntu-common/$operatingsystemrelease/etc-openntpd-ntpd.conf.erb"),
  }
}

If I understand it right, OpenBSD works until this file is included in 
cache, when an Ubuntu agent connects this file is loaded and as the 
"include" is outside the class it will be included for OpenBSD too, am I 
right? At least moving the include inside the ubuntu-common::base class 
fixed my issue.

I find it a bit annoying that something may fail depending on which agent 
connects, is there something I can do (like a puppet master option) so that 
in my example OpenBSD would fail directly and not only once an Ubuntu agent 
connects?

Mike

On Wednesday, October 3, 2012 4:43:16 PM UTC+2, jcbollinger wrote:
>
>
>
> On Tuesday, October 2, 2012 9:35:13 AM UTC-5, Mike wrote:
>>
>> Hi,
>>
>> I've have some problems with my puppet configuration, I'm managing 
>> several Ubuntu and OpenBSD hosts.
>>
>> I sometimes get on OpenBSD hosts (5.0 is OpenBSD release):
>> info: Retrieving plugin
>> err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
>> Could not find template 'ubuntu-common/5.0/etc-openntpd-ntpd.conf.erb' at 
>> /usr/share/puppet/modules/ubuntu-common/manifests/base.pp:7 on node xxx
>> warning: Not using cache on failed catalog
>> err: Could not retrieve catalog; skipping run
>>
>> But this is in an Ubuntu template file, OpenBSD should never include this 
>> file, according to the case $operatingsystem in site.pp.
>>
>> I tracked the exact scenario which make it fail:
>>
>> 1. Restart puppet master - run agent only with OpenBSD hosts - it never 
>> fails, everything works as expected
>> 2. Restart puppet master - run agent only with Ubuntu hosts - it never 
>> fails, everything works as expected
>> 3. Restart puppet master - run agent with Ubuntu and OpenBSD hosts - 
>> Ubuntu works as expected, OpenBSD fails with the above error message (after 
>> the first Ubuntu agent was connected)
>> 4. after scenario 3. on puppet config file changes, OpenBSD works again 
>> until an Ubuntu agent connects to the master
>>
>> Do you have an idea of what could be wrong, or an known issue of puppet?
>>
>
>
> I am not aware of any known Puppet issue that results in behavior 
> comparable to this.
>
>  
>
>>
>> Could it be a puppet version issue, the master and Ubuntu hosts are using 
>> 2.7.19, OpenBSD hosts are using 2.7.1? (I haven't tried to downgrade ubuntu 
>> or upgrade OpenBSD's version, newer OpenBSD 5.1 comes with puppet 2.7.5)
>>
>
>
> That should not be an issue.  If the master and all the clients are on 
> 2.7.x, and none of the clients use newer Puppet than the master, then you 
> should be fine.  You should be ok even with 2.6.x clients.
>
>  
>
>>
>> According to scenario 4. could it be a caching issue on the master?
>>
>
>
> It rather looks like one, but the key question is why would such an issue 
> arise?  Puppet should never use cached details of one node's catalog to 
> build a different node's catalog.  Although I can't rule out a Puppet bug, 
> it more likely arises from a problem in your manifests or client 
> configuration.
>
>
>> I tried some puppet.conf options:
>>
>> ignorecache=true
>> usecacheonfailure=false
>>
>> but it didn't change anything.
>>
>
>
> Those options affect only the agent as far as I know, not the master.
>  
>
>>
>> The master and ubuntu hosts are running on Ubuntu 12.04
>> # puppet --version
>> 2.7.19
>> # ruby --version
>> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
>>
>> The OpenBSD hosts are OpenBSD 5.0
>> # puppet --version
>> 2.7.1
>> # ruby18  --version
>> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-openbsd]
>>
>> Here is my very simplified version of puppet files, I didn't try exactly 
>> this subset of configuration, I will try to narrow down the problem to the 
>> simplest configuration.
>>
>
>
> Often the process of narrowing it down will itself reveal the problem.  I 
> don't see why the manifest set you presented would exhibit a problem such 
> as the one you described, and since you didn't confirm that it does, I'm 
> not going to do further analysis.
>
> My only guess at this point is that something is screwy with your SSL 
> configuration.  Puppet identifies nodes by the certname on the client 
> certificates they present, so if you've done something like sharing the 
> same client cert among all your clients then the master will not recognize 
> them as different nodes.  Node facts (including $hostname) do not enter 
> that picture.
>
>
> John
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/ms

[Puppet Users] Puppet 3.0 + Inventory search

[Nathan Flynn]

Hello,

I am having problems with Puppet since upgrading to 3.0.0.

When I call an inventory search I get a Error 400. I have used dashboard + 
Perl

Oct  4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET 
/production/facts_search/search?facts.lsbdistcodename.eq=lenny
Oct  4 08:58:43 puppet01 puppet-master[7008]: header too long


ii  facter  1.6.12-1puppetlabs2  Ruby 
module for collecting simple facts about a host operating system
ii  hiera   1.0.0-1puppetlabs2   A 
simple pluggable Hierarchical Database.
ii  puppet  3.0.0-1puppetlabs1   
Centralized configuration management - agent startup and compatibility 
scripts
ii  puppet-common   3.0.0-1puppetlabs1   
Centralized configuration management
ii  puppet-dashboard1.2.11-1puppetlabs1  
Dashboard for Puppet
ii  puppetdb1.0.0-1puppetlabs1   
PuppetDB Centralized Storage.
ii  puppetdb-terminus   1.0.0-1puppetlabs1   
Connect Puppet to PuppetDB by setting up a terminus for PuppetDB.
ii  puppetmaster3.0.0-1puppetlabs1   
Centralized configuration management - master startup and compatibility 
scripts
ii  puppetmaster-common 3.0.0-1puppetlabs1   Puppet 
master common scripts
ii  puppetmaster-passenger  3.0.0-1puppetlabs1   
Centralised configuration management - master setup to run under mod 
passenger
ii  vim-puppet  3.0.0-1puppetlabs1   syntax 
highlighting for puppet manifests in vim

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/QNQWubob8lYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: puppet 3.0 with passenger

[Antidot SAS]

Hi I have filled out the ticket, let me know if something is missing.

Regards,
JM

On Thu, Oct 4, 2012 at 1:07 AM, Eric Sorenson
wrote:

> Hi JM, this sounds like a real problem that was probably introduced with
> our code to start warning on certificates close to their expiration dates.
>
> (#7962)
>
>
> https://github.com/puppetlabs/puppet/commit/12d81c7ef97167f1831143ff0037ae9a3970960d
>
> I created a ticket for this issue:
> https://projects.puppetlabs.com/issues/16769
>
> Can you please update the ticket with more information about your
> environment?
>
> - what version of passenger?
> - what version of apache?
>
> Thanks!
>
>
> On Tuesday, October 2, 2012 7:07:32 AM UTC-7, A_SAAS wrote:
>>
>> Hi everyone,
>>
>> I am trying to setup puppet 3.0 with passenger since this morning, it is
>> a really painful for me.
>>
>> I am using the directive:
>> SSLOptions  +StdEnvVars +ExportCertData
>>
>>
>> No problem, but when putting '+ExportCertData', I am unable to autosign
>> or revoke remotely any certificate I have the following error:
>> info: Creating a new SSL key for linux-install.fqdn
>> err: Could not request certificate: Error 400 on SERVER: header too long
>> Exiting; failed to retrieve certificate and waitforcert is disabled
>>
>> When using only:
>> SSLOptions  +StdEnvVars
>>
>> Everything works perfectly.
>>
>>
>> So here is the apache configuration file:
>> --
>> # you probably want to tune these settings
>> PassengerMaxPoolSize 12
>> PassengerPoolIdleTime 1500
>> # PassengerMaxRequests 1000
>> PassengerStatThrottleRate 120
>> RackAutoDetect Off
>> RailsAutoDetect Off
>> PassengerHighPerformance on
>>
>> Listen 8140
>>
>> 
>> ServerName puppetmaster.fqdn
>> ServerAlias puppetmaster
>>
>> ErrorLog /var/log/apache2/puppetmaster_**error.log
>> LogLevel warn
>> SetEnvIf Remote_Addr "::1" dontlog
>> CustomLog /var/log/apache2/puppetmaster_**access.log combined
>> env=!dontlog
>>
>> SSLEngine on
>> SSLProtocol -ALL +SSLv3 +TLSv1
>> SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+**MEDIUM:-LOW:-SSLv2:-EXP
>>
>> SSLCertificateFile  /data/local/puppet/ssl/certs/**
>> puppetmaster.fqdn.pem
>> SSLCertificateKeyFile   /data/local/puppet/ssl/**
>> private_keys/puppetmaster.**fqdn.pem
>> SSLCertificateChainFile /data/local/puppet/ssl/ca/ca_**crt.pem
>> SSLCACertificateFile/data/local/puppet/ssl/ca/ca_**crt.pem
>> # If Apache complains about invalid signatures on the CRL, you
>> can try disabling
>> # CRL checking by commenting the next line, but this is not
>> recommended.
>> SSLCARevocationFile /data/local/puppet/ssl/ca/ca_**crl.pem
>> SSLVerifyClient optional
>> SSLVerifyDepth  1
>> # The `ExportCertData` option is needed for agent certificate
>> expiration warnings
>> SSLOptions  +StdEnvVars +ExportCertData
>>
>> # This header needs to be set if using a loadbalancer or proxy
>> # RequestHeader unset X-Forwarded-For
>>
>> RequestHeader set X-SSL-Subject %{SSL_CLIENT_S_DN}e
>> RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e
>> RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e
>>
>> RackAutoDetect  On
>>
>> DocumentRoot /var/www/puppetmaster/public/
>> RackBaseURI /
>> 
>> Options None
>> AllowOverride None
>> Order allow,deny
>> allow from all
>> 
>> 
>> --
>>
>>
>> So any clue?
>>
>>
>> Regards,
>> JM
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/ap55DPU-uRsJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet Forge Happenings

[Mister Guru]

On 3 October 2012 22:26, llowder  wrote:

>
>
> On Wednesday, October 3, 2012 4:40:59 AM UTC-5, Mister Guru wrote:
>>
>>
>> On 3 Oct 2012, at 03:35, Ryan Coleman wrote:
>>
>> > Hello,
>> >
>> > If you weren't at PuppetConf or didn't catch my talk, here's a quick
>> > recap. I'm product owner for the Puppet Forge team which formed in
>> > July with 2 awesome engineers and an equally awesome designer. We're a
>> > team dedicated to the Forge and while ramping up, we've shipped three
>> > small improvements to the Forge that we hope you enjoy.
>>
>> Good Morning Ryan! Nice to hear news about the puppet forge! Product
>> owner huh?? Hey guys, now we know who to bug when it come to the Forge!
>>
>> >
>> > * Two lists were added to the homepage, highlighting recently active
>> > modules and contributors
>> > * An authors Gravatar is now displayed on each module page.
>> > * Today, the Forge will now retrieve information about GitHub issues
>> > and pull requests for a module for display on a module page. This has
>> > been automatically enabled for any module that lists GitHub as its
>> > 'Project Issue Tracker URL'.
>>
>> I noticed this last night, it was great. I was stuck with a module I
>> downloaded - I looked it up on the forge, and I noticed a link to the git
>> page - I then realised the problem was ummm. me, using the module in
>> the not right way. Most useful, saved me bashing my keyboard against the
>> computer
>>
>> > The team is just getting started. In the mean-time, we've been making
>> > improvements to our back-end services, user-testing new feature ideas
>> > and getting ready for the next wave of functionality. Our next
>> > features will focus on these two areas. A) Making it easy for you to
>> > contribute your module & B) Improve the information you have to make a
>> > decision about which module to use.
>> >
>> > As we develop and test ideas to address these goals, we want your
>> feedback!
>> >
>>
>> Ah yes - Point B - How about ranking by downloads? I'm sure you can pull
>> the stats from Forge servers. I'm assuming people log into the forge to do
>> some background before running public code, for compliance, and in my case
>> to suppress paranoia :)
>>
>> How about making the forge a bit more social - For example how about
>> being able to review a module, or write a comment about it on the forge?
>> That way, it's a bit easier for the author to get some feedback, and also
>> for others to get an idea how 'good' the module is.
>>
>> That would come in useful when some modules depend on others, if I'm
>> trying to install module A, and A insists on B, C, and D - I'd rather read
>> up on others, who went live straight away without testing and are
>> complaining about their broken systems  Oh, I mean, I'd like to read
>> the reviews from other users praising the awesomeness of the forge.
>>
>> Imagine that - In 6 months we could have modules writers competing
>> against each other - now that would be cool - Author rankings, (obviously
>> Puppet Labs Employees and modules excluded!) - and peer competition could
>> only lead to better code
>>
>
> +1 on all these ideas, though I don't think that the "number of downloads"
> metric is really useful, a high number could just mean that it is easrlier
> in the list and still a crappy module..
>
> But I do really like the idea of being able have some sort of community
> review on the modules, be that comments or even a simple up/down voting
> type system.
>


Hmm... Thinking about it, the download stats would be misleading - Good
point - Voting up and down would be a place to start.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet 3.0.0 and Augeas on Ubuntu Lucid 10.04

[Paul Tötterman]

Hi Eric,

Thank you. I filled in some more detail, and started following the bug. 
Let's continue there.

Cheers,
Paul

On Thursday, October 4, 2012 4:01:28 AM UTC+3, Eric Sorenson wrote:
>
> Hi Paul, I created a ticket to track this issue, thanks for posting the 
> trace output and manifest.
>
> http://projects.puppetlabs.com/issues/16772
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/3uiffjeeBA4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Testing exported resources

[David Schmitt]

On 03.10.2012 17:01, Pete wrote:

Hello,

Is there any way to test if a resources has been exported (without
realising it)?  The reason being - I don't want to realise a
nagios_service that's associated with a nagios_hostgroup until at least
one nagios_host belonging to that hostgroup exists (otherwise nagios
will refuse to start).

Any ideas?


With puppetdb collections can have complex queries. That could allow 
each nagios_host to collect its _services and _hostgroups.



Please report back with your results!


Best Regards, David

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] puppet client can't get certificate

[mike sonero]

Hi All,

I apologize for what I'm sure is a very boneheaded question, but I'm 
stuck.  I have a number of puppet agents all talking to the same master.  
Things worked great until at some point one of the agents stopped talking 
to the master - I'm not sure why that happened.  I decided to wipe its key 
from the master and "start fresh".  Unfortunately I haven't had any luck 
getting them to play nicely.

The agent is running 2.7.11.  The master is running 2.7.1.  They can ping, 
do hostname lookups, etc to each other.

When I attempt a manual update from the agent I see:
  ubuntu@agent:~$ sudo puppet agent --onetime --no-daemonize --verbose
  warning: peer certificate won't be verified in this SSL session
  warning: peer certificate won't be verified in this SSL session
  warning: peer certificate won't be verified in this SSL session
  Exiting; no certificate found and waitforcert is disabled

Doing a "sudo puppet cert list" on the master shows nothing pending.  
Running the server with debugging turned on shows the following:
  ubuntu@puppet:/var/lib$ sudo puppetmasterd --no-daemonize --debug 
--verbose
   ...startup...
  info: access[^/catalog/([^/]+)$]: allowing 'method' find
  info: access[^/catalog/([^/]+)$]: allowing $1 access
  info: access[^/node/([^/]+)$]: allowing 'method' find
  info: access[^/node/([^/]+)$]: allowing $1 access
  info: access[/certificate_revocation_list/ca]: allowing 'method' find
  info: access[/certificate_revocation_list/ca]: allowing * access
  info: access[/report]: allowing 'method' save
  info: access[/report]: allowing * access
  info: access[/file]: allowing * access
  info: access[/certificate/ca]: adding authentication no
  info: access[/certificate/ca]: allowing 'method' find
  info: access[/certificate/ca]: allowing * access
  info: access[/certificate/]: adding authentication no
  info: access[/certificate/]: allowing 'method' find
  info: access[/certificate/]: allowing * access
  info: access[/certificate_request]: adding authentication no
  info: access[/certificate_request]: allowing 'method' find
  info: access[/certificate_request]: allowing 'method' save
  info: access[/certificate_request]: allowing * access
  info: access[/]: adding authentication any
  info: Inserting default '/status'(auth) ACL because none were found in 
'/etc/puppet/auth.conf'
  info: Could not find certificate for 'agent.foo.com'
  info: Could not find certificate for 'agent.foo.com'
  info: Could not find certificate for 'agent.foo.com'

I tried generating a key on the server (even though it said there was no 
pending request) with:
  cert generate agent.foo.com

However, the client then reported:
  ubuntu@agent:~$ sudo puppet agent --onetime --no-daemonize --verbose 
--waitforcert 120
  err: Could not request certificate: The certificate retrieved from the 
master does not match the agent's private key.
  Certificate fingerprint: 51:E2:EC:3B:28:39:FB:24:95:38:AD:FE:D0:89:8C:93
  To fix this, remove the certificate from both the master and the agent 
and then start a puppet run, which will automatically regenerate a 
certficate.
  On the master:
puppet cert clean agent.foo.com
  On the agent:
rm -f /var/lib/puppet/ssl/certs/agent.foo.com.pem
puppet agent -t

I followed those instructions, but now am back at the beginning...

If anybody has ideas on things I might try I'd really appreciate it!  Sorry 
if I didn't include the right info.  /var/log/syslog seemed pretty empty.

Thanks,
- mike


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/4P4Iu7xlZIwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Could not load downloaded file /var/lib/puppet/lib/puppet/parser/functions/upcase.rb: Function upcase already defined

[nan]

Hi Guys,
I'ts my first time join this group and post a topic here. I recently 
encounter a quite strange issue in our production puppet env.
I have a VM installed a puppet agent(v 2.7.6) which works well before the 
master installed. After i installed a puppet master(v 2.7.11) with gem it 
reports below message in the /var/log/syslog:
Oct  3 23:40:24 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/is_array.rb: Function is_array 
already defined
Oct  3 23:40:24 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/reports/appstack.rb: Class Appstack is already 
defined in Puppet::Reports
Oct  3 23:40:24 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/parseyaml.rb: Function 
parseyaml already defined
Oct  3 23:40:24 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/member.rb: Function member 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/mysql_password.rb: Function 
mysql_password already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/downcase.rb: Function downcase 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/grep.rb: Function grep already 
defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/lstrip.rb: Function lstrip 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/is_mac_address.rb: Function 
is_mac_address already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/type.rb: Function type already 
defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/abs.rb: Function abs already 
defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/chomp.rb: Function chomp 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/validate_string.rb: Function 
validate_string already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/loadyaml.rb: Function loadyaml 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/validate_bool.rb: Function 
validate_bool already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/size.rb: Function size already 
defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/capitalize.rb: Function 
capitalize already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/unique.rb: Function unique 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/shuffle.rb: Function shuffle 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/reverse.rb: Function reverse 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/flatten.rb: Function flatten 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/validate_array.rb: Function 
validate_array already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/parsejson.rb: Function 
parsejson already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/is_numeric.rb: Function 
is_numeric already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/is_integer.rb: Function 
is_integer already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/values.rb: Function values 
already defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/functions/sort.rb: Function sort already 
defined
Oct  3 23:40:25 ubuntu puppet-agent[27445]: Could not load downloaded file 
/var/lib/puppet/lib/puppet/parser/