search for: olliesdad

Hello, I am trying to setup a template with data being passed in as a long string of data which is being returned via extlookup() i.e. $resolvers = "10.10.10.10 11.11.11.11.12.12.12.12" The template should split those up and put a nameserver entry per line in /etc/resolv.conf I have this in the template now:- <%=

Hello, Using the LVM module/providers from the forge I want to create a logical volume at the maximum size and I cannot work out how to do this. physical_volume -> volume_group -> logical_volume -> filesystem -> mount All works fine but you have to hard code the size for the logical volume. Anyone know if this is possible ? Thanks Paul -- You received this message because you

Hello, If I want to do something like this:- if $::lsbdistrelease >= 6.3 { SOMETHING } Do I have to convert lsbdistrelease from a string to a number with an inline template or some such ? Thanks Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email

Hello, Attempting to setup a CA primary/standby as well as seperate puppetmaster servers (all running Apache/Passenger) behind another Apache/Passenger type load balancer. Clients are not getting certs:- err: Could not request certificate: Could not intern from s: nested asn1 error Clearly an SSL issue but not something I know a great deal about. loadbalancer.conf # Puppet Load Balancing

Hello, A quick search showed some people may have got this working. Anyone got a Python (or Perl) script to parse the Puppet reports and put them into a human readable format ? Might be able to knock something together myself but not used PyYAML too much and might need some pointers. Thanks -- You received this message because you are subscribed to the Google Groups "Puppet

Trying to setup a volume group with puppet lvm and this:- volume_group { "my_vg": ensure => present, physical_volumes => "/dev/sdb /dev/sdc /dev/sdd", require => [ Physical_volume["/dev/sdb"], Physical_volume["/dev/sdc"], Physical_volume["/dev/sdd"] ] } Fails with this in the debug

How can I configure F5 load balancer to be infront of multiple puppet masters? The SSL will break as the server name if different, hostname of the VIP on the LB vs hostnames of each masters, right? Can you shed some light? Thanks. -- Hai Tao -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hello, Migrating some clients from an ancient client to a new infrastructure based on 2.7.11 these are RHEL boxes Some clients are hitting an issue [30/06/12 05:11:37 UTC] /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:733: [BUG] Segmentation fault [30/06/12 05:11:37 UTC] ruby 1.8.5 (2006-08-25) [x86_64-linux] [30/06/12 05:11:37 UTC] [30/06/12 05:11:37 UTC] Puppet SSL run return

Hello, Just kicking the tyres with PuppetDB (1.1.0) on a test setup with 100-odd nodes running only once an hour by default. Looking at the dashboard the catalog duplication is showing 0.0% which seems a little odd to me. Any way to track down why this is and how to correct it as presumably this is not desired behaviour. Cheers Paul -- You received this message because you are subscribed

Hello, Have a fully working setup with mostly Linux clients running on a 2.7.x master all is good. Trying to join Solaris clients to this master yields:- info: Creating a new SSL key for <FQDN> warning: peer certificate won''t be verified in this SSL session info: Caching certificate for ca warning: peer certificate won''t be verified in this SSL session warning: peer

Hello, As the 2.7 branch doesn''t seem to be available for RHEL4 (yes I know EOS next week) am trying to use a 2.6.11 client for our new Puppet infrastructure to replace the creaking one we have now. The POC setup is all running behind an F5 with a pair of CA''s and seperate pool of Puppet Masters. RHEL5/6 clients running 2.7.9 work fine. The older version on RHEL4 gives me SSL

Hello, On some machines being managed by Puppet I would like to perform targetted audit runs with "puppet -t --noop --tags audit" For better or for worse I am trying to do this with a separate module "audit" rather than add the audit => to the resources and use inheritence. i.e. class audit::resolver inherits resolver::config { notify{"Running audit on