[Puppet Users] Re: Can Puppet interact with perl script user input fields?
The script is several thousand lines of code. Definitely not easier than Guzman Braso's suggestion :-) Although I'm surprised that Puppet doesn't have any supported way of shell interaction with scripts? On Oct 5, 4:01 am, Peter Brown rendhal...@gmail.com wrote: It's probably easier in the long run to work out what that script does and replicate those settings in your samba puppet class. On 4 October 2012 19:34, Jon Skarpeteig jon.skarpet...@gmail.com wrote: I'm trying to automate deployment of centrify-samba, which has a adbindproxy.pl setup script attached. This script expects user input (where 9 out of 10 options can be defaulted). Is there any way for Puppet to preconfigure the inputs for this scripts, and mimic user behavior by supplying this information? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Massive Import/Include
As regards your 3 proposals : - that it would probably all need to go into one YAML file = it will be the same than insert all my config in the manifest.pp, and it's not interesting to me - you could put it in an hiera data store = i don't know this method yet - You could write a custom function that reads the directory = i think it's the better choice Thanks for answering. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/qF7rOFmRyMAJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: activerecord and puppet-3.0.0
On 04/10/12 17:30, Andy Parker wrote: I encountered this issue yesterday when trying to reproduce another issue. I discovered that you need to be using activerecord 3.0.11. Later versions don't seem to work (error with a stack too deep) and earlier versions don't seem to work (error with uninitialized constant ActiveRecord). Interesting. On my *old* puppetmaster (2.7 upgraded to 3.0) I'm running activerecord-2.1.1-2 from the puppetlabs-deps repo. It doesn't work, failing with the uninitialized constant ActiveRecord error. On my *new* puppetmaster (fresh install of 3.0 on a blank box) it is also running activerecord-2.1.1-2 from the puppetlabs-deps repo. It *does* work. Both puppetmasters are running identical puppet configs. The *old* puppetmaster has these gems: activemodel (3.2.8, 3.2.3, 3.0.9) activerecord (2.1.1) activesupport (3.2.8, 3.2.3, 3.0.9, 2.1.1) arel (3.0.2, 2.0.10) builder (3.0.0, 2.1.2) hiera (1.0.0) i18n (0.6.0, 0.5.0) multi_json (1.3.2) rake (0.8.7) tzinfo (0.3.33, 0.3.29) The *new* puppetmaster has these: activerecord (2.1.1) activesupport (2.1.1) Possibly there's an issue with the multiple versions of activesupport? I don't really know anything about ruby - I'm merely a user of puppet. Cheers, Jonathan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet 2.7 v 3.0 in the PuppetLabs yum repo
Hi Chad * Take a look at the yum versionlock plugin. My life has been much simpler since I deployed it. For a while I was excludeing puppet and friends in yum.conf, but that was a real pain. The versionlock plugin pins a package at the version you want, and then you can update when ready. When I do that I get # yum versionlock add puppet-server-2.7\* puppet-2.7\* # yum versionlock list Loaded plugins: fastestmirror, security, versionlock 0:puppet-server-2.7.19-1.el6.* 0:puppet-2.7.19-1.el6.* versionlock list done which I suppose will lock it to 2.7.19 and never to 2.7.20. Is it possible to lock it to 2.7.x ? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/MLdbBDAqqgYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Could not find certificate for - Puppet 3.0.0-rc4
I'm receiving the message: Could not find certificate for ... on the server when I try to run the agent on an old server where I was trying to make some experimentation. I've removed cert and keys from clent and runa clean on the server. The /etc/hosts in the server is configured correctly. Have no idea on what happened. Also as a side notice all the documentation aroun is perhaps referring to 2.x and 3.x uses a different syntax puppet ca instead of puppetca. Any hints? Thanks -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/KYFDD_sa8yoJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Could not find certificate for - Puppet 3.0.0-rc4
Ok solved by deleting all the /var/lib/puppet/ssl content in the agent. made a puppat run and the master accepted the client and autosigned all and all went correctly. BUT I went to see if in the master issuing the command: puppet ca list --all or --signed There was to find the host but ... nothing just the puppetmaster and the CA certs... WHY I'm not getting the thing. Thanks Il giorno venerdì 5 ottobre 2012 11:23:59 UTC+2, Luca Gioppo ha scritto: I'm receiving the message: Could not find certificate for ... on the server when I try to run the agent on an old server where I was trying to make some experimentation. I've removed cert and keys from clent and runa clean on the server. The /etc/hosts in the server is configured correctly. Have no idea on what happened. Also as a side notice all the documentation aroun is perhaps referring to 2.x and 3.x uses a different syntax puppet ca instead of puppetca. Any hints? Thanks -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/48yOd8ELwbUJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
RE: [Puppet Users] Re: Can Puppet interact with perl script user input fields?
The centrify script may be thousands of lines, but it doesn't do that much. A lot of it is for user interaction and multiple OS stuff. At my last company we used centrify for authentication. It was less then a dozen commands to setup. A bit longer than that once put into puppet. If you really want to interact with the script instead, Linux has programs for doing this. There is no reason to duplicate this in the puppet core, when this is not the recommended way of doing things. If the script is installing things and puppet doesn't know about everything that is installed and modified, it can't manage them. Goes against the primary design. Steven Date: Thu, 4 Oct 2012 23:55:55 -0700 Subject: [Puppet Users] Re: Can Puppet interact with perl script user input fields? From: jon.skarpet...@gmail.com To: puppet-users@googlegroups.com The script is several thousand lines of code. Definitely not easier than Guzman Braso's suggestion :-) Although I'm surprised that Puppet doesn't have any supported way of shell interaction with scripts? On Oct 5, 4:01 am, Peter Brown rendhal...@gmail.com wrote: It's probably easier in the long run to work out what that script does and replicate those settings in your samba puppet class. On 4 October 2012 19:34, Jon Skarpeteig jon.skarpet...@gmail.com wrote: I'm trying to automate deployment of centrify-samba, which has a adbindproxy.pl setup script attached. This script expects user input (where 9 out of 10 options can be defaulted). Is there any way for Puppet to preconfigure the inputs for this scripts, and mimic user behavior by supplying this information? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Are future versions of facter and hiera 2.7.x backwards compatible?
Hi, I am using puppet 2.7 so I am wondering if the new facter-1.6.13-1 hiera-1.1.0 and future versions are compatible with puppet 2.7 ? Hugs, Sandra -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/yeYeMvKfbPgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] How to remove warnings related to Resource references should now be capitalized when starts with number?
Hi Guys! I want to clean warning messages: *warning: Deprecation notice: Resource references should now be capitalized*... It is related to following line: * - appcmd::32Bit['32BitappPool']* If I try to change any piece of the code using caps. for the fisrt letter, a syntax error is displayed. * err: Could not parse for environment production: Syntax error at ':'; expected '}' * Any suggestion? (The main issue is that the reference values start with numbers. With the refers that start with letters we have no problem, 'cause we know the structure) Thnx! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Oai34whey_8J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Remove directory
Here's one for you!
We're rolling out some zip files to our servers using Puppet, there's an
exec that unzips them, the zip file is then deleted. I need to remove the
old versions of the unzipped directory using Puppet when we rol out a newer
version.
So, on my client/node machine I have the below directories.
/opt/1234
/opt/12345
/opt/123456
What I need to do, is rm the the above directories when we roll out
1234567.zip. When the newest directory (1234567) is unzipped, the Puppet
exec sym links it to /opt/java. So could I remove the older directores that
are not sym linked?
Maybe using:
tidy { tidy_opt:
path = /opt/,
age = 1d,
backup = false,
matches = [ some nice ruby here that finds the non sym linked
directories?? ],
}
Hope this makes sense?
Thanks,
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/nq3bxtqSYNwJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Hiera problem: Can't convert Symbol into String
Have you tried,
---
family: prod
cluster: prod
compresslogs: true
?
On Monday, 23 July 2012 05:15:02 UTC+2, Aaron Nichols wrote:
All,
I have found very few references to this error so I'm guessing I must
be doing something wrong. I have just started using hiera and am trying to
use it in the simplest way possible, I have a class that looks like this:
class app_users2($compresslogs = hiera('compresslogs')) {
#Setup Cronjob for compressing app logs
if $compresslogs == true {
file { /etc/cron.daily/copyLogs.cron:
mode = 750,
ensure = present,
alias = compresslogscron,
source = puppet:///modules/app_users2/copyLogs.sh
}
}
}
For the node I'm running this on, hiera returns 'true' for that value when
I test it out:
$ hiera -c hiera.yaml compresslogs loc=sd type=app
true
I am using the yaml hiera backend and the yaml file this is configured in
looks like this:
---
family : prod
cluster : prod
compresslogs : true
However, when I try to execute the manifests either on the host or test
them using cucumber-puppet I get the following error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
can't convert Symbol into String at
/etc/puppet/modules/app_users2/manifests/init.pp:2 on node xyz
I have tried quoting, unquoting the data in the yaml file in the
conditional in the class. I've tried calling hiera as a parameter to the
class, also just as part of the conditional ( if hiera('compresslogs') ==
true ) etc. It appears that anytime I try to reference that value from
puppet it throws this error.
I have found a few references in IRC logs to others having this problem
but they all stated Oh, I figured it out without explaining how - so I'm
a bit stuck.
I am running the following hiera versions on the puppetmaster:
hiera-puppet-1.0.0-0.1rc1.el5
hiera-1.0.0-0.1rc3.el5
And the puppetmaster is running puppet v. 2.7.6.-2. I also tried updating
the puppet version on my host running cucumber-puppet to 2.7.18 and it
continues to throw this error.
Any help would be greatly appreciated.
Thanks,
Aaron
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/w_yzv9P9fZMJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppet client can't get certificate
Hi mate, I use Puppet 2.6 but in this situation would run: From puppetmaster puppetca --revoke agent.foo.com puppetcat --clean agent.foo.com From agent rm -rf /var/lib/puppet/ssl puppetd --waitforcert 30 --server puppetmaster -v From puppetmaster puppetca --sign agent.foo.com On Thursday, October 4, 2012 4:14:14 AM UTC+1, mike sonero wrote: Hi All, I apologize for what I'm sure is a very boneheaded question, but I'm stuck. I have a number of puppet agents all talking to the same master. Things worked great until at some point one of the agents stopped talking to the master - I'm not sure why that happened. I decided to wipe its key from the master and start fresh. Unfortunately I haven't had any luck getting them to play nicely. The agent is running 2.7.11. The master is running 2.7.1. They can ping, do hostname lookups, etc to each other. When I attempt a manual update from the agent I see: ubuntu@agent:~$ sudo puppet agent --onetime --no-daemonize --verbose warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session warning: peer certificate won't be verified in this SSL session Exiting; no certificate found and waitforcert is disabled Doing a sudo puppet cert list on the master shows nothing pending. Running the server with debugging turned on shows the following: ubuntu@puppet:/var/lib$ sudo puppetmasterd --no-daemonize --debug --verbose ...startup... info: access[^/catalog/([^/]+)$]: allowing 'method' find info: access[^/catalog/([^/]+)$]: allowing $1 access info: access[^/node/([^/]+)$]: allowing 'method' find info: access[^/node/([^/]+)$]: allowing $1 access info: access[/certificate_revocation_list/ca]: allowing 'method' find info: access[/certificate_revocation_list/ca]: allowing * access info: access[/report]: allowing 'method' save info: access[/report]: allowing * access info: access[/file]: allowing * access info: access[/certificate/ca]: adding authentication no info: access[/certificate/ca]: allowing 'method' find info: access[/certificate/ca]: allowing * access info: access[/certificate/]: adding authentication no info: access[/certificate/]: allowing 'method' find info: access[/certificate/]: allowing * access info: access[/certificate_request]: adding authentication no info: access[/certificate_request]: allowing 'method' find info: access[/certificate_request]: allowing 'method' save info: access[/certificate_request]: allowing * access info: access[/]: adding authentication any info: Inserting default '/status'(auth) ACL because none were found in '/etc/puppet/auth.conf' info: Could not find certificate for 'agent.foo.com' info: Could not find certificate for 'agent.foo.com' info: Could not find certificate for 'agent.foo.com' I tried generating a key on the server (even though it said there was no pending request) with: cert generate agent.foo.com However, the client then reported: ubuntu@agent:~$ sudo puppet agent --onetime --no-daemonize --verbose --waitforcert 120 err: Could not request certificate: The certificate retrieved from the master does not match the agent's private key. Certificate fingerprint: 51:E2:EC:3B:28:39:FB:24:95:38:AD:FE:D0:89:8C:93 To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate. On the master: puppet cert clean agent.foo.com On the agent: rm -f /var/lib/puppet/ssl/certs/agent.foo.com.pem puppet agent -t I followed those instructions, but now am back at the beginning... If anybody has ideas on things I might try I'd really appreciate it! Sorry if I didn't include the right info. /var/log/syslog seemed pretty empty. Thanks, - mike -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/UYOw8wirADsJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Need help with rspec-puppet
Hello Everyone,
I am fairly new to puppet and I would like to run som unit tests. I hope
rspec is the right tool for it. Unfortunately, after setting it up, when I
try to execute it I receive the following error:
Failures:
1) helloworld
Failure/Error: it { should include_class('helloworld') }
Puppet::Error:
Error converting value for param 'deviceconfig': Could not find
value for $confdir on node puppet-demo
# ./spec/classes/helloworld_spec.rb:8
Thiss error pops up for any test I try.
I wasn't able to find a solution yet. Can you please give me any advice?
Thank you.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/nhblHh4eNsQJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Dashboard inventory search problems.
I'm using Dashboard 1.2.10 on an Ubuntu 10.04 LTS system, and Puppet 2.7.19
When I do an inventory search, I get a blank screen.
In the logs, I found the following:
Processing NodesController#search (for X.X.X.X at 2012-10-05 08:44:57) [GET]
Parameters: {action=search, controller=nodes,
search_params=[{fact=OSFamily, comparator=eq, value=Debian}]}
Errno::EIO (Input/output error):
/usr/lib/ruby/1.8/net/http.rb:564:in `write'
/usr/lib/ruby/1.8/net/http.rb:564:in `warn'
/usr/lib/ruby/1.8/net/http.rb:564:in `connect'
/usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
/usr/lib/ruby/1.8/net/http.rb:542:in `start'
lib/puppet_https.rb:18:in `make_ssl_request'
lib/puppet_https.rb:33:in `get'
app/models/node.rb:85:in `find_from_inventory_search'
app/controllers/nodes_controller.rb:44
app/controllers/nodes_controller.rb:40:in `search'
sass (3.1.2) [v] rails/./lib/sass/plugin/rack.rb:54:in `call'
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:82:in `start'
Rendering /usr/share/puppet-dashboard/public/500.html (500 Internal Server
Error)
Any ideas as to the cause?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/G1TyOXTlJKsJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Dashboard inventory search problems.
Sounds like this bug:
http://projects.puppetlabs.com/issues/14974
On 12-10-05 10:22 AM, llowder wrote:
I'm using Dashboard 1.2.10 on an Ubuntu 10.04 LTS system, and Puppet 2.7.19
When I do an inventory search, I get a blank screen.
In the logs, I found the following:
Processing NodesController#search (for X.X.X.X at 2012-10-05 08:44:57) [GET]
Parameters: {action=search, controller=nodes,
search_params=[{fact=OSFamily, comparator=eq,
value=Debian}]}
Errno::EIO (Input/output error):
/usr/lib/ruby/1.8/net/http.rb:564:in `write'
/usr/lib/ruby/1.8/net/http.rb:564:in `warn'
/usr/lib/ruby/1.8/net/http.rb:564:in `connect'
/usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
/usr/lib/ruby/1.8/net/http.rb:542:in `start'
lib/puppet_https.rb:18:in `make_ssl_request'
lib/puppet_https.rb:33:in `get'
app/models/node.rb:85:in `find_from_inventory_search'
app/controllers/nodes_controller.rb:44
app/controllers/nodes_controller.rb:40:in `search'
sass (3.1.2) [v] rails/./lib/sass/plugin/rack.rb:54:in `call'
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
/usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
/usr/lib/ruby/1.8/webrick/server.rb:82:in `start'
Rendering /usr/share/puppet-dashboard/public/500.html (500 Internal Server
Error)
Any ideas as to the cause?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Custom Resource type Fail
From a quick glance, it seems like you are trying to reassign a
variable value - that is not allowed in puppet. You may assign to a
variable that exists in an outer scope (thereby shadowing it), but not
reassign in the same scope.
As an example:
case $semisync_master {
on: {
$semisync_master = ...
}
off: {
$semisync_master = ...
}
}
will not work because $semisync_master is a parameter with a bound value.
Use different variable names in your logic and template, or pass on
different values to a second define.
You will probably find the selector expression easier to use in cases
like this. i.e.
$semisync = $semisync_master ? {
'on' = 'value when on',
'off' = 'value when off',
}
Regards
- henrik
On 2012-05-10 15:23, Douglas Brancaglion wrote:
Hi guys!
I have a problem in a custom resource type, because the idea is that I
had to put in the manifest options on or off as an example below, but
these rules are not working case. any idea what it is?
define mysql ( $server_id, $relay_log_index, $performance_schema,
$rpl_semi_sync_master_enabled, $rpl_semi_sync_master_timeout,
$rpl_semi_sync_slave_enabled, $semisync_master, $semisync_slave,
$mod_opr, $read_only, $expire_logs_days, $max_binlog_size,
$binlog_format, $query_cache_limit, $query_cache_size, $server_id,
$innodb_file_per_table, $innodb_buffer_pool_size, $innodb_open_files,
$key_buffer_size, $tmp_table_size, $max_heap_table_size,
$table_open_cache, $max_connections, $thread_cache_size ) {
file { /etc/my.cnf:
ensure= present,
owner= root,
group= root,
mode= 0640,
notify= Service[mysql],
source= template(global/mysql/my.cnf.erb),
}
file { /var/log/mysql:
ensure= directory,
owner= mysql,
group= mysql,
mode= 0750,
}
case $read_only {
on: { $readonly = red_only=1 }
off: { $readonly = red_only=0 }
}
case $relay_log_index {
on: {
$relay_log_index =
relay_log_index=/var/log/mysql/relay_$(hostname).log
}
off: {
$relay_log_index =
;relay_log_index=/var/log/mysql/relay_$(hostname).log
}
}
case $semisync_master {
on: {
$semisync_master =
plugin_load=rpl_semi_sync_master=semisync_master.so
}
off: {
$semisync_master =
;plugin_load=rpl_semi_sync_master=semisync_master.so
}
}
case $semisync_slave {
on: {
$semisync_slave =
plugin_load=rpl_semi_sync_slave=semisync_slave.so
}
off: {
$semisync_slave =
;plugin_load=rpl_semi_sync_slave=semisync_slave.so
}
}
case $performance_schema {
on: {
$performance_schema = performance_schema
}
off: {
$performance_schema = ;performance_schema
}
}
case $mod_opr {
master: {
$server_id = 1
}
slave: {
$server_id = 2
}
}
case $rpl_semi_sync_master_enabled {
on: {
$rpl_semi_sync_master_enabled =
rpl_semi_sync_master_enabled=1
}
off: {
$rpl_semi_sync_master_enabled =
;rpl_semi_sync_master_enabled=1
}
}
case $rpl_semi_sync_master_timeout {
on: {
$rpl_semi_sync_master_timeout =
rpl_semi_sync_master_timeout=10
}
off: {
$rpl_semi_sync_master_timeout =
;rpl_semi_sync_master_timeout=1
}
}
case $rpl_semi_sync_slave_enabled {
on: {
$rpl_semi_sync_slave_enabled =
rpl_semi_sync_slave_enabled=1
}
off: {
$rpl_semi_sync_slave_enabled =
;rpl_semi_sync_slave_enabled=1
}
}
packages { mysql-server:
ensure= present,
}
}
And it is my manifest:
class global::mysql::teste {
mysql { teste:
mod_ops= master,
server_id= 1,
innodb-file-per-table= 1,
innodb-buffer-pool-size= 256M,
innodb-open-files= 400,
key-buffer-size= 256M,
tmp-table-size= 16M,
max-heap-table-size= 128M,
table-open-cache= 400,
max-connections= 1000,
thread-cache-size= 20,
read_only= off,
relay-log-index= off,
binlog_format= run,
max_binlog_size= 32M,
query_cache_limit= 2098,
query_cache_size= 32M,
semisync_master= off,
semisync_slave= off,
rpl_semi_sync_master_enabled= off,
rpl_semi_sync_master_timeout= off,
rpl_semi_sync_slave_enabled= off,
performance_schema= off,
}
}
Tks Again!
--
Douglas Brancaglion
Security Analist
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
[Puppet Users] Re: is_virtual selector
Hey,
This selector expects to get a true boolean value e.g. true / false
(TrueClass / FalseClass in Ruby) and that is why it is failing, since you
are passing a string true from the fact (and all values coming from
Facter are strings, even numeric values).
Grab this:
https://raw.github.com/kwilczynski/puppet-functions/master/lib/puppet/parser/functions/str2bool.rb
And then try:
class baseline-testing::ntpd {
package { ntp:
ensure = str2bool($is_virtual) ? {
false = present,
true = purged
}
}
}
Hope that helps :)
KW
On Wednesday, October 3, 2012 2:43:01 AM UTC+1, Matt wrote:
I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now
at 3.0.0. Not sure if this is a version change or syntax error that I am
experiencing. We'll use 'ntp' as the example and the build host is a VM.
The old way:
class baseline::ntpd {
package { ntp:
ensure = $virtual ? {
physical = present,
vmware = purged,
default = present
}
}
On the client, it always says that it is created, even though it's not
present:
[root@build ~]# puppet agent -tv
Info: Retrieving plugin
Info: Caching catalog for build
Info: Applying configuration version '1349227476'
/Stage[main]/Baseline::Ntpd/Package[ntp]/ensure: created
Finished catalog run in 1.46 seconds
[root@build ~]#
[root@build ~]# rpm -q ntp
package ntp is not installed
[root@build ~]#
When trying the $is_virtual facter..
class baseline-testing::ntpd {
package { ntp:
ensure = $is_virtual ? {
false = present,
true = purged
}
}
}
On client:
[root@build ~]# puppet agent -tv
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: No matching value for selector param 'true' at
/etc/puppet/manifests/classes/baseline_linux-testing.pp:35 on node build
[root@build ~]#
[root@build ~]# facter | grep virtual
is_virtual = true
virtual = vmware
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/GUQ5PMTcO9wJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet doc no longer producing documentation
On Thursday, October 4, 2012 9:01:58 PM UTC+1, Jeff McCune wrote: On Wed, Oct 3, 2012 at 6:31 AM, Hugh Cole-Baker hu...@fanduel.comjavascript: wrote: After upgrading to Puppet 3.0.0 it seems that puppet doc is no longer producing documentation from my modules / manifests. I have a setup with two environments in /etc/puppet/environments/[production, testing], and I'm running the following command to generate the docs: puppet doc --all --mode rdoc --environment production --outputdir doc After running this it creates the 'doc' directory but there are no files in it. The same command was working OK on 2.7.19. Has anything changed in the required format of doc comments in the manifests? This is likely a bug. Could you please file an issue at http://projects.puppetlabs.com/projects/puppet describing the problem and snippets of commands showing how to reproduce the issue? If you follow up to this conversation with the ticket number, I'll start watching the ticket and work to reproduce the issue. With some effort we might be able to fix this for the 3.0.1 release. Thanks, -Jeff Hi Jeff, I've created https://projects.puppetlabs.com/issues/16803 in the issue tracker. Thanks, Hugh -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/graOEp0CFq0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Could not find certificate for - Puppet 3.0.0-rc4
On Fri, Oct 5, 2012 at 2:37 AM, Luca Gioppo lucagio...@gmail.com wrote: Ok solved by deleting all the /var/lib/puppet/ssl content in the agent. made a puppat run and the master accepted the client and autosigned all and all went correctly. BUT I went to see if in the master issuing the command: puppet ca list --all or --signed There was to find the host but ... nothing just the puppetmaster and the CA certs... WHY Could you try puppet cert --list on the master instead of `puppet ca`? If that works, please let me know by reply, I'd definitely like to make sure we clear up this confusion between `puppet ca` and `puppet cert` as best I can. Thanks, -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Trying to delete home directory while deleting accounts.
Hi all,
I wondering why having provider=useradd the parameter managehome =
true don't delete home directory ?
I have :
user { $name: ensure = absent, managehome = true }
As result, home directory was not deleted.
I appreciate any advise about it.
Thanks in advanced, eduardo
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet 3.0.0 and Hiera
I've been using Hiera and Hiera-Puppet with Puppet 2.7 for a while now, and I've been quite enjoying it. I just noticed the available update for Puppet and saw that Hiera was now part of core Puppet. However, I've been unable to parse exactly what parts made it over, and every source of information I read seems to have different info. My confusion includes: 1. The Hiera-Puppet functions, hiera() and the array, hash and include versions. They appear in the 3.0.0 doc, but I've read they may be deprecated, changed or even unnecessary, their functionality having been incorporated into things like lookup() and include(). Since I've been making fairly heavy use of them, I need to know if I should migrate my modules to something else. 2. The hierarchy itself. How much of the configurability made it over? I've been using a custom fact or two in mine, and I'm wondering if that's still supported. Also, I've been using a combination of YAML on disk and a puppet data module to store variables, is that still supported? Basically, I've been having trouble finding consistent documentation on the subject of what changed and what didn't, so if someone could explain or point me to the correct docs, that would be greatly appreciated, as I really want to upgrade to take advantage of the other new features. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/rbwWoB1WDGEJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] PuppetDB Installation
I am attempting to install PuppetDB from source. I am a bit confused however, is lein required? thanks! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] PuppetDB Installation
On Fri, Oct 05, 2012 at 01:21:46PM -0600, Deepak Giridharagopal dee...@puppetlabs.com wrote: On Fri, Oct 05, 2012 at 02:14:41PM -0400, Worker Bee beeworke...@gmail.com wrote: I am attempting to install PuppetDB from source. I am a bit confused however, is lein required? Correct, you'll need that to build the actual PuppetDB daemon itself. For the 1.0.0 release and earlier, you'll need the stable version (1.7.x) of lein, which you can get from the upstream here: https://github.com/technomancy/leiningen https://raw.github.com/technomancy/leiningen/stable/bin/lein ...assuming it's not available via system package or the like. I was just informed that we actually have lein packages in the puppetlabs repos, in fact. For example: http://yum.puppetlabs.com/el/5/dependencies/x86_64/leiningen-1.7.1-1.el5.noarch.rpm http://apt.puppetlabs.com/pool/precise/dependencies/l/leiningen/leiningen_1.7.1-1puppetlabs2_all.deb deepak -- Deepak Giridharagopal / Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet 3.0.0 and Hiera
On Friday, October 5, 2012 10:47:58 AM UTC-7, Ellison Marks wrote: I've been using Hiera and Hiera-Puppet with Puppet 2.7 for a while now, and I've been quite enjoying it. I just noticed the available update for Puppet and saw that Hiera was now part of core Puppet. However, I've been unable to parse exactly what parts made it over... Yeah sorry, I'm working on clarifying that today. The answer is: ALL OF IT, but you might have to move your config file or change a setting. - Puppet has a hiera_config setting that defaults to $confdir/hiera.yaml. It won't fall back to hiera's default conf file. If your conf is at /etc/hiera.yaml, move it or tell puppet.conf where it is. http://docs.puppetlabs.com/references/latest/configuration.html#hieraconfig - The hierarchy itself works the same, including fact interpolation. - All four hiera functions are still there. No need to change their names. - The puppet backend is still there! That's one that we were planning to remove at one point, and I don't yet have the whole story on how that went down, but it did stay in. Or at least, it's in the source code; I don't know how packages and gems deal with it, yet. - The generic lookup function didn't happen. The built-in data_binding code currently only applies to class parameters; we left an expansion of it for a later date, once we have a deeper understanding of users' needs and challenges. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/KluWo130L3kJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Are future versions of facter and hiera 2.7.x backwards compatible?
Hiera is following semver, so any new releases in the Hiera 1.x series will be backward compatible and will work with Puppet 2.7.x. The Facter 1.6.x series will also continue to work with Puppet 2.7.x. On Fri, Oct 5, 2012 at 4:40 AM, Sandra Schlichting littlesandr...@gmail.com wrote: Hi, I am using puppet 2.7 so I am wondering if the new facter-1.6.13-1 hiera-1.1.0 and future versions are compatible with puppet 2.7 ? Hugs, Sandra -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/yeYeMvKfbPgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Matthaus Owens Release Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet 3.0.0 and Hiera
Thanks for the reply. I'll probably start migrating things to the new parameter based lookup and a disk based hierarchy anyway, but it's good to know that my setup probably won't break immediately upon upgrading. ^_^ On Friday, October 5, 2012 12:44:41 PM UTC-7, Nick Fagerlund wrote: On Friday, October 5, 2012 10:47:58 AM UTC-7, Ellison Marks wrote: I've been using Hiera and Hiera-Puppet with Puppet 2.7 for a while now, and I've been quite enjoying it. I just noticed the available update for Puppet and saw that Hiera was now part of core Puppet. However, I've been unable to parse exactly what parts made it over... Yeah sorry, I'm working on clarifying that today. The answer is: ALL OF IT, but you might have to move your config file or change a setting. - Puppet has a hiera_config setting that defaults to $confdir/hiera.yaml. It won't fall back to hiera's default conf file. If your conf is at /etc/hiera.yaml, move it or tell puppet.conf where it is. http://docs.puppetlabs.com/references/latest/configuration.html#hieraconfig - The hierarchy itself works the same, including fact interpolation. - All four hiera functions are still there. No need to change their names. - The puppet backend is still there! That's one that we were planning to remove at one point, and I don't yet have the whole story on how that went down, but it did stay in. Or at least, it's in the source code; I don't know how packages and gems deal with it, yet. - The generic lookup function didn't happen. The built-in data_binding code currently only applies to class parameters; we left an expansion of it for a later date, once we have a deeper understanding of users' needs and challenges. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/pjyE89rYin4J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Nagios types
Can Puppet's Nagios types accept custom variable macros? I want something that
looks like:
define service {
## --PUPPET_NAME-- (called '_naginator_name' in the manifest)
rpm-db-corrupt
uselog-error-template
service_descriptionRPM DB Corruption
hostgroup_name all_hosts
_alert_code 1234
}
Thanks for the help.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Conf Slides
While waiting for the video and audio to be published, I went through a bunch of the tweets and collected links to slides already out there. That list is at https://docs.google.com/document/d/1rtrwrSEsXXM5gwaH7cUSkJ-pMbnmedMTdgvONO5k728/edit If you know of any I missed, let me know by mail, twitter or IRC (I am FriedBob on both) and I will update. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/FXqvhfBvTlcJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] PuppetDB Installation
Is it possible to get the srpm for puppetdeb-1.0.0 ? Thanks! On Fri, Oct 5, 2012 at 3:34 PM, Deepak Giridharagopal dee...@puppetlabs.com wrote: On Fri, Oct 05, 2012 at 01:21:46PM -0600, Deepak Giridharagopal dee...@puppetlabs.com wrote: On Fri, Oct 05, 2012 at 02:14:41PM -0400, Worker Bee beeworke...@gmail.com wrote: I am attempting to install PuppetDB from source. I am a bit confused however, is lein required? Correct, you'll need that to build the actual PuppetDB daemon itself. For the 1.0.0 release and earlier, you'll need the stable version (1.7.x) of lein, which you can get from the upstream here: https://github.com/**technomancy/leiningenhttps://github.com/technomancy/leiningen https://raw.github.com/**technomancy/leiningen/stable/**bin/leinhttps://raw.github.com/technomancy/leiningen/stable/bin/lein ...assuming it's not available via system package or the like. I was just informed that we actually have lein packages in the puppetlabs repos, in fact. For example: http://yum.puppetlabs.com/el/**5/dependencies/x86_64/** leiningen-1.7.1-1.el5.noarch.**rpmhttp://yum.puppetlabs.com/el/5/dependencies/x86_64/leiningen-1.7.1-1.el5.noarch.rpm http://apt.puppetlabs.com/**pool/precise/dependencies/l/** leiningen/leiningen_1.7.1-**1puppetlabs2_all.debhttp://apt.puppetlabs.com/pool/precise/dependencies/l/leiningen/leiningen_1.7.1-1puppetlabs2_all.deb deepak -- Deepak Giridharagopal / Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@** googlegroups.com puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://groups.google.com/group/puppet-users?hl=en . -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] PuppetDB Installation
My bad... just found it! Please disreagrd On Fri, Oct 5, 2012 at 5:45 PM, Worker Bee beeworke...@gmail.com wrote: Is it possible to get the srpm for puppetdeb-1.0.0 ? Thanks! On Fri, Oct 5, 2012 at 3:34 PM, Deepak Giridharagopal dee...@puppetlabs.com wrote: On Fri, Oct 05, 2012 at 01:21:46PM -0600, Deepak Giridharagopal dee...@puppetlabs.com wrote: On Fri, Oct 05, 2012 at 02:14:41PM -0400, Worker Bee beeworke...@gmail.com wrote: I am attempting to install PuppetDB from source. I am a bit confused however, is lein required? Correct, you'll need that to build the actual PuppetDB daemon itself. For the 1.0.0 release and earlier, you'll need the stable version (1.7.x) of lein, which you can get from the upstream here: https://github.com/**technomancy/leiningenhttps://github.com/technomancy/leiningen https://raw.github.com/**technomancy/leiningen/stable/**bin/leinhttps://raw.github.com/technomancy/leiningen/stable/bin/lein ...assuming it's not available via system package or the like. I was just informed that we actually have lein packages in the puppetlabs repos, in fact. For example: http://yum.puppetlabs.com/el/**5/dependencies/x86_64/** leiningen-1.7.1-1.el5.noarch.**rpmhttp://yum.puppetlabs.com/el/5/dependencies/x86_64/leiningen-1.7.1-1.el5.noarch.rpm http://apt.puppetlabs.com/**pool/precise/dependencies/l/** leiningen/leiningen_1.7.1-**1puppetlabs2_all.debhttp://apt.puppetlabs.com/pool/precise/dependencies/l/leiningen/leiningen_1.7.1-1puppetlabs2_all.deb deepak -- Deepak Giridharagopal / Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@** googlegroups.com puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://groups.google.com/group/puppet-users?hl=en . -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: is_virtual selector
Thanks Krzysztof. It successfully runs now, but output is misleading on
subsequent runs:
build ~]# puppet agent -tv
Info: Retrieving plugin
Info: Caching catalog for build
Info: Applying configuration version '1349482471'
/Stage[main]/Baseline-testing::Ntpd/Package[ntp]/ensure: ensure changed
'4.2.4p8-2.el6' to 'purged'
Finished catalog run in 6.10 seconds
build ~]#
build ~]# puppet agent -tv
Info: Retrieving plugin
Info: Caching catalog for build
Info: Applying configuration version '1349482471'
/Stage[main]/Baseline-testing::Ntpd/Package[ntp]/ensure: created
Finished catalog run in 1.10 seconds
build ~]#
build ~]# rpm -q ntp
package ntp is not installed
The only class being called for the 'build' node is
'baseline-testing::ntpd', which only ensures that the NTP package is
removed (the 8 lines of code you recommended). It does remove the package,
but I don't know why it mentions creating it upon the second run, even
though it does not actually get re-installed. Maybe traditional 'if'
statements are advised.
~Matt
On Friday, October 5, 2012 11:09:03 AM UTC-4, Krzysztof Wilczynski wrote:
Hey,
This selector expects to get a true boolean value e.g. true / false
(TrueClass / FalseClass in Ruby) and that is why it is failing, since you
are passing a string true from the fact (and all values coming from
Facter are strings, even numeric values).
Grab this:
https://raw.github.com/kwilczynski/puppet-functions/master/lib/puppet/parser/functions/str2bool.rb
And then try:
class baseline-testing::ntpd {
package { ntp:
ensure = str2bool($is_virtual) ? {
false = present,
true = purged
}
}
}
Hope that helps :)
KW
On Wednesday, October 3, 2012 2:43:01 AM UTC+1, Matt wrote:
I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now
at 3.0.0. Not sure if this is a version change or syntax error that I am
experiencing. We'll use 'ntp' as the example and the build host is a VM.
The old way:
class baseline::ntpd {
package { ntp:
ensure = $virtual ? {
physical = present,
vmware = purged,
default = present
}
}
On the client, it always says that it is created, even though it's not
present:
[root@build ~]# puppet agent -tv
Info: Retrieving plugin
Info: Caching catalog for build
Info: Applying configuration version '1349227476'
/Stage[main]/Baseline::Ntpd/Package[ntp]/ensure: created
Finished catalog run in 1.46 seconds
[root@build ~]#
[root@build ~]# rpm -q ntp
package ntp is not installed
[root@build ~]#
When trying the $is_virtual facter..
class baseline-testing::ntpd {
package { ntp:
ensure = $is_virtual ? {
false = present,
true = purged
}
}
}
On client:
[root@build ~]# puppet agent -tv
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: No matching value for selector param 'true' at
/etc/puppet/manifests/classes/baseline_linux-testing.pp:35 on node build
[root@build ~]#
[root@build ~]# facter | grep virtual
is_virtual = true
virtual = vmware
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/8JkoXA2w8Q0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
