similar to: --tags main not inheriting correctly?

I am wondering why my function works fine in R1.7.1 and R1.8.1 but not in R1.9.0. I thought it's an environment related problem but I can't solve it. >data weta jd 1 1 4 2 2 13 3 2 13 4 6 4 5 1 3 6 1 7 7 2 10 8 3 10 9 1 8 10 1 8 11 3 6 12 1 9 13 1 5 14 1 1 15 3 13 16 1 2 17 2 2 18 7 11 19 1 3 20 5 4

Hello all, I'm not sure if this is a bug. It's probably just an upgrade note. In summary I had no namespace section in my 2.0.17 config. When trying out 2.1rc5 no user could login because of a namespace error. 2.1rc5 adds a default namespace clause which broke my logins (It was noted in the changelog) I seemed to fix it by just putting this in the config file: namespace inbox {

https://bugzilla.samba.org/show_bug.cgi?id=7953 Summary: -x flag prevents symlink on source filesystem from overwriting dest dir Product: rsync Version: 3.0.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at

I asked on IRC but no one responded. Suppose the following: class basenode { include users include security class webserver { include apache, php } } node web1a { include basenode::webserver } Does node web1a imply including users and security specified under class basenode as well? Similarly, does this mean the same thing? class basenode { include users include security }

CALL FOR PAPERS ================================================================= LLVM-HPC: The LLVM Compiler Infrastructure in HPC http://llvm-hpc-workshop.github.io/ November 17th, 2014, New Orleans In conjunction with the 2014 ACM/IEEE Supercomputing Conference (SC'14)

I am running puppet 3.1.1 and have a site.pp which roughly looks like this site.pp: node basenode { include common } node ''server1'' inherits basenode { include role::appserver } node ''server2'' inherits basenode { include role::webserver } And my common module includes lots of different types of classes for creating base directories, adding in

Hi , I am using tags according to environments Eg: prd_env and stg_env How do i implement a default node Eg: node default inherits basenode { tag("prd_eu")|("stg_eu")) include general } The above does not work. I invoke the puppe agent puppet agent --test --noop --server=puppetmaster.domain.local -- tags=prd_env|stg_env Any ideas how i can allow both the

OS: FreeBSD 6.2-RELEASE Puppet: 0.22.4 OS: CentOS 5.0 Puppet: 0.23.2 Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, and when puppetd attempted to restart itself (using the init provider), it failed to start back up. Perhaps the init provider needs to close all file handles before executing the rc.d scripts? Additionally, I had puppetd update its

Hello, I am rather new to Puppet and am starting to test it out for use on a client''s servers. I am running into difficulty with node behavior. I want to specify a different firewall for every server. The default "basenode" works (applies the various files/functions/etc to all the servers just fine). However, when I specify the following (see nodes.pp, specifically),

Still very new to puppet, so go easy :-) Bit of a braindump I''m afraid, but I''d really appreciate any "Yep", "interesting", "No!!!" comments. I''ll start with an example - adding NTP support. This primarily consists of two configs: a) NTP clients - this is quite easy, it''s a templated file requiring the names of the NTP

I just installed puppet 3 (3.0.0-0.1rc3puppetlabs1) on a 32bit Ubuntu 12.04 ''server'' VM. I used the packages for the install. I then copied over my existing modules and manifests from my production 2.7.x puppet master, and also my hiera.yaml and hieradata/*. When I run puppet agent --test I get the following: Error: Puppet::Parser::AST::Resource failed with error

Hi I am a newbie to puppet. I have tried an initial config serving a simple file & dir from the puppetmaster, but the client will not mount. What obvious mistake am I making, I wonder? puppetmaster is a DNS alias for osiris3. Config files: [root@osiris3 puppet]# cat fileserver.conf [config] path /data/puppet/manifests/files allow *.pinnacle.co.uk [root@osiris3 puppet]# cat puppet.conf

I''m getting this on my client: Jun 14 15:21:26 s_sys@app09.fr.xxx.com puppetd[24751]: Could not retrieve catalog: stack level too deep on node app09.fr.twofish.com Jun 14 15:21:26 s_sys@app09.fr.xxx.com puppetd[24751]: Not using cache on failed catalog Since running puppetd in debug gives no useful info: info: Starting handler for Runner info: Starting server for Puppet version 0.24.8

hello guys, I am trying to incorporate run stages into my puppet setup. I''ve been working with this for a few days and I haven''t quite got the hang of it yet... When I attempt my puppet run this is the error I see: ------------------------------------------------ [root@chromews21 ~]# puppetd -t err: Could not retrieve catalog from remote server: Error 400 on SERVER:

Hello List, i''m running into an issue with puppet where I don''t know how to solve correctly. We''re managing applications and our monitoring (nagios) using puppet using the following schema: class nagios { // ensure nrpe ist installed // export a host definition nagios::check { ''ping'': } nagios::check { ''load'': } ...

I managed to build a reduced test case: ================== foo.m ================== #include <Foundation/Foundation.h> @interface BaseNode : NSObject <NSCoding, NSCopying> { } @end @implementation BaseNode @end int main(int argc, char **argv) { return 0; } ========================================== # clang -o foo -arch i386 -framework Foundation foo.m foo.m:8:1: warning:

Hi all, I am working on rewriting my entire puppet environment and try to ''fix'' ''Dynamic lookup'' as it will be deprecated in some time, but even after reading quite some docs and on the forum, it''s not really clear to me. What I have read so far, is that each variable must be fully-qualified or parameterized in a class. As a quick

Hi i am creating a template.pp for different OS.. Following is my template.pp file node basenode { case $operatingsystem { fedora: { include fedora } default: { include debian } } include baseapps, sshd, admin, default } <=== line 7 node default inherits basenode {} I receive an error. err: Could not parse for environment production: Syntax error

I am trying to configure puppet with LDAP repository . I have set puppet schema and I have also added node definition at LDAP. Here is my configuration details . ############################################################## Puppet.conf node_terminus = ldap ldapserver = 10.250.11.127 ldapbase = ou=Hosts,dc=xyz,dc=com ldapassword = secret

Hello, I''m configuring my linux server with puppet open and is ok. My question is the next; I''ve a declared in mi nodes.pp the next: [.............] node ''basenode'' { include ''baseos'' include ''motd'' import ''useradd.pp'' } #All nodes for my domain node /.*\.example\.com/ inherits