similar to: ANNOUNCE: 0.22.0

I''m a new puppet user. I can''t puppetmasterd to start. I searched this group for the error message I get, but found nothing. Any ideas? [root@puppet ~]# puppetmasterd undefined method `name'' for nil:NilClass Using the --debug switch and ruby''s --debug option shows the following: [root@puppet ~]# puppetmasterd --debug debug: Parsing /etc/puppet/puppet.conf

We have resources that, from time to time, are selected to be removed (unmanaged). When it comes to ssh keys, fstab... this leaves a lot of stuff behind that we don''t want. Is there a simple way to remove the unmanaged data so we can keep the systems clean. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

Hi! I want to manage all local user accounts on my Samba DC. So I add to my node two resources like this: resources {''user'': purge => true, unless_system_user => 999, } file {''/home'': ensure => directory, owner => ''root'', group => ''root'', mode => 0644, force => true, purge => true, recurse =>

http://projects.puppetlabs.com/issues/7600 I call this the "agent orange" option :) This works, purging all unmanaged hosts entries: resources { ''host'': purge => true, noop => true, } We should have a similar property for all (most?) types. Please comment on the ticket or reply here, whichever you prefer. Thanks! r P.S. This is in

Note, 0.21.0 wasn't a true release, the release script bombed out because an ifdef was missing, so here's 0.22.0. And even numbers are better than odd ones anyway, or something. Two fixes, the first one fixes the new tap button map option handling. It had a copy-paste error and was instead disabling the device (when set via the xorg.conf option). Second, when the first device was

Hello, My organization is currently running a complete production environment on Amazon EC2, and I''m now trying to implement some automations and scaling with puppet. I have several instances which I want them to be almost automatic, meaning that whenever is needed more instances will come up, and when they''re not needed they will be stopped. This should eventually be

Hi all, I''m trying to fix #594[1], and it looks like the problem only occurs when you specify other parameters (e.g., owner or mode). That is, Puppet will not purge managed files, and when you specify these parameters with ''recurse => true'', Puppet applies the parameters to all files in the directory, which means that all contained files are considered

Hi all, As requested by at least one person (and because I''d been thinking about it and figured it would be a good idea), I''ve just made it simple to use external node sources with Puppet. If you set ''external_nodes'' to a command (the default is ''none''), then Puppet will call that command and use it to configure nodes. The output of

I have the following define... define puppet::module_dir { if $name { include puppet file { "${puppetdir}/modules/${name}": ensure => directory, mode => 0755, purge => true, recurse => true, } } } I call it like so: puppet::module_dir { "main" } puppet::module_dir

Ok, given the statement on the web page about unlesssystemuser under Resources ( http://reductivelabs.com/projects/puppet/documentation/typedocs.html#resources), I assume that users can be purged. However, when I attempt to do this with resources { user: purge => true, noop => true } and what I get is: err: Found a bug: private method ''split'' called for nil:NilClass.

Hi all, This just keeps coming up, again and again, so I decided to take a few hours and break everyone''s configuration. Oh, wait, just kidding. :) Really, I''ve completely rewritten external node support. Here''s the changelog entry: Only ONE node source can be used -- you can use LDAP, code, or an external node program, but not more than one.

So I have the following: define nagios::service ( $nagios_template = ''service-template'', $host_name = $fqdn, $service_groups = '''', $contact_groups = $default_contact_group, $max_check_attempts = 3, $dependency = false, $dependent_host = $fqdn, $dependent_service = '''', $check_command = '''' ) {

At long last, 0.24.0 has been released. Look for your friendly packagers to package it up in the near future, but in the meantime you can download it: http://reductivelabs.com/downloads/puppet/puppet-0.24.0.tgz I''ll be walking the different release sites (RubyForge et al) and posting it there, too. Look for a related announcement later today on changes in development practices

I''m trying to setup dashboard as a node classifier w/puppet 2.6.14. Not sure why this is not working... In puppet.conf on the master I have: node_terminus = exec external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http:// localhost /usr/share/puppet-dashboard/bin/external_node The agent''s return: err: Could not retrieve catalog from remote server: Error 400 on SERVER:

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

----- Oorspronkelijk bericht ----- Van: "James Hogarth" <james.hogarth at gmail.com> Aan: "CentOS mailing list" <centos at centos.org> Verzonden: Donderdag 11 juni 2015 19:59:39 Onderwerp: Re: [CentOS] NetworkManager / wireless on latest Centos7 installs On 11 Jun 2015 13:28, <johan.vermeulen7 at telenet.be> wrote: > > > > ----- Oorspronkelijk

I''m using the external_nodes functionality to read in a flat file of a node''s configuration. Currently said file is a straight yaml file (just to keep things simple). The place I''m currently stuck is in doing some more advance node configurations and placing that data in the yaml file. For example: node ''foo'' { $var1 =

Beta 2 is now available for testing. ---------------------------------------------------------------------------- I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E ---------------------------------------------------------------------------- 1) This release includes all defect repair from Shorewall 4.5.17.1. 2) The following warning message could be emitted

Hi: I have a problem, on the same puppetmaster host, how to through the puppet dashboard management three environment: production, development and testing. Because in the puppet.conf file , ENC can only 1 configuration, like： External_nodes = / data/puppet-dashboard/bin/external_node External_node file configuration of the dashboard listen port. If I start the production on port

Use the new MMU_NOTIFY_MIGRATE event to skip GPU MMU invalidations of device private memory and handle the invalidation in the driver as part of migrating device private memory. Signed-off-by: Ralph Campbell <rcampbell at nvidia.com> --- drivers/gpu/drm/nouveau/nouveau_dmem.c | 15 ++++++++++++--- drivers/gpu/drm/nouveau/nouveau_svm.c | 21 +++++++++------------