similar to: Usability concern with overrides

Another override question: Is it possible to specify multiple overrides using a list/array? For example: User[games, baduser] { ensure => absent } I''ve tried various syntax manipulations, but nothing seems to work. Thanks, Trevor _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com

I believe this has already been discussed[1], but I''d like to add a bit more to that original discussion and see if anyone has any suggestions. Here''s what I''m trying to do: we have a set of very thorough "wipe" scripts that run every night on our workstations. I''d like to stash these into a class so that I can include them as a group: class wiped

I have this config: # BL00070 - Disable NFS service {["nfs","nfslock","netfs","portmap"]: ensure => stopped, enable => false, } user {"rpc": ensure => absent, provider => "useradd" } user {"rpcuser": ensure => absent, provider => "useradd" } file

This has been a "fun" issue. Basically, I''m trying to purge (ensure => absent) useless users and groups that I don''t need. The problem that I''m having, is that I can''t seem to determine a way to make sure that the users are deleted before the groups. For example: user { games: ensure => absent } group { games: ensure => absent } Now,

Hi, I''m running into a problem with the user type with puppet 0.20.1... this worked before with 0.19.x at least, not sure about 0.20. But I''ve got adduser.pp: <snip> define adduser($uid, $gid, $groups="users", $membership="minimum") { group { $name: gid => $gid, allowdupe => false, ensure

Hi all, I''m having problems making some manifest work, and it''s so simple that I don''t know where the issue is: I get this error message when trying to load this vhost.pp file: "Could not retrieve configuration: Syntax error at ''}'' in file /etc/puppet/manifests/classes/vhost.pp at line 9" define vhost ( $domain, $admin, $docroot, $enable )

I just updated to 0.22.2 and am running into a strange issue. I''m starting puppetmaster, and seeing this in my error log: err: /puppetconfig/reporting/File[/Library/Puppet/Generated/Server/var/reports]/ensure: change from absent to directory failed: Cannot create /Library/Puppet/Generated/Server/var/reports; parent directory /Library/Puppet/Generated/Server/var does not exist err:

This this definition: group { "puppettestgroup2": gid => 1235, ensure => present } user { "puppettestuser2": gid => "puppettestgroup2", uid => 1235, ensure => present } I see this: notice: Starting

Given the following: file { "/my/file": source => "puppet://server/path/to/some/file", ensure => absent } Puppet will copy /my/file to the host. What I was hoping was that ensure => absent would trump a source file. However, if we change the above slightly like this: file { "/my/file": source =>

On 21/04/19 17:12, Rowland Penny wrote: > On Sun, 21 Apr 2019 08:59:01 +0930 > Stephen Davies via samba <samba at lists.samba.org> wrote: > >> I have been a bit divorced from Samba for a while and am stumped by a >> recently seen issue. >> >> My Samba server (V4.8.3) is Centos 7 and the remote clients are >> windoze boxes at the other end of a VPN

Has anyone done rollbacks with puppet? The story goes that last night I pushed a change out, which intentionally changed the way certain services where managed. The change involved pushing out a few files, cronjobs, etc., which was okay until it was discovered there was a bug with the service. My configurations are kept in subversion and rolling back to a previous configuration would have

Darned thing is suddenly failing. We had a reboot last night, and I changed a couple of files today too, so either one could somehow be responsible. But I can''t figure out how from this crash. First I noticed that my changes weren''t updating. Then I noticed that puppet wasn''t running. Then I found that it won''t, in fact, run. /selinux contains only a

I''ve been going through Pat''s example story and noticed that there was no checking for a bad login. I assume this is because that would have made the article bigger and more complicated than it needed to be. So the question that comes of of this is: How do folks normally handle the negative case? My plan was to just use another scenario, but as a new person to BDD/TDD,

Since I had my type development epiphany a couple of days ago, I''ve decided to write down my understanding of developing simple types, at http://reductivelabs.com/trac/puppet/wiki/PracticalTypes. I''d appreciate comments from people who already know how to develop types as to correctness, and also comments from people who are new to type development about whether it''s a

I have a situation where I''d like to perform some actions when a node is removed from a class. I have a few (homegrown) services that install ssh keys in authorized_keys and it''s possible that a node may have the service enabled and disabled during it''s lifetime. When disabled I''d like to clean up the ssh keys for security reasons. This brings up the broader

Hi, I just got my local yum repo setup so that I can use puppet to install packages... and it looks like something is not working. <snip> Tue Sep 19 02:13:05 PDT 2006 Puppet (notice): Starting configuration run Tue Sep 19 02:13:10 PDT 2006 //default/java/package=jdk/ensure (err): change from absent to latest failed: Could not update: Could not execute ''/usr/bin/yum -y install

I expect that there is something simple that I am missing, but if I set a file to "ensure => absent", puppet is actually just renaming it to "${ORIGINALNAME}puppet" (i.e., appending puppet to the name). Did I forget to turn off a debug flag somewhere? The file definition that I am using is just: file { "/usr/lib/xen-tools/debian.d/55-create-dev": ensure =>

file { "/var/log/syslog": target => "/var/log/messages" } generates the following error: err: //henson/stanford/syslog/file=/var/log/syslog: Failed to retrieve current state: undefined method `should'' for false:FalseClass

Ok, so I''m obviously doing something wrong here. This is running puppet 0.22.2 on a centos 4 update 4 box. When I try running this test - mount { bigdisk: ensure => mounted, device => ''bigserver:/bigdisk'', fstype => nfs, name => ''/bigdisk'', dump => "0", pass => "0", options =>

I have a recipe that I''m ensuring that I remove rpms that may be installed by CentOS/RHEL before I install the MySQL.com rpms. the recipe and logs are listed below. For testing I have mysql-* rpms already installed. Is there a method to force specific order to run the recipe? What am I doing wrong? # install mysql rpms (not CentOS/RHEL vesions) # PROCESS: # - removes any CentOS/RHEL