Hi,
stumbled upon this again a couple of days ago. Turns out you *can* use
undef as a default value for parameters of a define and it will word in
Puppet 2.7.x.
With 2.6.8, no cigar. Your parameters get the string value "undef", and
defined($paramname) yields true.
Cheers,
Felix
On 12/02/2011 0
> Yes, if noone else does, I can sanitize an example from our environment,
> but I'll have to be back in the office.
This is how we do that: (learned from puppet btw)
create module users:
I will put a line +BEGIN and -END around files to show
boundaries. Don't put those lines in your files
hi all,
Please help me with the following:
I need to be sure aptitude update has run before puppet tries to
install mysql_percona:
in SHORT:
require => [
Apt::pin['libmysqlclient18_libmysqlclient-dev'],
Apt::source['Mysql_Percona'],
],
in LONG I've got these pieces:
Hi,
On 12/12/2011 11:13 AM, Alexander Swen wrote:
> result is now: Syntax error at '::pin'; expected ']' at
I think you need to uppercase that.
require => [ Apt::Pin[...] ]
HTH,
Felix
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group
>
>> In the first place, your definition is a bit screwey in that it cannot
>> be instantiated more than once (you would get a duplicate resource
>> error on File['sshd_config']). A definition creates a resource *type*
>> but you're using it as if it created a single resource.
>>
>> And that leads
On Dec 10, 12:20 am, Jo Rhett wrote:
> > On Dec 8, 1:07 pm, Jo Rhett wrote:
> >> I've found some problems due to the extremely random ordering puppet does.
> >> It is necessary for some of these items to all happen together, with no
> >> other random resources executed in between.
>
> On Dec
> I think you need to uppercase that.
>
> require => [ Apt::Pin[...] ]
Seems to do the trick! thanks!
--
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 g
On Dec 9, 5:47 pm, Alexander Swen wrote:
> > Nevertheless, if it's more important just to make it work right now,
> > then class users::beheerserver can override the $functie property of
> > the users::account instances it collects, like so:
>
> > Users::Account <| (othergroups == 'pep' or other
Please do not hijack existing threads. Create a new thread for a new
question.
John
--
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
Thanks! do i need any includes or similar to "Install" this?
On 12 Dec, 10:55, Alexander Swen wrote:
> > Yes, if noone else does, I can sanitize an example from our environment,
> > but I'll have to be back in the office.
>
> This is how we do that: (learned from puppet btw)
>
> create module use
Now thats wierd. I did. Different title, different body...how did it flag my
quetion to an old thread?
jcbollinger wrote:
>Please do not hijack existing threads. Create a new thread for a new
>question.
>
>
>John
>
>--
>You received this message because you are subscribed to the Google Group
It usually happens when you Reply to an existing email, change the
subject and body, but the Reply retains the original mail headers.
On 12/12/11 15:26, Marek Dohojda wrote:
Now thats wierd. I did. Different title, different body...how did it flag my
quetion to an old thread?
jcbollinger wr
I am told that somehow I hijacked a thread. I have no idea why that would
be since I replied to my own email. If it got attached to anything it
shouldn't be I apologize, for an email client snafu.
Anyway, any hints of what may be happening with my variables, why they are
hating me?
-Or
Is class 'hosts' declared in node 'env_prod' or node 'something'? For
this to work I would think it needs to be in node 'something', after the
variable declaration.
I'd try declare all your global variables at the top of your node
definitions first, then start including classes. Or, convert th
Last Friday, with a minimum of hiccups, we moved to using freight
(http://www.github.com/rcrowley/freight) to handle our repository at
apt.puppetlabs.com. One consequence of this move is that the debian
repository links will need to be updated. They should be changed to
the following:
deb http://a
On Fri, Dec 9, 2011 at 22:20, Jo Rhett wrote:
>> On Dec 8, 1:07 pm, Jo Rhett wrote:
>>> I've found some problems due to the extremely random ordering puppet does.
>>> It is necessary for some of these items to all happen together, with no
>>> other random resources executed in between.
>
> On
Here's a summary of issues that have been fixed in facter and puppet since
our last email. Due to the large number of issues, I'm only giving a one
line summary of each issue, and crediting individuals outside of Puppet
Labs for their contributions. More information about each issue can be
found at
On Mon, Dec 12, 2011 at 11:33:37AM -0800, Daniel Pittman wrote:
> On Fri, Dec 9, 2011 at 22:20, Jo Rhett wrote:
> >> On Dec 8, 1:07 pm, Jo Rhett wrote:
> >>> I've found some problems due to the extremely random ordering puppet
> >>> does. It is necessary for some of these items to all happen to
While analyzing the Puppet 2.7.6 from server as well as from target
nodes, I faced an error as followed:
[root@TARGET ~]# puppet apply 1.file.pp
notice: /File[/var/lib/puppet/facts]: Not removing directory; use
'force' to override
notice: /File[/var/lib/puppet/facts]: Not removing directory; use
Hi,
Are there still any known issues with puppet and ruby 1.9?
Or 1.8.7 is still the preferred version to use eith puppet?
Thanks
Alex
--
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@googlegr
Having a brain storm this morning I had a thought. This can be dangerous
at times.
I have an infrastructure where I am moving user authentication to be LDAP
based. Further I am working out how to create host groups in LDAP such that
I can group which user can log into what hosts. For instance I
On Mon, Dec 12, 2011 at 3:24 PM, Peter Berghold wrote:
>
> Has anybody managed to come up with a class or define that would query an
> LDAP server for a hostgroup and create the home directories and apply a
> skeleton to those directories based on the users in the host group?
>
If you're not usin
Fedora 14 has reached its end-of-life.
Puppet Labs will no longer be making packages for Fedora 14.
We offer Fedora 15 and 16 as they are still current.
see
http://lists.fedoraproject.org/pipermail/announce/2011-November/003010.html
Mike
--
You received this message because you are subscrib
Hi
In puppet 2.6.9, I'm trying to run it with passenger.
Details are as below:
1. Puppet: 2.6.9
2. Rack: 1.2.2
3. Passenger: 3.0.7
4. OS: CentOS 6
Error encountered at client:
-
err: Could not retrieve catalog; skipping run
err: Could not retrieve catalog from remote server: e
On Mon, Dec 12, 2011 at 12:12 PM, Lion wrote:
> While analyzing the Puppet 2.7.6 from server as well as from target
> nodes, I faced an error as followed:
>
> [root@TARGET ~]# puppet apply 1.file.pp
>
> notice: /File[/var/lib/puppet/facts]: Not removing directory; use
> 'force' to override
> noti
Just to re-iterate, it's working fine when I run puppetmaster from
the /etc/init.d/puppetmaster.
On Dec 13, 2:24 am, Ganesh Sharma wrote:
> Hi
>
> In puppet 2.6.9, I'm trying to run it with passenger.
> Details are as below:
> 1. Puppet: 2.6.9
> 2. Rack: 1.2.2
> 3. Passenger: 3.0.7
> 4. OS: CentO
G'day. I can't be sure this is your problem, but one difference
between the 2.6 series and the 2.7 series is that we changed the
master/agent interaction to use POST rather than GET for facts.
Specifically, we changed that because once you get too many bytes of
facts we would get a message that l
This is a maintenance release candidate of Puppet Dashboard. This release
resolves issues #6717, #7554, #9529, #10017, #10076, #11058, and
#11063. More details below.
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages a
On Dec 12, 8:42 am, Darin Perusich wrote:
> >> In the first place, your definition is a bit screwey in that it cannot
> >> be instantiated more than once (you would get a duplicate resource
> >> error on File['sshd_config']). A definition creates a resource *type*
> >> but you're using it as if
This release is the final maintenance release of the 2.6.x series of Puppet.
Further releases in this series will only be issues to address
security concerns.
This release is available for download at:
http://puppetlabs.com/downloads/puppet/puppet-2.6.13.tar.gz
See the Verifying Puppet Download s
On 12/12/11 12:41 PM, Darin Perusich wrote:
On Mon, Dec 12, 2011 at 3:24 PM, Peter Berghold
mailto:salty.cowd...@gmail.com>> wrote:
Has anybody managed to come up with a class or define that would
query an LDAP server for a hostgroup and create the home
directories and apply a sk
Hi Peter,
we used a different method here for linux hosts.
We put the groups we want to grant access to in /etc/security/access.conf ; ala:
[root@---]# egrep -v ^# /etc/security/access.conf
- : ALL EXCEPT root admin pci_sysadmin pci_devadmin : ALL
and then just add users to the group which perm
I've done some more development on my Puppet module that handles password
integration with Secret Server from Thycotic, and now it handles certificates
as well.
This allows you to have a 'password' define that ensures the password is stored
in SecretServer, and changes it on a regular basis:
p
The issue is that puppet can't find a user provider for your system, and
without that, it can't manage file ownership. What is the output of the
following?
$ ruby -e "require 'puppet/type/user';
Puppet::Type::User.provider_hash.each_pair do |k,v| puts
\"#{k}=#{v.suitable?.to_s}\" end"
Josh
On Fr
34 matches
Mail list logo
