Hi,
> > So, the tags are not inherited. Each node prints the tag that is
> > declared in its own node, but not those from the parent or the
> > children. I have also tried to do manual tags, and they are not
> > inherited either.
> >
> > Am I doing something wrong, or is "tagging" not well docume
Hi Gonzalo,
> I tried to implement a second Puppet server as a "staging" server with
the idea of being able to run puppet in dry run mode against this staging
server.
Have you looked at environments for differentiating between staging and
production instead of separate puppet masters?
> I ran
Hi All,
I am very new to puppet and would like to know how to
distribute some files to all the puppet client.
i used the following to do my task.
edited the site.pp file to below.
class sudo {
file { "/etc/sudoers":
owner => root,
group => root,
mode => 44
My module now depends on the puppetlabs/puppet-apt module for supporting
Debian/Ubuntu hosts, doing this however broke all my debian/ubuntu related
rspec-puppet tests.
Is there a reasonable way to mock out resources (like apt::source, etc) to just
test that my classes are doing what they should be
Whenever I use puppet agent --test on a client I get the error "err: Failed
when searching for node sage.jack: Failed to find sage.jack via exec:
Execution of '/home/ldigitaldash/classifier sage.jack' returned 1:" if i
run the enc as a command /home/ldigitaldash/classifier sage.jack I get this
That's basically OK, but try
source => "puppet:///files/etc/sudoers"
instead. This will link automatically to your local host's Puppet master. If
you are already working with modules, you should work with
source => "puppet:///modules//etc/sudoers"
Your file 'sudoers' must then be below a direc
Hi Bernd,
I get the following error on doing what you said.
root@client1:~# puppet agent --test --server='rover.test.com'
info: Caching catalog for client1.test.com
info: Applying configuration version '1331112706'
err: /Stage[main]/Sudo/File[/etc/sudoers]: Could not evaluate: Error
400 on SER
Niraj,
I'll give you an example that works for me. But it uses modules. If you don't
so far, you really should start.
Given this structure below an environment below '/etc/puppet' on my Puppet
master:
.
├── manifests
├── modules
│ ├── backup
│ │ ├── files
│ │ └── manifests
│ ├── ex
Hi,
I have the following basic node definition
node 'mynode' {
class { 'oracle::server': }
class { 'oracle::patch::patchA':
require => Class['oracle::server'],
}
class { 'oracle::patch::patchB':
require => Class['oracle::server'],
}
oracle::
Hello
Is it possible to configure a 2.6.6 Puppet Client so that the reports
that are sent to the PuppetMaster is in "Report Format 1" instead of
"Report Format 2" ?
Cheers,
Kalle Larsson
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post
Hi Gonzalo,
> Has anyone done this sort of thing? How'd you get around the SSL issues? I
> could use the same CA cert on both Puppet servers but I assume that won't
> work as the hostnames are different?
I am actually doing this, but on the same puppet server. What I have done is
the following:
On Mar 6, 12:40 pm, "chris_sny...@sra.com"
wrote:
> I have to say I'm very disapointed right now with the state of Puppet. It
> seems that the official documentation is pushing parameterized classes but
> at the same time there are very serious drawbacks to their usage.
I agree that that is a
On Tue, Mar 6, 2012 at 11:20 PM, Gonzalo Servat wrote:
> Hi All,
>
> I tried to implement a second Puppet server as a "staging" server with the
> idea of being able to run puppet in dry run mode against this staging
> server.
As other have suggested, environments might be an easier way to do this
I have been using the Dashboard facility for assigning string values to
keys with great glee. It solves a number of support issues that I was
dealing with in a very neat fashion.
I did a google search on "puppet dashboard arrays" and found that there had
been some discussion about this and a feat
On Mar 6, 1:00 pm, Justin Lloyd wrote:
> John,
>
> I'm running into some snags of my own and your explanations have been
> helpful. However, I'd like to ask if you can comment a bit more on the
> emphasis Puppet Labs has on parameterized classes versus include. For one,
> I'm thinking of modules
On Wed, Mar 7, 2012 at 4:20 AM, Stefan Schulte
wrote:
> Hi,
>
> I have the following basic node definition
>
> node 'mynode' {
> class { 'oracle::server': }
> class { 'oracle::patch::patchA':
> require => Class['oracle::server'],
> }
> class { 'oracle::patch::patchB':
On Tue, Mar 6, 2012 at 8:03 PM, Jack Harris Jr wrote:
> Whenever I use puppet agent --test on a client I get the error "err:
> Failed when searching for node sage.jack: Failed to find sage.jack via
> exec: Execution of '/home/ldigitaldash/classifier sage.jack' returned 1:"
> if i run the enc as a
A colleague of mine has pointed out that to post to Google Groups, he
must give his mobile phone number to Google to send an SMS or to call
him so that he can create a Google account.
Are there any alternatives? Thanks.
--
You received this message because you are subscribed to the Google Groups
On Tue, Mar 6, 2012 at 10:53 PM, R. Tyler Croy wrote:
> My module now depends on the puppetlabs/puppet-apt module for supporting
> Debian/Ubuntu hosts, doing this however broke all my debian/ubuntu related
> rspec-puppet tests.
>
> Is there a reasonable way to mock out resources (like apt::source
Hello group,
I have a Tomcat class which takes a java package name as a parameter.
The parameter looks like openjdk-1.2.3 or sunjava-2.3.4. The purpose of the
parameter is that it sets a configuration option in the Tomcat
configuration to tell it which java binary to use.
I need to determine whi
On Wed, Mar 7, 2012 at 8:22 AM, jimbob palmer wrote:
> A colleague of mine has pointed out that to post to Google Groups, he
> must give his mobile phone number to Google to send an SMS or to call
> him so that he can create a Google account.
>
> Are there any alternatives? Thanks.
Has he or she
On Wed, Mar 7, 2012 at 7:53 AM, Peter Berghold wrote:
> I have been using the Dashboard facility for assigning string values to keys
> with great glee. It solves a number of support issues that I was dealing
> with in a very neat fashion.
>
> I did a google search on "puppet dashboard arrays" and
On Mar 7, 2:37 am, Pablo Fernandez wrote:
> > On the other hand, I think your expectations are incorrect. It is
> > "enclosed" objects that are documented to also get tagged, and I would
> > not consider a node definition to be "enclosed by" another that
> > inherits from it.
>
> So, is there n
OK: that was the impression I was under after reading everything that was
posted to the feature request for this...
--
Peter L. Berghold
Owner, Shark River Technical Solutions LLC
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post
Hi,
[...]
> I know I'm doing something stupid, but I can't figure it out. Any help
> greatly appreciated.
>
>
Look this small example:
matti@acrux ~ $ cat - | puppet 2> /dev/null
$array = ['abc', 'def', 'xyz']
define iterator {
notice "You have said: ${name}"
}
iterator { $array: }^D
notic
On Wed, Mar 07, 2012 at 08:15:54AM -0800, Nan Liu wrote:
> On Wed, Mar 7, 2012 at 4:20 AM, Stefan Schulte
> wrote:
> > Hi,
> >
> > I have the following basic node definition
> >
> > node 'mynode' {
> > class { 'oracle::server': }
> > class { 'oracle::patch::patchA':
> > require
On Wed, Mar 7, 2012 at 12:15 PM, Stefan Schulte
wrote:
> On Wed, Mar 07, 2012 at 08:15:54AM -0800, Nan Liu wrote:
>> On Wed, Mar 7, 2012 at 4:20 AM, Stefan Schulte
>> wrote:
>> > Hi,
>> >
>> > I have the following basic node definition
>> >
>> > node 'mynode' {
>> > class { 'oracle::serve
On Wed, Mar 7, 2012 at 8:44 AM, Peter Berghold wrote:
> OK: that was the impression I was under after reading everything that was
> posted to the feature request for this...
Actually, I've mistakenly filed it as a bug. If you use json, you can
parse the parameter via parsejson available in stdli
Just wanted to add that if you decide to use environments, and you use
an external node classifier, you have to set the environment in each
node's puppet.conf for everything to work. I use foreman and set the
environment using a puppet.conf template with the undocumented (I
think) foreman_env varia
I recently noticed that the Windows host where I installed the Puppet agent
for testing was thrashing the CPU.
The culprit ended up being Ruby.exe *32 - "Ruby interpreter (CUI) 1.8.7.334
[i386-mingw32]". This is actually being launched by the puppet-agent
service in Windows. The CPU on the host
On Wed, Mar 7, 2012 at 2:58 PM, Matt Mencel wrote:
> I recently noticed that the Windows host where I installed the Puppet
> agent for testing was thrashing the CPU.
>
> The culprit ended up being Ruby.exe *32 - "Ruby interpreter (CUI)
> 1.8.7.334 [i386-mingw32]". This is actually being launched
Hi Matt,
On Wed, Mar 7, 2012 at 2:58 PM, Matt Mencel wrote:
> I recently noticed that the Windows host where I installed the Puppet
> agent for testing was thrashing the CPU.
>
> The culprit ended up being Ruby.exe *32 - "Ruby interpreter (CUI)
> 1.8.7.334 [i386-mingw32]". This is actually bein
yup that was it, weird. teach me not to check process tables first. :)
On Tue, Mar 6, 2012 at 1:24 PM, Gary Larizza wrote:
> Do you have more than one mcollectived instances in the process table?
>
> `ps aux | grep [m]collective`
>
> I've seen this before when I had started two instances of the
Is the source file readable by the puppet user?
On 7 March 2012 23:06, Bernd Adamowicz wrote:
> Niraj,
>
> I'll give you an example that works for me. But it uses modules. If you
> don't so far, you really should start.
>
> Given this structure below an environment below '/etc/puppet' on my Pupp
I managed to trigger this behavior when I realized the readline package in
the ruby_devel class instead of specifying it. It appears that the resource
chain in the rvm class does not include the realized resource. Is this the
current expected behavior? I'm running 2.7.11 on the client and serve
I'm excited to announce the release of the puppetlabs-apt module to the
Puppet Forge.
http://forge.puppetlabs.com/puppetlabs/apt
Originally a community members module, Puppet Labs forked it, added to it
and collaborated with other awesome community members that have been
hacking on it ever si
I can delete a node in dashboard fine, but when I do a search with the
Inventory Search the node shows up again and also then shows up under
"Unreported". Any way to get rid of all references to the node?
Thanks,
--
Romeo
--
You received this message because you are subscribed to the Google Gr
On Wednesday, March 7, 2012 11:19:19 AM UTC-5, Jeff McCune wrote:
>
> On Tue, Mar 6, 2012 at 8:03 PM, Jack Harris Jr wrote:
>
>> Whenever I use puppet agent --test on a client I get the error "err:
>> Failed when searching for node sage.jack: Failed to find sage.jack via
>> exec: Execution of '
38 matches
Mail list logo
