[Puppet Users] Cannot use relative URL's
Hi,
I am running into this error:
Running Puppet agent on demand ...
Info: Retrieving plugin
Info: Caching catalog for test-pc
Error: Failed to apply catalog: Parameter source failed on
File[c:/locale.reg]: Cannot use relative URLs
'/etc/puppet/modules/a_locale'
Why the source is not working as should ?
$ ls -l /etc/puppet/modules/
-rw-r--r-- 1 root root 1898 Mar 20 15:44 a_locale
site.pp
case $operatingsystem {
windows: { $fileName=c:/locale.reg}
default: { fail([puppet] os not supported) }
}
file { $fileName:
ensure = present,
source = /etc/puppet/modules/a_locale,
}
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Custom type and provider development
Did you get any further with the installutil provider? It sounds really interesting - I myself is trying to automate install of PerfTab (a .net application).. -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Cannot use relative URL's
The source parameter takes URIs. You can't just give it a system path. Make
sure the file lives in a files directory in a module and is properly
readable by puppet and use puppet://modules/(modulename)/(filename) in
source.
On Thursday, March 21, 2013 12:38:32 AM UTC-7, Dragos R wrote:
Hi,
I am running into this error:
Running Puppet agent on demand ...
Info: Retrieving plugin
Info: Caching catalog for test-pc
Error: Failed to apply catalog: Parameter source failed on
File[c:/locale.reg]: Cannot use relative URLs
'/etc/puppet/modules/a_locale'
Why the source is not working as should ?
$ ls -l /etc/puppet/modules/
-rw-r--r-- 1 root root 1898 Mar 20 15:44 a_locale
site.pp
case $operatingsystem {
windows: { $fileName=c:/locale.reg}
default: { fail([puppet] os not supported) }
}
file { $fileName:
ensure = present,
source = /etc/puppet/modules/a_locale,
}
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet 3.1.1 and file… - Error: Failed to apply catalog: Attribute 'user' or 'target' is mandatory
Gee, thanks for being this guy (http://thedailywtf.com/Articles/A-Misleading-Memory.aspx) Have you made sure that $1 $2 and $3 are available in the scope you are using them? That code is not very robust, you may want to wrap the ssh_authorized_key into a defined type with sane default parameters, so undefined variables will not hurt you in these exciting ways. On 03/20/2013 05:18 PM, Xavier Beaudouin wrote: Okay after fighting, seem that my class user that use ssh_authorized_key ressource is giving me this headache. So... I tried some stuff on this : http://pastealacon.com/32000 but I have no clues :( So bad the error is so simple that we can wastes hours just about a wrong class... Xavier -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: PuppetDB queue problem
Hi ak0ska, How are things going? Anything to report? ken. On Fri, Mar 15, 2013 at 5:00 AM, Ken Barber k...@puppetlabs.com wrote: Hi ak0ska, FWIW - with the help of some of my colleagues we've managed to replicate your constraint issue in a lab style environment now: https://gist.github.com/kbarber/5157836 Which is a start. It requires a unique precondition to replicate, and I've been unable however to replicate it in any way with PuppetDB directly, so the statement log will still be helpful if you can supply it. ken. On Thu, Mar 14, 2013 at 2:12 PM, Ken Barber k...@puppetlabs.com wrote: So I have this sinking feeling that all of your problems (including the constraint side-effect) are related to general performance issues on your database 'for some reason we are yet to determine'. This could be related to IO contention, it could be a bad index (although you've rebuilt them all right?) or something else. What continues to bother me is the fact you have only managed to reduce your DB size to 30GB, this is far larger than I expect and I it screams 'problem' to me. It should be less than 5 GB, at least based on my rough calculations from other DBs I've seen in the wild. It could very well be that something still isn't sufficiently organised (index, tablespace data) for optimal performance. A recreation of the database is by all means a very fast way to recreate everything, its like heaving an axe though. Having said that, it is fast and would eradicate a lot of back forth between us to try and solve this problem. A dump, drop, recreate and restore is also another way, not 100% the same thing, but close to it. Its entirely up to you - if you want to try either option then go ahead. It would be a fast step to achieving a lot of small steps. If it works, we may have lost some clarity on the issue however, so might be good to keep the original DB backup. If it doesn't work, at least we have ruled out a lot of possibilities in one quick action. So yeah, I wouldn't be upset if you take this action - there is a reason why I suggested this earlier, and that is it performs a lot of actions in one single step ... and I still think this is a viable action, but since you were keen on trying other things I was happy to go along :-). At the end of the day your time and your risk assessment is up to you. If it was me, yeah, I would try it. Esp. considering the amount of time already spent with very little final result. Thanks for being patient with me on this btw ... :-). ken. On Thu, Mar 14, 2013 at 3:36 AM, ak0ska akos.he...@gmail.com wrote: Hello Ken, I really appreciate you guys looking into this problem, and I'm happy to provide you with the data you ask for. However, I feel like I should ask, whether you think this problem is worth your efforts, if rebuilding the database might solve the issue? Cheers, ak0ska On Thursday, March 14, 2013 8:05:59 AM UTC+1, Ken Barber wrote: Hi ak0ska, So I've been spending the last 2 days trying all kinds of things to replicate your constraint violation problem and I still am getting nowhere with it. I've been speaking to all kinds of smart people and we believe its some sort of lock and/or transactional mode problem but none of my testing can replicate it. My latest test was something like: https://gist.github.com/kbarber/5157836 But with all that preparation and load simulation I still couldn't replicate it :-(. I think I need more data from you ... in this case, a statement log. Now a statement log can be pretty heavy, so if we can get the data surrounding a GC only that should be enough - however I anticipate it might reduce some performance so if you're apprehensive about doing it in production I fully understand. I'm just running out of ideas, and without more data I may have trouble coming to a conclusion. Anyway, if at all possible the instructions for enabling this are as follows: * Go to your postgresql.conf file (On RHEL 6 this is usually located in /var/lib/pgsql/data) * Add/modify the entries: log_statement = 'all' log_line_prefix = '%m PID[%p] SID[%c] VTID[%v] TID[%x] ' * Restart postgresql * Logs should go to: /var/lib/pgsql/data/pg_log The closer you can do this to being set _just before_ a GC run the better, as it will reduce the amount of time this setting needs to be on. Once you have a GC run and a subsequent constraint logged you should be able to turn it off. Don't worry about PuppetDB during these cases, it retries the database so if you can take the small hit with queries the outage should be quick while you switch off/on the setting (and be mindful that catalogs/facts/reports submissions will get queued, queries of course will fail during that short time during DB restart). Now the data itself is going to obviously contain private items, so if you prefer to send it to me privately thats fine (contact me off this list if so). Otherwise, it might
Re: [Puppet Users] Windows Reboot
Hi Guys
The way I get around it now, is by using a powershell script that creates a
text file and delete puppetlockd if exists and then reboots, and then
puppet checks if text file exists upon next run and ignores
e.g. Powershell
Add-Content c:\Installs\Puppet_Confirmation\Joined_AD_domain.txt Windows
has joined $domain
$strFileName = c:\ProgramData\PuppetLabs\Puppet
Enterprise\var\state\puppetlockd
IF (Test-Path $strFileName){
Remove-Item $strFileName }
shutdown /r /t 60
e.g. Puppet manifest
exec { 'domain_join':
command = 'C:/Windows\System32\WindowsPowerShell\v1.0\powershell.exe
-executionpolicy remotesigned -file C:\Installs\Scripts\domain_join.ps1',
creates = 'C:\Installs\Puppet_Confirmation\Joined_AD_domain.txt',
This approach seems to work ok for me, as I can then control, how puppet
works by using another script to delete the text file, I so it will re-run
if required
(if that make sense)
regards
James
On Thursday, 21 March 2013 05:26:27 UTC, ad wrote:
Hi Josh,
As you may recall, I'm the odd kid on the block using Puppet to manage
many many embedded Windows 7 and XP devices, so my needs are probably not
very representative of the Puppet community. I have no need for a reboot
message/code. Most our devices already have a nightly scheduled reboot. I
use run stages and a delayed shutdown to, for all practical purposes,
ensure a resource that requires a reboot runs last and give the agent
enough time to cleanly finish the run and send reports back. I also use a
schedule resource to control when devices are allowed to apply a resource
that requires a reboot.
I'll check out your reboot provider, thanks. I just use an exec currently.
Regards,
Adam
On Tuesday, March 19, 2013 11:42:19 PM UTC-5, Josh Cooper wrote:
On Monday, March 11, 2013, ad wrote:
James,
Not yet, see http://projects.puppetlabs.com/issues/19162.
My (ugly) approach for this now is a refreshonly exec with a delayed
shutdown. I'd like to see a reboot = true or such for all resources that
tell the agent to reboot after a run is complete when that resource is
applied.
I did something similar, reboot resource type that is only triggered via
notify/subscribe relationship from another resource. See
https://github.com/joshcooper/puppetlabs-reboot
Adam, I'm curious about the approach you're talking about also. If reboot
was a metaparameter, I don't think it would be possible to specify
the reboot message or reason code (for different resources) But perhaps
that's not really important?
Adam
On Monday, March 11, 2013 6:55:46 AM UTC-5, jim wrote:
Hi Guys
I'm using puppet for my windows configuration, and was wondering when
installing / configuration something windowys, it requires a reboot, how
does this effect the puppet run
e.g. join to domain ?
e.g. removing old version of software
e.g. host re-name
Is there options you can tell puppet its going to reboot and to finish
that puppet run upon restart
Regards
James
--
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 to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
Josh Cooper
Developer, Puppet Labs
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Redmine upgrade beginning
Right. Was that by design? On 03/18/2013 09:32 PM, Hunter Haugen wrote: Looks like the upvote/downvote buttons are missing. (/red(dit|mine)/ anyone?) -Hunter -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Cannot use relative URL's
Thanks,
It worked. Though it would of been great to make source work without
creating all that structure.
If you don't mind can you please tell me where I can put my logic now if I
want to deploy certain files
depending on the OS: in the init.pp or the site.pp ?
tree -a --charset=ASCII /etc/puppet/modules/
/etc/puppet/modules/
`-- aex
|-- files
| `-- aexlocale
`-- manifests
`-- init.pp
3 directories, 2 files
site.pp
import 'aex'
include aex
case $operatingsystem {
centos: { include abc ? }
windows: { include aex }
default: { fail([puppet] OS not supported) }
}
?
Regards
On Thursday, March 21, 2013 10:56:16 AM UTC+2, Ellison Marks wrote:
The source parameter takes URIs. You can't just give it a system path.
Make sure the file lives in a files directory in a module and is properly
readable by puppet and use puppet://modules/(modulename)/(filename) in
source.
On Thursday, March 21, 2013 12:38:32 AM UTC-7, Dragos R wrote:
Hi,
I am running into this error:
Running Puppet agent on demand ...
Info: Retrieving plugin
Info: Caching catalog for test-pc
Error: Failed to apply catalog: Parameter source failed on
File[c:/locale.reg]: Cannot use relative URLs
'/etc/puppet/modules/a_locale'
Why the source is not working as should ?
$ ls -l /etc/puppet/modules/
-rw-r--r-- 1 root root 1898 Mar 20 15:44 a_locale
site.pp
case $operatingsystem {
windows: { $fileName=c:/locale.reg}
default: { fail([puppet] os not supported) }
}
file { $fileName:
ensure = present,
source = /etc/puppet/modules/a_locale,
}
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet 3.1.1 failing to generate Private Key Certificate: Permission denied - /etc/puppet/ssl/ca/ca_key.pem
The Puppet master runs as the puppet user so try: # chown -R puppet:puppet /etc/puppet - Keith On 13 March 2013 19:42, Mike Canty cantyma...@yahoo.com wrote: Successfully installed Puppet 3.1.1 under Centos 6. When trying to start puppet as the root user, puppet generates the following message: Could not prepare for execution: Permission denied - /etc/puppet/ssl/ca/ca_key.pem Any help is greatly appreciated! Mike -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] exec resource not refreshed when subscribed resource changes
The subscribe isn't needed if notify is used which is in point 1. There are multiple ways to solve the problem - I prefer pushing these events using notify rather than pulling via subscribe :-) On 21 March 2013 10:37, Felix Frank felix.fr...@alumni.tu-berlin.de wrote: Hi, On 03/14/2013 09:25 AM, Keith Burdis wrote: 2) Adding refreshonly = true to the exec. 3) Remove the creates and subscribe from the exec. The subscribe is actually fine, but yes - the 'creates' needs to go in order to allow repeated execution. Note that this can be considered unclean manifest design, because a) notifications can get lost during agent crashes (if you're unlucky) and b) if the exec fails, puppet will likely not notify again next time, which is a painful and not at all unlikely failure scenario. Ideally, you could construct a dynamic creates or unless clause, that will enable puppet to always infer wether the exec need running or not. -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Processing custom function response from calling custom function?
Morning all I'm trying to write a custom function that calls the foreman search function (https://github.com/ohadlevy/puppet-foreman/blob/master/foreman/lib/puppet/parser/functions/foreman.rb) and then processes the results, before returning itself... A code snippet is here: http://pastebin.com/MPf7z0ui. This also includes the error being returned by Puppet agent on runtime. The notice in my function does print out in the master messages.log, with the following content: puppet-master[28971]: (Scope(Class[Act::Server::Linux::Db::Oracle])) DB_servers looks like: . Nil = false. Class = Hash. Ap = . However I'm still getting the puppet error when running the agent??? Any ideas greatly received. Regards Gavin -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet time accuracy
Hi, I consider Puppet for maintaining regional configuration in 5 offices across 2 timezones. I know Puppet is very time sensitive (the SSL handshake actually). There will be only one puppetmaster in one of the timezones and agents will be Windows workstations and Mac notebooks. My questions are: 1) Will there be problems running clients from different time zone than puppet master ? 2) What is the required client clock accuracy ? Thank you, Dragos -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet time accuracy
- Original Message - From: Dragos R the...@gmail.com To: puppet-users@googlegroups.com Sent: Thursday, March 21, 2013 11:33:03 AM Subject: [Puppet Users] Puppet time accuracy Hi, I consider Puppet for maintaining regional configuration in 5 offices across 2 timezones. I know Puppet is very time sensitive (the SSL handshake actually). There will be only one puppetmaster in one of the timezones and agents will be Windows workstations and Mac notebooks. My questions are: 1) Will there be problems running clients from different time zone than puppet master ? no it works fine, the thing that matters are the times in the certificates and those are done via UTC so your machines timezone generally doesnt matter 2) What is the required client clock accuracy ? just install NTP, there isn't really a range of accuracy, its easier to just have the correct time than worry about it being kind of right -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet time accuracy
On 21.03.2013 12:33, Dragos R wrote: Hi, I consider Puppet for maintaining regional configuration in 5 offices across 2 timezones. I know Puppet is very time sensitive (the SSL handshake actually). There will be only one puppetmaster in one of the timezones and agents will be Windows workstations and Mac notebooks. My questions are: 1) Will there be problems running clients from different time zone than puppet master ? I can say from experience that this is no problem. All time calculations are done taking the timezone into account. 2) What is the required client clock accuracy ? The only real constraint I ever noticed is, that the master refuses to sign certificates that were created in the (his) future. This often happens when the RTC (hardware clock) in a server is not set to UTC, but the installer thinks it is and puppet runs before NTP has kicked in. Best Regards, David -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] pluginsync trouble over SRV lookups
Hi, On 03/15/2013 03:21 AM, Ashwin N wrote: When using SRV lookups (over 2 puppetv3.1.1/RHEL6 masters), does anyone know why the pluginsync fails to sync at irregular intervals ? I gotta admit - I'm not familiar with SRV. What's it do? If I stop either of masters, everything proceeds fine ! I don't really understand what you're saying by that. Are there multiple masters? -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] What's your hiera tree look like?
On Wednesday, March 20, 2013 5:37:14 PM UTC-5, Andy Parker wrote:
On Tue, Mar 19, 2013 at 2:30 PM, Larry Fast lfas...@gmail.comjavascript:
wrote:
My Hiera tree is turning into a chaotic mess. I'm guessing that my tree
structure is one problem source. So I'm wondering how other real users have
setup hiera. Here are the core problems that are giving me headaches.
I'd be interested in seeing some of these as well. I'm looking for real
world examples of what people are putting in their hierarchies that we
might be able to make better in a hiera 2, which is something that my team
is looking at working on.
---
#This file is managed via puppet.
:hierarchy:
- %{node_id}
- %{cluster_type}
- common
:backends:
- yaml
- gpg
:yaml:
:datadir: /etc/puppet/hieradata
:gpg:
:datadir: /etc/puppet/hieradata/gpg
:key_dir: /etc/puppet/gpgkeys
We have 2 environments, each with their own $modulepath, but with a shared
manifests and hieradata. $::cluster_type identifies the type of cluster -
app, web, batch etc and $::node_id (is poorly named) identifies a specific
cluster (web-a, app-b etc) with both defaulting to hostname for the
non-clustered nodes.
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: How we can create two database Using same credetial using Puppet
On Thursday, March 21, 2013 5:37:35 AM UTC-5, Jithin Xavier wrote:
Hello All,
I wanted to create two two MySQL database with same user credential using
Puppet-MySQL. How can I achieve this? Please find my script below.
class mysql::vsdatabase {
include mysql
mysql::db { 'vidispine':
user = 'user',
password = 'user123',
host = 'db.hostname.com',
}
}
Use a define[1] to create the database rather than a class. Classes are
singletons, so you can only use them once per catalog (node).
By using a define, you can pull the data from a wrapper class param or
hiera, and then just call the define twice with different namevar but the
same user pass.
How can I add another database here with same credential.(If I create
different Class with different database and same credential I am getting
below error.
root@demo:/mnt# puppet agent -t
info: Retrieving plugin
info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/concat_basedir.rb
info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/puppet_vardir.rb
info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/root_home.rb
info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/iptables.rb
info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_version.rb
info: Loading facts in
/var/opt/lib/pe-puppet/lib/facter/custom_auth_conf.rb
info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/facter_dot_d.rb
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Duplicate declaration: Database_user[gxu...@db.demo.com javascript:] is
already declared in file
/etc/puppetlabs/puppet/modules/mysql/manifests/db.pp at line 62; cannot
redeclare at /etc/puppetlabs/puppet/modules/mysql/manifests/db.pp:62 on
node demo
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
)
Thanks,
Jithin Xavier
[1] http://docs.puppetlabs.com/puppet/3/reference/lang_defined_types.html
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] files outside a module
On 03/15/2013 05:02 PM, PF Carpentier wrote: I don't know if this message is relevant in my case because my file is not inside a module. I believe it is. The message is telling you that this pattern *will not work anymore* when you upgrade your master. You should consider creating your own simple openldap module and serve the file from there. HTH, Felix -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] How we can create two database Using same credetial using Puppet
On Thu, 2013-03-21 at 03:37 -0700, Jithin Xavier wrote:
Hello All,
I wanted to create two two MySQL database with same user credential using
Puppet-MySQL. How can I achieve this? Please find my script below.
class mysql::vsdatabase {
include mysql
mysql::db { 'vidispine':
user = 'user',
password = 'user123',
host = 'db.hostname.com',
}
}
How can I add another database here with same credential.(If I create
different Class with different database and same credential I am getting
below error.
The current git version of the mysql module has a fix for this error:
https://github.com/puppetlabs/puppetlabs-mysql/commit/1d6ca771d480e756cfdc5f84d73ef2d49f08ba38
but it has not yet been released. In the mean time, you can separately
use the underlying resources: (The mysql::db type is just a
convenience), just add additional 'database' and 'database_grant'
resources as needed:
database { 'vidispine':
ensure = 'present',
charset = 'utf-8',
provider = 'mysql',
require = Class['mysql::server'],
}
database_user { 'u...@example.com':
ensure = 'present',
password_hash = mysql_password('user123'),
provider = 'mysql',
require = Database['vidispine'],
}
database_grant { 'u...@example.com/vidispine':
privileges = 'all',
provider = 'mysql',
require = Database_user['u...@example.com'],
}
--
Calvin Walton calvin.wal...@kepstin.ca
smime.p7s
Description: S/MIME cryptographic signature
[Puppet Users] Need a puppet manifest to initialize a puppetmaster
What I am looking for is something along the lines of this: - Install fresh OS - Install puppet and git - Clone a git repo (remote or local) containing my puppetmaster configuration - Run a puppet command (or commands) with a manifest from the repo to install and configure a puppetmaster - Basically, I'm asking for example manifests, classes, modules, and templates that will do this - Whenever a commit occurs, a hook will automatically update the puppetmaster config. This part is a nice to have, but is not necessary, as long as I have the ability to sync manually or via cron. I wasn't really sure how to Google the answer to my question. I've seen a few incomplete examples of each, but not a combined solution. If anyone has a lmgtfy.com link or actual links to real examples, that would be greatly appreciated. Thanks in advance. -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Host name look up failure- unable to generate certificate in agent and transfer that to master for signature.
Uhm - those links you posted use an unroutable address. So that's not going to work for anyone. On 03/20/2013 07:06 AM, yarlagadda ramya wrote: *dnsdomainname: Host name lookup failure dnsdomainname: Host name lookup failure * this is common in the starting two lines of both the commands Facter cannot detect your host's FQDN because dnsdomainname -f isn't working. The easiest way to resolve this is adding a suitable line near the top of your /etc/hosts file. You can generate this line like this: echo `facter ipaddress` my.fully-qualfied-name.domain `facter hostname` of course, replacing my.fully-qualfied-name.domain with the actual fqdn. Puppet cannot work until facter fqdn returns a sensible value. HTH, Felix -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Query for file synchronization
Hi All, I have a simple requirement for file synchronization across multiple servers. Can puppet synchronize the files from master to agent nodes instantly? *My requirement:* Let say file on master server *test_1.txt *got modified by some binary. After modification I want to replicate the changes instantly on all other nodes (agent nodes/servers). Do puppet synchronize the file instantly to all servers? Thanks Regards Nivrutti -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Cannot use relative URL's
On Thursday, March 21, 2013 6:19:39 AM UTC-5, Dragos R wrote: Thanks, It worked. Though it would of been great to make source work without creating all that structure. If you had already been putting your code in modules, which I would recommend to everyone, then it would not have been all that [new] structure -- just one subdirectory of your existing module's main directory. If I interpret you correctly then you have now created a module for your class, so good show! Do note that you do not necessarily need a separate module for each class. Part of the idea is that you can, and often should, group related classes together in the same module. Note also that one of the advantages of modules is enabling the autoloader. You do not need to 'import' the manifests of classes that are properly laid out in modules, and indeed, you should not do so, so scratch the import 'aex' from your site.pp. As for where you put your logic: a module's init.pp should not contain any top-level declarations other than the definition of a class with the same name as the module in which it appears -- 'aex' in your case. If the logic you are talking about belongs inside class aex then put it there; otherwise not. Probably, however, it does not belong in site.pp or anywhere else at top level. Generally speaking, logic belongs in classes, and classes should be in modules. Very little should appear at top level in your site.pp and any manifests it imports, other than node definitions and possibly global resource defaults. Only a single class or definition should appear at top level in other manifests (which should all belong to modules). John -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Query for file synchronization
*My requirement:* Let say file on master server *test_1.txt *got modified by some binary. After modification I want to replicate the changes instantly on all other nodes (agent nodes/servers). Do puppet synchronize the file instantly to all servers? No, puppet nodes usually pull a new catalog from time to time (by default every half an hour) from the master. But your requirements sounds more that you want to look into something like lsyncd. I would not recommend to try to abuse puppet for instant file synchronization. Also puppet is not very good a synchronizing large directory trees. There are better tools for that job. ~pete -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] What's your hiera tree look like?
On Thu, Mar 21, 2013 at 5:46 AM, llowder llowde...@gmail.com wrote:
On Wednesday, March 20, 2013 5:37:14 PM UTC-5, Andy Parker wrote:
On Tue, Mar 19, 2013 at 2:30 PM, Larry Fast lfas...@gmail.com wrote:
My Hiera tree is turning into a chaotic mess. I'm guessing that my tree
structure is one problem source. So I'm wondering how other real users have
setup hiera. Here are the core problems that are giving me headaches.
I'd be interested in seeing some of these as well. I'm looking for real
world examples of what people are putting in their hierarchies that we
might be able to make better in a hiera 2, which is something that my team
is looking at working on.
---
#This file is managed via puppet.
:hierarchy:
- %{node_id}
- %{cluster_type}
- common
:backends:
- yaml
- gpg
:yaml:
:datadir: /etc/puppet/hieradata
:gpg:
:datadir: /etc/puppet/hieradata/gpg
:key_dir: /etc/puppet/gpgkeys
We have 2 environments, each with their own $modulepath, but with a shared
manifests and hieradata. $::cluster_type identifies the type of cluster -
app, web, batch etc and $::node_id (is poorly named) identifies a specific
cluster (web-a, app-b etc) with both defaulting to hostname for the
non-clustered nodes.
You are using both the yaml and gpg backends. Is the way hiera handles the
hierarchy + backends the way you would want it to work or is there a
different way of putting those two parts together that would fit what you
are trying to do better?
--
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 to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] What's your hiera tree look like?
Hi All,
Very interesting topic. Here's what I'm using:
---
:hierarchy:
- %{fqdn}
- %{role}
- %{group}
- %{osfamily}
- common
:backends:
- yaml
- puppet
:yaml:
:datadir: /etc/puppet/environments/%{environment}/data
:puppet:
:datasource: data
We don't have any uses of %{fqdn} but in the abstract I like having
that level of granularity. Role is what the system does like
production-webserver this the main makes-it-go bit. Group is the
group of humans it's for and handles things like access control, sudo,
and to a lesser extent software that a group wants on all their
systems. We have both Linux and FreeBSD in production, osfamily lets
us make some important distinctions in the way each OS handles some
basic things that would otherwise be in common which has the obvious
meaning.
All production systems use the production environment other
environments are for testing and development. Admins can create new
testing environments arbitrarily simply by checking out whatever
version of the git repo they're working on in /etc/puppet/environments
in practice here this tends to be username-test or some variant.
In terms of keeping data and code decoupled in version control we're
not doing anything special, the master branch is always production
and the puppet masters pull from a central repo every 5min with all
development done branches, once the branch seems to work it's merged
into master.
We do use git submodules to track both locally developed puppet
modules and some community modules we pull from github. It's kind of
a pain, but the least pain of a few alternatives we've tried. If you
need strong separation of hiera you could put it in a separate repo
and use submodules to bundle them together..
-Jon
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] What's your hiera tree look like?
On Thursday, March 21, 2013 10:47:11 AM UTC-5, Andy Parker wrote:
On Thu, Mar 21, 2013 at 5:46 AM, llowder llow...@gmail.com
javascript:wrote:
On Wednesday, March 20, 2013 5:37:14 PM UTC-5, Andy Parker wrote:
On Tue, Mar 19, 2013 at 2:30 PM, Larry Fast lfas...@gmail.com wrote:
My Hiera tree is turning into a chaotic mess. I'm guessing that my tree
structure is one problem source. So I'm wondering how other real users
have
setup hiera. Here are the core problems that are giving me headaches.
I'd be interested in seeing some of these as well. I'm looking for real
world examples of what people are putting in their hierarchies that we
might be able to make better in a hiera 2, which is something that my team
is looking at working on.
---
#This file is managed via puppet.
:hierarchy:
- %{node_id}
- %{cluster_type}
- common
:backends:
- yaml
- gpg
:yaml:
:datadir: /etc/puppet/hieradata
:gpg:
:datadir: /etc/puppet/hieradata/gpg
:key_dir: /etc/puppet/gpgkeys
We have 2 environments, each with their own $modulepath, but with a
shared manifests and hieradata. $::cluster_type identifies the type of
cluster - app, web, batch etc and $::node_id (is poorly named) identifies a
specific cluster (web-a, app-b etc) with both defaulting to hostname for
the non-clustered nodes.
You are using both the yaml and gpg backends. Is the way hiera handles
the hierarchy + backends the way you would want it to work or is there a
different way of putting those two parts together that would fit what you
are trying to do better?
It would be nice to be able to have per-backend hierarchies, but as it is,
I just don't create .gpg files for the levels of hierarchy I don't need, so
this isn't that big of a deal.
The only thing that would make it better, would be if hiera-gpg came with
hiera / puppet or didn't require a gem, but that's probably an issue to
take up with the author.
--
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 to puppet-users...@googlegroups.com javascript:.
To post to this group, send email to puppet...@googlegroups.comjavascript:
.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] How to make sure my common module executes before all other ones
ahhh, this is exactly what I needed. Thanks Wolf!!
On Wednesday, March 20, 2013 7:00:26 PM UTC-4, Wolf Noble wrote:
Hi Chris,
Take a look at run stages
http://docs.puppetlabs.com/guides/language_guide.html#stages
They make it a little easier to perform some coarse ordering.
additionally, you can use PuppetLabs stdlib module and take advantage of
the anchor pattern sparingly.
Here's a good example of its use:
https://github.com/adrienthebo/puppetlabs-mrepo/blob/master/manifests/init.pp
Hope that helps!
W
On Mar 20, 2013, at 5:04 PM, Chris Handy chris...@gmail.com javascript:
wrote:
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 users/groups, setting up LDAP,
mcollective, etc.. So my issue is how to make sure that the common module
runs before the roles listed in my node definitions. I know that I could
write out
node 'server1' inherits basenode {
class{'common': } -
class{'role::appserver': }
}
node 'server2' inherits basenode {
class{'common': } -
class{'role::webserver': }
}
but I am trying to think of a better way to do this. Thoughts?
Thanks,
Chris
--
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 to puppet-users...@googlegroups.com javascript:.
To post to this group, send email to
puppet...@googlegroups.comjavascript:.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
This message may contain confidential or privileged information. If you
are not the intended recipient, please advise us immediately and delete
this message. See http://www.datapipe.com/legal/email_disclaimer/ for
further information on confidentiality and the risks of non-secure
electronic communication. If you cannot access these links, please notify
us by reply message and we will send the contents to you.
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Windows ACL best practise
Hi Thomas,
On Wed, Mar 20, 2013 at 3:31 AM, Thomas Bendler thomas.bend...@gmail.comwrote:
Hi Josh,
2013/3/20 Josh Cooper j...@puppetlabs.com
S-1-5-18
thanks for the clarification, I wasn't aware that the SIDs are always the
same as stated in http://support.microsoft.com/kb/243330.
Many accounts have fixed SIDs, though some have a unique per-domain
component:
SID: S-1-5-21-domain-500
Name: Administrator
where the domain part is unique. For example, you can display your SID as:
C:\whoami /user
What's about everyone or user, will everyone or user get read-only access
when I change the mode to 0775?
Puppet maps the 'other' POSIX class to the Everyone SID ('S-1-1-0'). In
most recent versions of Windows, this is all accounts except anonymous
logon:
http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/3816efc7-255f-4f01-a71d-f27be627e439/
Multiple groups can't be specified inside the file type, can they? The
reference documentation (
http://docs.puppetlabs.com/references/3.1.latest/type.html#file) isn't
really clear about this topics ... at least from my point of view ;).
Puppet's file type only supports a single group account, but on Windows
that group can contain multiple nested groups and work as expected.
There is a ticket filed to support native NTFS ACLs, which would give you
fine-grain permissions, such as the ability to list multiple groups,
deny/allow, etc. See https://projects.puppetlabs.com/issues/13249
Josh
--
Josh Cooper
Developer, Puppet Labs
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Puppet Dashboard 1.2.23 Available
Puppet Dashboard 1.2.23 is a maintenance release of the 1.2 series of
Puppet Dashboard with bug fixes and minor features.
This release is available for download at:
https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23.tar.gz
Available in native package format in the Puppet Labs yum and apt
repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.2.23:
http://projects.puppetlabs.com/projects/dashboard
Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html
Contributors:
Aaron Stone, Daniel Pittman, Dustin J. Mitchell, Ken Barber, Matthaus
Owens, Moses Mendoza, and fhrbek
=
## Puppet Dashboard 1.2.23 Release Notes ##
=
Comment out specific gem rack version in our vendored Rails
* addresses http://projects.puppetlabs.com/issues/11669
(#17914) Store FlashHash as a normal Hash in session
This patch is a backport of:
https://github.com/rails/rails/commit/36376560fdd02f955ae3bf6b7792b784443660ad
In the form of a monkey patch in the puppet-dashboard initializer stage.
This is required to allow puppet-dashboard to co-exist with other
applications
that do not have the full rails stack in their namespace. Without it, other
non-rails applications (such as the certificate service and live management)
are unable to unmarshal cookies created in Rails. Instead, they
invalidate the
session and we start to see weird authentication glitches in the GUI.
In essence this patch ensures that when the FlashHash data is
stored in a cookie
it is stored as a normal Ruby Hash, as apposed to an
ActionController::Flash::FlashHash. As all other Ruby applications should be
able to unmarshal a Hash, this will avoid the Marshal.load method in
Rack::Session::Cookie from throwing a NameError exception.
Signed-off-by: Ken Barber k...@bob.sh
Add addgroup, addclass, listgroups, listclasses tasks for nodes
Previously if a user wanted to use rake tasks to interrogate the dashboard
about which groups or classes a node belonged to, they would be out of luck.
Similarly, if a user wanted to add a class or group to a node
without replacing
the already assigned classes/groups of a node it was not possible via only
rake. This commit adds a task in the node namespace to add a group
or groups to
a node and to add a class or classes to a node. The other two
tasks added here
list out the groups or classes already assigned to a node.
(#16429) Fix relative URLs of icons in tables.css
These links work when puppet-dashboard is at the top level because
browsers treat /../ as equivalent to /.
==
## Puppet Dashboard 1.2.23 Changelog ##
==
Aaron Stone (11):
e56a1dd Travis for master branch.
5584128 Issue 11760: Remove unused Services view.
2c9c954 Bug fix: inherited_resources using deprecated
{{mustache}} syntax instead of %{newer} syntax
a4b73a9 Spec fix to 04b4c0f use should be_any instead of array indexing.
b98ef7e Node and Group parameters rake tasks should not create
duplicate entries. Fixes #13867, updates commit 0108c040 to behave as
intended.
792d74a Check that the reports import dir exists, is a
directory, is readable. #18512
7bc9438 puts is STDOUT.puts
7ea8816 Change deprecated 'ftools' to 'fileutils'.
c244fa2 Daemonize in the Debian / Ubuntu server init.
2b0aad4 Tighten up code for rake api tasks, and move common
get_node get_group and get_class methods into a shared helper file.
7753bc5 Comment out specific gem rack version in our vendored Rails
Daniel Pittman (1):
e362172 (#19304) Upgrade to json_pure 1.7.7 for CVE-2013-0269
Dustin J. Mitchell (4):
775ab52 (#16429) Fix relative URLs of icons in tables.css
f37359a (#16429) fix relative links in application.scss
c7560d7 (#16429) use a controller reference for the delayed jobs link
1b1f0ee (#16429) use correct links for radiator, too
Ken Barber (1):
720da9d (#17914) Store FlashHash as a normal Hash in session
Matthaus Owens (7):
c040b17 Add addgroup, addclass, listgroups, listclasses tasks for nodes
d7d53da Fix descriptions of node tasks to match reality
f5e4a8e Add get_node helper method to node.rake
df715b4 (packaging) Update VERSION to 1.2.23-rc1
1c061e5 (maint) Make rails gems optional for rake tasks
aa33fbf (maint) Improve message during a load error in Rakefile
1dfc89b (packaging) Update VERSION to 1.2.23-rc2
Moses Mendoza (4):
65e5596 [packaging] Update mocks for rpmbuilder mock format
ea4ea37 [packaging] remove natty distribution from builds
c577d39 Update VERSION for 1.2.23-rc3
ac12e01 (packaging) Update VERSION to 1.2.23
fhrbek (2):
Re: [Puppet Users] Need a puppet manifest to initialize a puppetmaster
T ry this: http://usgcb.nist.gov/usgcb/rhel/download_rhel5.html There is a tarball for a basic puppet setup, designed to comply with security hardening guidelines. http://usgcb.nist.gov/usgcb/content/configuration/puppet-sdc-dist.tar.gz As it shows a reasonably complete setup, it should get you rolling. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin Hobbes) - Original Message - From: Daniel Schaefer danschae...@gmail.com To: puppet-users@googlegroups.com Sent: Thursday, March 21, 2013 9:03:12 AM Subject: [Puppet Users] Need a puppet manifest to initialize a puppetmaster What I am looking for is something along the lines of this: - Install fresh OS - Install puppet and git - Clone a git repo (remote or local) containing my puppetmaster configuration - Run a puppet command (or commands) with a manifest from the repo to install and configure a puppetmaster - Basically, I'm asking for example manifests, classes, modules, and templates that will do this - Whenever a commit occurs, a hook will automatically update the puppetmaster config. This part is a nice to have, but is not necessary, as long as I have the ability to sync manually or via cron. I wasn't really sure how to Google the answer to my question. I've seen a few incomplete examples of each, but not a combined solution. If anyone has a lmgtfy.com link or actual links to real examples, that would be greatly appreciated. Thanks in advance. -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: What's your hiera tree look like?
Hi Andy, I guess my most important request for Hiera 2 is diagnostic information. It's probably a broader request for better diagnostics in puppet as a whole. Here's what I dream of ... 1. The ability to run Puppet on the puppetmaster using the cached Facts from a server. 2. A postmortem (sorry, retrospective) output that includes a dump of all internal variables. Probably a .yaml file. Ideally each variable should be able to state how it was set. Eg. Came from Hiera/qa_env/zookeeper_role/zabbix_module OR set at file:line module/zabbix/manifest/init.pp:136 To answer some questions about how we are using Hiera more generally Puppet - we only use the yaml backend - we create custom facts for each server inside a puppet module (soon to be an ENC): location, project, role server_env. The last could be renamed as server_collection or service_group. - Each Puppet Environment is a git clone of our repo. - Development activity is delivered into the tip and then we create a branch for the deployment pipeline: integration=staging=production. IMO, we need the branch because our puppet code is still young. When things are more stable we may be able to push straight from the tip. -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Announce: Puppet Dashboard 1.2.23 Available
The documentation is a bit contradictory.
It says you need ruby 1.8.7, and then says you cannot use it with CentOS/RHEL-5
'cause the supported version of ruby is 1.8.7
It totally ignores the Puppet dependencies repos, which contain ruby 1.8.7
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin Hobbes)
- Original Message -
From: Moses Mendoza mo...@puppetlabs.com
To: puppet-users@googlegroups.com, puppet-...@googlegroups.com,
puppet-annou...@googlegroups.com
Sent: Thursday, March 21, 2013 3:28:46 PM
Subject: [Puppet Users] Announce: Puppet Dashboard 1.2.23 Available
Puppet Dashboard 1.2.23 is a maintenance release of the 1.2 series of
Puppet Dashboard with bug fixes and minor features.
This release is available for download at:
https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23.tar.gz
Available in native package format in the Puppet Labs yum and apt
repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.2.23:
http://projects.puppetlabs.com/projects/dashboard
Documentation is available at: http://docs.puppetlabs.com/dashboard/index.html
Contributors:
Aaron Stone, Daniel Pittman, Dustin J. Mitchell, Ken Barber, Matthaus
Owens, Moses Mendoza, and fhrbek
=
## Puppet Dashboard 1.2.23 Release Notes ##
=
Comment out specific gem rack version in our vendored Rails
* addresses http://projects.puppetlabs.com/issues/11669
(#17914) Store FlashHash as a normal Hash in session
This patch is a backport of:
https://github.com/rails/rails/commit/36376560fdd02f955ae3bf6b7792b784443660ad
In the form of a monkey patch in the puppet-dashboard initializer stage.
This is required to allow puppet-dashboard to co-exist with other
applications
that do not have the full rails stack in their namespace. Without it, other
non-rails applications (such as the certificate service and live management)
are unable to unmarshal cookies created in Rails. Instead, they
invalidate the
session and we start to see weird authentication glitches in the GUI.
In essence this patch ensures that when the FlashHash data is
stored in a cookie
it is stored as a normal Ruby Hash, as apposed to an
ActionController::Flash::FlashHash. As all other Ruby applications should be
able to unmarshal a Hash, this will avoid the Marshal.load method in
Rack::Session::Cookie from throwing a NameError exception.
Signed-off-by: Ken Barber k...@bob.sh
Add addgroup, addclass, listgroups, listclasses tasks for nodes
Previously if a user wanted to use rake tasks to interrogate the dashboard
about which groups or classes a node belonged to, they would be out of luck.
Similarly, if a user wanted to add a class or group to a node
without replacing
the already assigned classes/groups of a node it was not possible via only
rake. This commit adds a task in the node namespace to add a group
or groups to
a node and to add a class or classes to a node. The other two
tasks added here
list out the groups or classes already assigned to a node.
(#16429) Fix relative URLs of icons in tables.css
These links work when puppet-dashboard is at the top level because
browsers treat /../ as equivalent to /.
==
## Puppet Dashboard 1.2.23 Changelog ##
==
Aaron Stone (11):
e56a1dd Travis for master branch.
5584128 Issue 11760: Remove unused Services view.
2c9c954 Bug fix: inherited_resources using deprecated
{{mustache}} syntax instead of %{newer} syntax
a4b73a9 Spec fix to 04b4c0f use should be_any instead of array indexing.
b98ef7e Node and Group parameters rake tasks should not create
duplicate entries. Fixes #13867, updates commit 0108c040 to behave as
intended.
792d74a Check that the reports import dir exists, is a
directory, is readable. #18512
7bc9438 puts is STDOUT.puts
7ea8816 Change deprecated 'ftools' to 'fileutils'.
c244fa2 Daemonize in the Debian / Ubuntu server init.
2b0aad4 Tighten up code for rake api tasks, and move common
get_node get_group and get_class methods into a shared helper file.
7753bc5 Comment out specific gem rack version in our vendored Rails
Daniel Pittman (1):
e362172 (#19304) Upgrade to json_pure 1.7.7 for CVE-2013-0269
Dustin J. Mitchell (4):
775ab52 (#16429) Fix relative URLs of icons in tables.css
f37359a (#16429) fix relative links in application.scss
c7560d7 (#16429) use a controller reference for the delayed jobs link
1b1f0ee (#16429) use correct links for radiator, too
Ken Barber (1):
720da9d (#17914) Store FlashHash as a normal Hash in session
Matthaus Owens (7):
c040b17 Add addgroup, addclass, listgroups, listclasses tasks for nodes
d7d53da Fix descriptions of node tasks to
[Puppet Users] syntax problems trying to use Keith Burdis's erwbgy/system module without Hiera
I'm trying to use Keith Burdis's excellent erwbgy/system module without
Hiera, at least initially.
http://forge.puppetlabs.com/erwbgy/system
I cannot determine how call the modules. From what I can tell the
documentation isn't quite correct (or I am reading it wrong). I'm trying
to start with ntp because that's an easy to understand example.
https://github.com/erwbgy/puppet-ntp
The ntp documentation says
snip
Specify a list of time servers to use:
class { 'ntp':
servers = [ 'ntp1.domain.com', 'ntp2.domain.com' ],
}
endsnip
If I enter it like this in my manifest, I get errors. I assume the correct
syntax is something more like this
snip
system::ntp { 'name':
servers = [ 'ntp1.domain.com', 'ntp2.domain.com' ],
}
endsnip
but that syntax gets me this error
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type system::ntp at /etc/puppet/manifests/site.pp:36 on node
Any help with this would be appreciated..
thanks!
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: syntax problems trying to use Keith Burdis's erwbgy/system module without Hiera
i replied to your post over in foreman :) you can also search for my i
can't wrap my head around hiera post for more details too.
On Thursday, March 21, 2013 3:09:02 PM UTC-5, John Smith wrote:
I'm trying to use Keith Burdis's excellent erwbgy/system module without
Hiera, at least initially.
http://forge.puppetlabs.com/erwbgy/system
I cannot determine how call the modules. From what I can tell the
documentation isn't quite correct (or I am reading it wrong). I'm trying
to start with ntp because that's an easy to understand example.
https://github.com/erwbgy/puppet-ntp
The ntp documentation says
snip
Specify a list of time servers to use:
class { 'ntp':
servers = [ 'ntp1.domain.com', 'ntp2.domain.com' ],
}
endsnip
If I enter it like this in my manifest, I get errors. I assume the correct
syntax is something more like this
snip
system::ntp { 'name':
servers = [ 'ntp1.domain.com', 'ntp2.domain.com' ],
}
endsnip
but that syntax gets me this error
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type system::ntp at /etc/puppet/manifests/site.pp:36 on node
Any help with this would be appreciated..
thanks!
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: syntax problems trying to use Keith Burdis's erwbgy/system module without Hiera
And just to have an answer on the list as well, the syntax in the docs is
correct. Though it might be class { system::ntp in your case. Not sure of
the specifics of that module.
http://docs.puppetlabs.com/puppet/3/reference/lang_classes.html#using-resource-like-declarations
On Thursday, March 21, 2013 1:09:02 PM UTC-7, John Smith wrote:
I'm trying to use Keith Burdis's excellent erwbgy/system module without
Hiera, at least initially.
http://forge.puppetlabs.com/erwbgy/system
I cannot determine how call the modules. From what I can tell the
documentation isn't quite correct (or I am reading it wrong). I'm trying
to start with ntp because that's an easy to understand example.
https://github.com/erwbgy/puppet-ntp
The ntp documentation says
snip
Specify a list of time servers to use:
class { 'ntp':
servers = [ 'ntp1.domain.com', 'ntp2.domain.com' ],
}
endsnip
If I enter it like this in my manifest, I get errors. I assume the correct
syntax is something more like this
snip
system::ntp { 'name':
servers = [ 'ntp1.domain.com', 'ntp2.domain.com' ],
}
endsnip
but that syntax gets me this error
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type system::ntp at /etc/puppet/manifests/site.pp:36 on node
Any help with this would be appreciated..
thanks!
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: syntax problems trying to use Keith Burdis's erwbgy/system module without Hiera
On Thursday, March 21, 2013 1:58:10 PM UTC-7, Ellison Marks wrote:
And just to have an answer on the list as well, the syntax in the docs is
correct. Though it might be class { system::ntp in your case. Not sure of
the specifics of that module.
http://docs.puppetlabs.com/puppet/3/reference/lang_classes.html#using-resource-like-declarations
I'm just trying to call his ntp module now and have removed system. I
still can't make it work... Here's my code
snip
include ntp
class ntp { 'ntp':
servers = [ 'ntp1.domain.com', 'ntp2.domain.com' ],
}
endsnip
and here's my error:
Could not parse for environment dev: Syntax error at ':'; expected '}' at
/etc/puppet/manifests/site.pp:35 on node
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Windows agent got a 'puppet:///' file source error
Hi,
I'm trying to run puppet agent from Windows Server 2008 R2, puppet version
is 3.0.2.
The puppet master is running on RHEL 5.8, version is 3.1.1
I'm running a simple task: downloading a file, TableauServer.exe, from the
master. The manifest, /etc/puppet/modules/tableau/manifests/init.pp, is as
follows:
class tableau::install {
file {'c:/temp.install':
ensure = 'directory',
}
file { 'c:/temp.install/TableauServer.exe':
ensure = 'present',
require = File['c:/temp.install'],
source = 'puppet:///modules/tableau/TableauServer.exe',
}
}
class tableau {
notify {'Module: tableau':}
include tableau::install
}
At the agent site, I got the error:
C:\Windows\system32puppet agent --test --trace
Info: Retrieving plugin
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/facter_dot_d.rb
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/puppet_vardir.rb
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/root_home.rb
Info: Caching catalog for mnappmktxwin2
Info: Applying configuration version '1363898070'
Notice: Module: tableau
Notice: /Stage[main]/Tableau/Notify[Module: tableau]/message: defined
'message' as 'Module: tableau'
Error:
/Stage[main]/Tableau::Install/File[c:/temp.install/TableauServer.exe]:
Could not evaluate: Co
uld not retrieve information from environment production source(s)
puppet:///modules/tableau/Tableau
Server.exe
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/util/errors.rb:60:in `fail'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/type/file/source.rb:166:in `metadata'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/type/file/source.rb:112:in `copy_source_
values'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/type/file.rb:632:in `retrieve'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/type.rb:693:in
`retrieve_resource'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:32:in `p
erform_changes'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:133:in `
evaluate'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:49:in `apply'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:84:in `eval_resource'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:104:in `evaluate'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:344:in
`thinmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/sys/ruby/lib/ruby/1.8/benchmark.rb:308:in `realtime'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:343:in
`thinmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:104:in `evaluate'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:383:in `traverse'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:99:in `evaluate'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/resource/catalog.rb:144:in `apply'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/configurer.rb:122:in `apply_catalog'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:179:in
`benchmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/sys/ruby/lib/ruby/1.8/benchmark.rb:308:in `realtime'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:178:in
`benchmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/configurer.rb:121:in `apply_catalog'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/configurer.rb:179:in `run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/agent/locker.rb:20:in `lock'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/sys/ruby/lib/ruby/1.8/sync.rb:230:in `synchronize'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in
`run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:119:in
`with_client'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:42:in
`run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:84:in
`run_in_fork'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:41:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/application.rb:175:in `call'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/application.rb:175:in `controlled_run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:39:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/application/agent.rb:338:in `onetime'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/application/agent.rb:312:in `run_command
'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/application.rb:346:in `run'
[Puppet Users] apt-get update before installing a package. The right way?
Hi,
I've been battling with trying to get our puppet to do the following:
Install all sources.list, apt-keys
then:
Run an apt-get update
then:
install Packages
I've tried a few ways.
1. Set a default requires
Package {
require = Exec['apt_update']
}
This doesn't work, I think because some packages have a requires attribute
and so this gets overridden.
2. Stages
I get into huge dependency cycles doing this because I have classes that
need apt sources that pull in other classes too, eg nagios.
3. Collectors
Exec['apt_update'] - Package | |
This works the best but (and it's a huge but) it installs all our virtual
packages everywhere.
What would be great would be if I could do:
Exec['apt_update'] - Package
But this isn't valid.
Does anyone have a sure fire way to get this to work in a large environment?
We're using the puppetlabs apt class by the way and many other 3rd party
modules.
Thanks,
Sam
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Windows Reboot
Hi Rich,
On Wed, Mar 20, 2013 at 5:54 AM, Rich Siegel rismo...@gmail.com wrote:
My idea on reboots is different. I don't think we should have puppet do
the reboot. If we go down this road, we need autologon, credentials,
runonce, and a subsequent puppet agent run among other things.
Why do we need autologon and credentials?
Since puppet is typically running as an automatic windows service, it will
run immediately after machine reboot, and re-apply the catalog, picking up
where it left off (assuming the resources leading up the reboot are
correctly idempotent).
If you don't run puppet as a service, then you're probably going to need an
external orchestration process.
Not ideal if a puppet agent service is running during business time.
This is orchestration and not where puppet should not be trying to succeed.
Sure, mcollective could be used to reboot en masse during a scheduled
maintenance windows, e.g. reboot all hosts where the reboot_pending fact is
true. But not everyone has or wants to setup mcollective, and reboots are a
common requirement on windows.
Originally I thought I needed a facter fact to determine if a reboot
pending state existed, but the problem is that the facts are determined
upfront. So if a resource triggers a state where a reboot is needed the
fact is busted.
I think we need a new embedded construct which can check the reboot state
before processing every resource. It has to happen before it makes it to
the provider since it should not be left to a provider author as it could
apply to any resource. If this boolean goes true then every resource in
that graph needs to be skipped.
So suppose we added a metaparameter to check if a reboot is pending, and
the metaparameter is set on a particular resource, e.g. package.
package { 'somepackage':
source = 'some.msi',
reboot_pending = check
}
Internally, that metaparameter could create an instance of a reboot_pending
resource, and setup a before/require relationship:
reboot_pending { '...':
before = Package['somepackage']
}
If the reboot_pending provider determines a reboot is necessary, then it
would cancel the transaction loop, causing all remaining resources to be
skipped. Puppet would remain in this state until the pending reboot is
cleared.
I don't think both approaches are mutually exclusive, though I think they
are modeling different things. The provider I created is about performing a
reboot as a result of another resource being applied (in cases where you
know a priori that a reboot will be necessary). Unfortunately, puppet
doesn't have a general mechanism for sending different types of events, so
all we know is the package was installed, but not whether it required a
reboot as a result.
The other approach, e.g. reboot_pending, is about modeling the reboot
pending state of the machine. This would be useful in cases where you don't
know ahead of time if a reboot will be necessary, or in cases that require
multiple reboots,
I think you could even combine them together in cases where you want puppet
to both detect that a reboot is pending and do the reboot:
package { 'somepackage':
source = 'some.msi',
reboot_pending = check
}
reboot_pending { 'somepackage':
before = Package['somepackage'],
}
reboot { 'now':
subscribe = Reboot_pending['somepackage'],
}
A meta param can be added to say reboot = force which can force a
resource to be processed _despite_ the boolean.
Isn't that the same as not specifying a reboot metaparameter? Or are you
saying only apply that resource, and skip the rest?
I also need way to stateful trigger reboot flag like a lockfile so I can
do a bios upgrade.
As a way of preventing puppet from applying changes? If so, you could add
an entry to the registry to make the system think a reboot is necessary.
Actually _rebooting_ with puppet I am leery of. I welcome all input on
this.
--
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 to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Josh
--
Josh Cooper
Developer, Puppet Labs
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Windows agent got a 'puppet:///' file source error
Are the permissions ok on that file? That is, is it readable by the master?
On Thursday, March 21, 2013 2:17:19 PM UTC-7, RAM wrote:
Hi,
I'm trying to run puppet agent from Windows Server 2008 R2, puppet version
is 3.0.2.
The puppet master is running on RHEL 5.8, version is 3.1.1
I'm running a simple task: downloading a file, TableauServer.exe, from the
master. The manifest, /etc/puppet/modules/tableau/manifests/init.pp, is as
follows:
class tableau::install {
file {'c:/temp.install':
ensure = 'directory',
}
file { 'c:/temp.install/TableauServer.exe':
ensure = 'present',
require = File['c:/temp.install'],
source = 'puppet:///modules/tableau/TableauServer.exe',
}
}
class tableau {
notify {'Module: tableau':}
include tableau::install
}
At the agent site, I got the error:
C:\Windows\system32puppet agent --test --trace
Info: Retrieving plugin
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/facter_dot_d.rb
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/puppet_vardir.rb
Info: Loading facts in
C:/ProgramData/PuppetLabs/puppet/var/lib/facter/root_home.rb
Info: Caching catalog for mnappmktxwin2
Info: Applying configuration version '1363898070'
Notice: Module: tableau
Notice: /Stage[main]/Tableau/Notify[Module: tableau]/message: defined
'message' as 'Module: tableau'
Error:
/Stage[main]/Tableau::Install/File[c:/temp.install/TableauServer.exe]:
Could not evaluate: Co
uld not retrieve information from environment production source(s)
puppet:///modules/tableau/Tableau
Server.exe
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/util/errors.rb:60:in `fail'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/type/file/source.rb:166:in `metadata'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/type/file/source.rb:112:in `copy_source_
values'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/type/file.rb:632:in `retrieve'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/type.rb:693:in
`retrieve_resource'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:32:in `p
erform_changes'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction/resource_harness.rb:133:in `
evaluate'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:49:in `apply'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:84:in `eval_resource'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:104:in `evaluate'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:344:in
`thinmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/sys/ruby/lib/ruby/1.8/benchmark.rb:308:in `realtime'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:343:in
`thinmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:104:in `evaluate'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:383:in `traverse'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/transaction.rb:99:in `evaluate'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/resource/catalog.rb:144:in `apply'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/configurer.rb:122:in `apply_catalog'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:179:in
`benchmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/sys/ruby/lib/ruby/1.8/benchmark.rb:308:in `realtime'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/util.rb:178:in
`benchmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/configurer.rb:121:in `apply_catalog'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/configurer.rb:179:in `run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/agent/locker.rb:20:in `lock'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/sys/ruby/lib/ruby/1.8/sync.rb:230:in `synchronize'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:45:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/agent.rb:119:in `with_client'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:42:in
`run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:84:in
`run_in_fork'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:41:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/application.rb:175:in `call'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/application.rb:175:in `controlled_run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/agent.rb:39:in
`run'
C:/Program Files (x86)/Puppet
[Puppet Users] Re: syntax problems trying to use Keith Burdis's erwbgy/system module without Hiera
On Thursday, March 21, 2013 2:10:20 PM UTC-7, John Smith wrote:
On Thursday, March 21, 2013 1:58:10 PM UTC-7, Ellison Marks wrote:
And just to have an answer on the list as well, the syntax in the docs is
correct. Though it might be class { system::ntp in your case. Not sure of
the specifics of that module.
http://docs.puppetlabs.com/puppet/3/reference/lang_classes.html#using-resource-like-declarations
I'm just trying to call his ntp module now and have removed system. I
still can't make it work... Here's my code
snip
include ntp
class ntp { 'ntp':
This syntax is incorrect. Not class ntp { 'ntp'. Just class { 'ntp',
like it says in the docs. If that's giving you an error, post it.
servers = [ 'ntp1.domain.com', 'ntp2.domain.com' ],
}
endsnip
and here's my error:
Could not parse for environment dev: Syntax error at ':'; expected '}' at
/etc/puppet/manifests/site.pp:35 on node
--
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
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Windows agent got a 'puppet:///' file source error
On Thu, Mar 21, 2013 at 4:20 PM, Ellison Marks gty...@gmail.com wrote:
Are the permissions ok on that file? That is, is it readable by the master?
On Thursday, March 21, 2013 2:17:19 PM UTC-7, RAM wrote:
Hi,
I'm trying to run puppet agent from Windows Server 2008 R2, puppet
version is 3.0.2.
The puppet master is running on RHEL 5.8, version is 3.1.1
I'm running a simple task: downloading a file, TableauServer.exe, from
the master. The manifest, /etc/puppet/modules/tableau/**manifests/init.pp,
is as follows:
class tableau::install {
file {'c:/temp.install':
ensure = 'directory',
}
file { 'c:/temp.install/**TableauServer.exe':
ensure = 'present',
require = File['c:/temp.install'],
source = 'puppet:///modules/tableau/**TableauServer.exe',
}
}
class tableau {
notify {'Module: tableau':}
include tableau::install
}
At the agent site, I got the error:
C:\Windows\system32puppet agent --test --trace
Info: Retrieving plugin
Info: Loading facts in C:/ProgramData/PuppetLabs/**
puppet/var/lib/facter/facter_**dot_d.rb
Info: Loading facts in C:/ProgramData/PuppetLabs/**
puppet/var/lib/facter/puppet_**vardir.rb
Info: Loading facts in C:/ProgramData/PuppetLabs/**
puppet/var/lib/facter/root_**home.rb
Info: Caching catalog for mnappmktxwin2
Info: Applying configuration version '1363898070'
Notice: Module: tableau
Notice: /Stage[main]/Tableau/Notify[**Module: tableau]/message: defined
'message' as 'Module: tableau'
Error:
/Stage[main]/Tableau::Install/**File[c:/temp.install/**TableauServer.exe]:
Could not evaluate: Co
uld not retrieve information from environment production source(s)
puppet:///modules/tableau/**Tableau
Server.exe
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**util/errors.rb:60:in
`fail'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**type/file/source.rb:166:in
`metadata'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**type/file/source.rb:112:in
`copy_source_
values'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**type/file.rb:632:in
`retrieve'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**type.rb:693:in
`retrieve_resource'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**
transaction/resource_harness.**rb:32:in `p
erform_changes'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**
transaction/resource_harness.**rb:133:in `
evaluate'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**transaction.rb:49:in
`apply'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**transaction.rb:84:in
`eval_resource'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**transaction.rb:104:in
`evaluate'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**util.rb:344:in
`thinmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/sys/ruby/lib/ruby/**1.8/benchmark.rb:308:in
`realtime'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**util.rb:343:in
`thinmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**transaction.rb:104:in
`evaluate'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**transaction.rb:383:in
`traverse'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**transaction.rb:99:in
`evaluate'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**resource/catalog.rb:144:in
`apply'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**configurer.rb:122:in
`apply_catalog'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**util.rb:179:in
`benchmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/sys/ruby/lib/ruby/**1.8/benchmark.rb:308:in
`realtime'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**util.rb:178:in
`benchmark'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**configurer.rb:121:in
`apply_catalog'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**configurer.rb:179:in
`run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**agent.rb:45:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**agent/locker.rb:20:in
`lock'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**agent.rb:45:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/sys/ruby/lib/ruby/**1.8/sync.rb:230:in
`synchronize'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**agent.rb:45:in
`run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**agent.rb:119:in
`with_client'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**agent.rb:42:in
`run'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**agent.rb:84:in
`run_in_fork'
C:/Program Files (x86)/Puppet Labs/Puppet/puppet/lib/puppet/**agent.rb:41:in
`run'
C:/Program Files (x86)/Puppet
Labs/Puppet/puppet/lib/puppet/**application.rb:175:in
`call'
C:/Program Files (x86)/Puppet
[Puppet Users] Re: Need a puppet manifest to initialize a puppetmaster
I guess I should also mention that I am using Ubuntu 12.04. Also, when I say run a puppet command, I'm referring to puppet apply -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Augeas lens dependency on valid config file parsing
Hi All, I just ran into a frustrating Augeas problem, which I thought I'd share with you all. We run a cron every morning to fetch the latest RPMs (for the packages we're interested in) from various places such as rpmforge, EPEL, etc. This morning I tried to build a VM and it failed. What happened was that last night, a new version of nagios-nrpe was downloaded so the VM that was built had this latest version. The RPM includes nrpe.cfg which had a new option added to it: allow_bash_command_substitution=0 In the manifest, I have an augeas block to modify the allowed_hosts line in the nrpe.cfg file. Puppet was failing giving a Save failed error message, so I went in via augtool to see what's going on. I noticed that it could not parse nrpe.cfg (i.e. ls /files/etc/nagios returned nothing). I had the previous config file saved for NRPE somewhere, so I diff'ed them and noticed the only new option is the option I mentioned above. After removing this new option, augtool could parse the file again and Puppet was happy. After having a quick read of the nrpe.lns file inside augeas-libs, I noticed it actually lists each of the options that it will recognise from the config file, and evidently fails if it finds new options that it doesn't recognise. Anyway, it hit me that there is quite a big dependency between config files and augeas lenses. A change in one config file can affect Augeas which affects Puppet runs. Or is this just a poorly written lens? - Gonzalo -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Announce: Puppet Dashboard 1.2.23 Available
Fair point. The documentation was written before we built shipped
our ruby 1.8.7 for el5, and was not updated to reflect the fact that
this is now available via the Puppet Labs yum repositories. I'll make
sure this gets updated.
On Thu, Mar 21, 2013 at 12:48 PM, Dan White y...@comcast.net wrote:
The documentation is a bit contradictory.
It says you need ruby 1.8.7, and then says you cannot use it with
CentOS/RHEL-5 'cause the supported version of ruby is 1.8.7
It totally ignores the Puppet dependencies repos, which contain ruby 1.8.7
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin Hobbes)
From: Moses Mendoza mo...@puppetlabs.com
To: puppet-users@googlegroups.com, puppet-...@googlegroups.com,
puppet-annou...@googlegroups.com
Sent: Thursday, March 21, 2013 3:28:46 PM
Subject: [Puppet Users] Announce: Puppet Dashboard 1.2.23 Available
Puppet Dashboard 1.2.23 is a maintenance release of the 1.2 series of
Puppet Dashboard with bug fixes and minor features.
This release is available for download at:
https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23.tar.gz
Available in native package format in the Puppet Labs yum and apt
repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.2.23:
http://projects.puppetlabs.com/projects/dashboard
Documentation is available at:
http://docs.puppetlabs.com/dashboard/index.html
Contributors:
Aaron Stone, Daniel Pittman, Dustin J. Mitchell, Ken Barber, Matthaus
Owens, Moses Mendoza, and fhrbek
=
## Puppet Dashboard 1.2.23 Release Notes ##
=
Comment out specific gem rack version in our vendored Rails
* addresses http://projects.puppetlabs.com/issues/11669
(#17914) Store FlashHash as a normal Hash in session
This patch is a backport of:
https://github.com/rails/rails/commit/36376560fdd02f955ae3bf6b7792b784443660ad
In the form of a monkey patch in the puppet-dashboard initializer stage.
This is required to allow puppet-dashboard to co-exist with other
applications
that do not have the full rails stack in their namespace. Without it,
other
non-rails applications (such as the certificate service and live
management)
are unable to unmarshal cookies created in Rails. Instead, they
invalidate the
session and we start to see weird authentication glitches in the GUI.
In essence this patch ensures that when the FlashHash data is
stored in a cookie
it is stored as a normal Ruby Hash, as apposed to an
ActionController::Flash::FlashHash. As all other Ruby applications
should be
able to unmarshal a Hash, this will avoid the Marshal.load method in
Rack::Session::Cookie from throwing a NameError exception.
Signed-off-by: Ken Barber k...@bob.sh
Add addgroup, addclass, listgroups, listclasses tasks for nodes
Previously if a user wanted to use rake tasks to interrogate the
dashboard
about which groups or classes a node belonged to, they would be out of
luck.
Similarly, if a user wanted to add a class or group to a node
without replacing
the already assigned classes/groups of a node it was not possible via
only
rake. This commit adds a task in the node namespace to add a group
or groups to
a node and to add a class or classes to a node. The other two
tasks added here
list out the groups or classes already assigned to a node.
(#16429) Fix relative URLs of icons in tables.css
These links work when puppet-dashboard is at the top level because
browsers treat /../ as equivalent to /.
==
## Puppet Dashboard 1.2.23 Changelog ##
==
Aaron Stone (11):
e56a1dd Travis for master branch.
5584128 Issue 11760: Remove unused Services view.
2c9c954 Bug fix: inherited_resources using deprecated
{{mustache}} syntax instead of %{newer} syntax
a4b73a9 Spec fix to 04b4c0f use should be_any instead of array
indexing.
b98ef7e Node and Group parameters rake tasks should not create
duplicate entries. Fixes #13867, updates commit 0108c040 to behave as
intended.
792d74a Check that the reports import dir exists, is a
directory, is readable. #18512
7bc9438 puts is STDOUT.puts
7ea8816 Change deprecated 'ftools' to 'fileutils'.
c244fa2 Daemonize in the Debian / Ubuntu server init.
2b0aad4 Tighten up code for rake api tasks, and move common
get_node get_group and get_class methods into a shared helper file.
7753bc5 Comment out specific gem rack version in our vendored Rails
Daniel Pittman (1):
e362172 (#19304) Upgrade to json_pure 1.7.7 for CVE-2013-0269
Dustin
Re: [Puppet Users] Redmine upgrade beginning
These should be back now the votes weren't lost and they still showed up on the query page, but the voting plugin had to be enabled per project to make the arrows and vote count render on an individual issue pages. Thanks to Zach Leslie for flipping the right bit. Eric Sorenson - eric.soren...@puppetlabs.com irc.freenode.net #puppet: eric0 Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 On Mar 18, 2013, at 1:32 PM, Hunter Haugen hun...@puppetlabs.com wrote: Looks like the upvote/downvote buttons are missing. (/red(dit|mine)/ anyone?) -Hunter On Thu, Mar 14, 2013 at 5:41 PM, Eric Sorenson eric.soren...@puppetlabs.com wrote: On Mar 14, 2013, at 5:12 PM, Eric Sorenson eric.soren...@puppetlabs.com wrote: Hi, we're starting the upgrade to projects.puppetlabs.com now. There will be a brief downtime as the old host's database is dumped and imported on the new box, then your requests should hit newprojects.puppetlabs.com until DNS propagates. This is done; please let me know if you run into any trouble using the new Redmine site. Eric Sorenson - eric.soren...@puppetlabs.com #puppet irc: eric0 -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
