[Puppet Users] Do you want a Puppet Conference in Berlin, Germany
Hello everybody, I am thinking about running a Puppet Conf in Berlin/Germany. Are there any people on this list from nearby? Do you want to support (talk, workshop)? Many thanks, Martin -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Do you want a Puppet Conference in Berlin, Germany
Hi. I'd be in (with enough notice, of course). I'd be even more in if the conference was on the other side of Germany near Cologne or even in Belgium. I'm assuming you already have a space you can use in Berlin, though? -G (located near Cologne) On Mon, Nov 19, 2012 at 3:02 AM, Martin Alfke tux...@gmail.com wrote: Hello everybody, I am thinking about running a Puppet Conf in Berlin/Germany. Are there any people on this list from nearby? Do you want to support (talk, workshop)? Many thanks, Martin -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- --- Geoff Galitz, ggal...@shutterstock.com WebOps Shutterstock Images -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Do you want a Puppet Conference in Berlin, Germany
On 19.11.2012, at 09:06, Geoff Galitz wrote: Hi. I'd be in (with enough notice, of course). I'd be even more in if the conference was on the other side of Germany near Cologne or even in Belgium. I'm assuming you already have a space you can use in Berlin, though? -G (located near Cologne) Hi Ralf, we plan to get the conference into the BCC (directly at Alexanderplatz, where Chaos Communication Congress took place until last year). But this is not confirmed yet. Due to the reason that 2013 schedule is filling up very fast we only have two options left: - February 2013 or - late November 2013 Many thanks, Martin On Mon, Nov 19, 2012 at 3:02 AM, Martin Alfke tux...@gmail.com wrote: Hello everybody, I am thinking about running a Puppet Conf in Berlin/Germany. Are there any people on this list from nearby? Do you want to support (talk, workshop)? Many thanks, Martin -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- --- Geoff Galitz, ggal...@shutterstock.com WebOps Shutterstock Images -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Do you want a Puppet Conference in Berlin, Germany
I'm only one man so don't make all your decisions around me, but do you happen to know the specific dates for those two months? Those just happen to be two difficult months for me. If necessary I can help to arrange a space on a different date. -G On Mon, Nov 19, 2012 at 3:09 AM, Martin Alfke tux...@gmail.com wrote: On 19.11.2012, at 09:06, Geoff Galitz wrote: Hi. I'd be in (with enough notice, of course). I'd be even more in if the conference was on the other side of Germany near Cologne or even in Belgium. I'm assuming you already have a space you can use in Berlin, though? -G (located near Cologne) Hi Ralf, we plan to get the conference into the BCC (directly at Alexanderplatz, where Chaos Communication Congress took place until last year). But this is not confirmed yet. Due to the reason that 2013 schedule is filling up very fast we only have two options left: - February 2013 or - late November 2013 Many thanks, Martin On Mon, Nov 19, 2012 at 3:02 AM, Martin Alfke tux...@gmail.com wrote: Hello everybody, I am thinking about running a Puppet Conf in Berlin/Germany. Are there any people on this list from nearby? Do you want to support (talk, workshop)? Many thanks, Martin -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- --- Geoff Galitz, ggal...@shutterstock.com WebOps Shutterstock Images -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- --- Geoff Galitz, ggal...@shutterstock.com WebOps Shutterstock Images -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Do you want a Puppet Conference in Berlin, Germany
Hi Martin, I'm interested, depending on the actual date.. My location is near Stuttgart, not exactly around the corner, but Berlin isn't that much further away than Amsterdam. :) Do you have a tentative list of topics, maybe there's something where I could help out? Cheers, Thorsten On Mon, Nov 19, 2012 at 9:02 AM, Martin Alfke tux...@gmail.com wrote: Hello everybody, I am thinking about running a Puppet Conf in Berlin/Germany. Are there any people on this list from nearby? Do you want to support (talk, workshop)? Many thanks, Martin -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Do you want a Puppet Conference in Berlin, Germany
Geoff Galitz wrote: Hi. I'd be in (with enough notice, of course). I'd be even more in if the conference was on the other side of Germany near Cologne or even in Belgium. I'm assuming you already have a space you can use in Berlin, though? Geoff We're also going to have a PuppetCamp in Ghent, Belgium - probably before or after FOSDEM in 2013. Regards James -- James Turnbull Puppet Labs 1-503-734-8571 To schedule a meeting with me: http://doodle.com/jamtur01 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] puppet-dashboard - rake API not working
Hello all, I am quite new to the puppet arena, but I am really impressed with puppet as a tool and the possibilities it gives you with regards to managing many systems. I am running dashboard 1.2.14 and am trying to query via the rake API: http://docs.puppetlabs.com/dashboard/manual/1.2/rake_api.html when I do, I get the following error: snip # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 'node:list' (in /var/log) config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rack-1.1.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem json_pure-1.5.1 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are deprecated. Use lib/tasks instead. (called from /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10) /snip ...I fail to find any info on this online ... has anyone else seen this? Thanks, //Jacob. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/oM7WDU0rDlsJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppet DB for inventory
Perfect. Thank you - I actually came across this URL and have read through it. Thanks for your reply On Sunday, November 18, 2012 10:07:44 PM UTC, Felipe Salum wrote: http://docs.puppetlabs.com/puppetdb/1/using.html#using-the-inventory-service If you are using puppetdb backend you just need to enable the dashboard inventory service and it will automatically get the inventory information from puppetdb. No more need to add those mysql settings on puppet.conf for the inventory service. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/egkVPcJvd8AJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet version 2.7 or 3?
On Sat, 17 Nov 2012 07:20:18 +0200, Ohad Levy ohadl...@gmail.com wrote: On Fri, Nov 16, 2012 at 10:10 AM, Thomas Bendler thomas.bend...@gmail.comwrote: Hi Ohad, 2012/11/16 Ohad Levy ohadl...@gmail.com [...] For the record, Puppet 3 support was added to foreman a couple of days ago. [...] do you know when the puppet 3 support will be available in the test RPMs? I've updated to the current test RPMs yesterday but still had to patch some files in foreman and foreman-proxy to get it working with Puppet 3. You would need the nightly rpms, hopefully we'll get a RC soon. Err, the puppet 3 support has not yet landed in the nightly RPMs. I just tried. http://theforeman.org/projects/foreman/repository/revisions/e81bf0573125fa569e35f991df451cb9e4e8a948/diff is missing in bash-4.1$ rpm -qa | grep foreman foreman-1.0.1-4.20121022.el6.noarch foreman-postgresql-1.0.1-4.20121022.el6.noarch foreman-proxy-1.0.0-3.20121022.el6.noarch [root@viepclvx-e15 foreman]# grep PUPPETVERSION /usr/share/foreman/lib/foreman/default_settings/loader.rb [root@viepclvx-e15 foreman]# Best Regards, David -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Question about PuppetDB queries
Hello, We get a good amount of warnings regarding queries that couldn't be executed within the threshold. There are 2 types of queries that usually get logged with this warning, I just wanted to ask if these queries look normal, because we cannot really judge, as we're fairly new to PuppetDB. Especially the second one looks weird, and it also makes our logfile grow fast. Example for type 1 : http://pastebin.com/exNG2bCj Example for type 2 (this is actually one single entry in the log) : http://pastebin.com/ym9AHPSk Thanks in advance! Cheers, ak0ska -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/x4ClCvRbyOYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Puppet version 2.7 or 3?
On Mon, 19 Nov 2012 11:21:34 +0100, David Schmitt da...@dasz.at wrote: bash-4.1$ rpm -qa | grep foreman foreman-1.0.1-4.20121022.el6.noarch foreman-postgresql-1.0.1-4.20121022.el6.noarch foreman-proxy-1.0.0-3.20121022.el6.noarch That I didn't notice, is that those are from 2012-10-22, which is not quite nightly. Seems like the repo at http://yum.theforeman.org/nightly/el6/x86_64/?C=M;O=D has stopped updating? Best Regards, David -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet passing an array to a define to move directories
You are passing an array (dir_name) into a single resource. Instead you
want to create three separate resources:
module_name::move { [ dir1, dir2, dir3 ]: ... }
Also, I feel compelled to point out that having verbs or actions as names
of resources is a big red warning flag, that you're doing something outside
the intended design of puppet. e.g. are you aware that your define will try
to move the directories every time you run the agent with this?
Best Regards, David
On Sun, 18 Nov 2012 23:14:29 -0800 (PST), mickael avedissian
xli...@gmail.com wrote:
Hi,
I'm trying to use puppet to move some folders from one directory to
another
in Windows.
That being said I have a parameterized define which looks like that:
define module_name::move ($dir_name, $arg2){
$dir_origin = c:/${dir_name}
$dir_destination = c:/tmp/${arg2}
file { $dir_destination:
ensure = 'directory',
mode = '755',
}
exec { $backup_folder :
command = cmd.exe /c move $dir_origin $dir_destination,
path = 'c:\windows\system32;c:\windows',
}
}
and I call the define as follow:
module_name::move { 'folder_name':
dir_name = ['dir1','dir2','dir3'],
arg2 = blah,
}
when I execute this code, puppet concatenate the value of $dir_name as
dir1dir2dir3 instead of running my define 3 separate times.
I would greatly appreciate getting some help on how I could reach my
purpose.
Thanks,
Mike
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Please document reports:prune Task Leaves Orphaned Data in Dashboard Documentation
On Mon, 19 Nov 2012 09:32:27 +1100, John Warburton jwarbur...@gmail.com wrote: Dear Puppet Labs I recently upgraded dashboard from 1.2.2 to 1.2.14. It was somewhat painful given the number of orphaned records that needed purging during database conversion Some weeks later, my 20 Gb mysql partition fills up with what should be a 1.5 Gb database. I assumed that with the orphaned record script being created, the purging old records would no longer create orphaned records in 1.2.14 I was wrong, and see it is documented for PE ( http://docs.puppetlabs.com/pe/2.0/welcome_known_issues.html#consoles-reportsprune-task-leaves-orphaned-data) but not in the open source dashboard ( http://docs.puppetlabs.com/dashboard/manual/1.2/maintaining.html) Can you please save others my experience and update the open source page? I've created https://projects.puppetlabs.com/issues/17712 for this request Thanks John Also keep in mind that mysql is unable to release table space once it has allocated it. Best Regards, David -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] vcsrepo: Could not create repository (non-repository at path)
Hi,
I'm running into a problem using the puppetlabs provided vcsrepo-module. It
keeps giving the same error:
--
notice: /Stage[main]//Vcsrepo[/usr/share/test2]/ensure: Creating repository
from latest
err: /Stage[main]//Vcsrepo[/usr/share/test2]/ensure: change from absent to
latest failed: Could not create repository (non-repository at path)
--
This is in my vcs.pp and when I run, puppet apply ./vcs.pp
I keep getting the error below. When I run git clone as the user it runs
fine.
Anybody any suggestions?
--
Exec { path = /bin:/usr/bin:/sbin:/usr/sbin, }
vcsrepo { '/usr/share/test2':
ensure = latest,
provider = git,
revision = 'master',
path= '/usr/share/test2',
user = user,
source =
'git://github.com/puppetlabs/puppetlabs-vcsrepo.git'
}
-
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/Oa4SscXpWJ0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Scope object available functions and getting the local scope, or node scope variable values
On Friday, November 16, 2012 6:30:43 AM UTC-6, Jayapandian Ponraj wrote:
Is there a way to get the local scope values of puppet variables via
scope.? wat r all the available functions in scope? can anyone provide a
working example.
One normally accesses local-scope variables directly, rather than via the
scope object:
$foo = 'bar'
# A stupid way to get the value of foo
$foo_copy = inline_template('%=@foo%')
Alternatively, you should be able to access any global or class variable
via its fully-qualified name, including those from the local scope (if it
is the top-level scope or a class scope).
I suspect that doesn't answer your real question though. As Abhijeet
asked, for what purpose do you want that?
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/dZAhLmTyUB4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How do I uninstall Puppet on Mac?
On Sun, Nov 18, 2012 at 9:35 AM, Laurence Cope amitywebsoluti...@gmail.com wrote: Hi I followed the install instructions to install the dmg package on Mac. I got errors when setting up the group and users, cant find help on that. So I decided to not to use it on my Mac. I will set puppet up on Linux instead. This is likely bug 12833 [1] and will be fixed when Puppet 3.0.2 is released. [1] http://projects.puppetlabs.com/issues/12833 -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Issue with service = disabled and stopped
On Friday, November 16, 2012 6:51:19 PM UTC-6, Steven wrote: If it is happening every time, it is usually an issue with init script. Puppet is not understanding the output of the init script, so it is not saving the correct state. Minor correction: it's not about what state Puppet saves, but rather about what state Puppet *detects*. Supposing that Puppet is using the redhat Service provider (since you mention chkconfig), it is determining the services' state via the exit code of command /sbin/service servicename status, with reference to the LSB standard for initscript exit codes. Hence Steven's suggestion to Run the init script manually and see what it is returning. If it is not obvious, run puppet with --debug and see the exact command puppet is running I note, however, that Redhat Linuxes and their derivatives (i.e. RHEL, Fedora, CentOS, Scientific Linux, etc.) are very reliable with respect to standards conformance in this area, so it's a bit strange to see a problem such as you describe on a system that appears to be in that class. Are you certain that the agent is running Puppet 2.7.19? The Service type has a parameter 'hasstatus' which used to default to false, but now defaults to true. Back when it defaulted to false, you would typically want to set it true where your initscript provided a standard-compliant 'status' command, and elsewhere you would sometimes need to set an explicit status testing command via the 'status' parameter. Of course, the flip side is that with recent Puppet, if your initscript does not support 'status' correctly, and you can't or won't fix it, then you need to tell Puppet hasstatus = false and status = command-to-determine-status. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ZTpLGYwQ2qkJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Dynamic Collection?
On Sunday, November 18, 2012 12:13:20 PM UTC-6, Rajul Vora wrote: From official documentation: User | (group == dba or group == sysadmin) or title == luke | You are missing Nick's point. In your example, you declare *secondary*groups for your users via their 'groups' properties, then you try to collect them based on a predicate testing the *primary* group (the 'group' property). These are separate, uncorrelated properties. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Wmd0Z4rhkOUJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: HOME is not set when running post-installation script on Ubuntu
On Sunday, November 18, 2012 1:36:18 PM UTC-6, Rajul Vora wrote: Trying to install mcollective with RabbitMQ. The following package install produces the errors listed below in Bold. I know exec resource unsets HOME and USER now starting with 3.0 and the workaround for that is to set environment = 'HOME=/root' for the exec resource. It looks like it is the same situation when running post-installation script during package install. And there doesn't seem to be any workaround for that since one can not pass environment parameter to package install. Any ideas how to solve this? Report the problem to the package provider; it is his. No package should be sensitive to the environment in which the package manager runs. If it is, that defeats a key objective of using packages in the first place: reliable, consistent installs. Indeed, that's exactly what has happened to you. In the meantime, your best alternative is to build a local, bugfixed version of the package, and to load it from your own local repository in preference to the buggy one. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/_wQ3gCrOnGEJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Scope problem in 2.7.12, bug?
On Sunday, November 18, 2012 2:35:56 PM UTC-6, Walter Heck - OlinData.com
wrote:
Hello,
On Sun, Nov 18, 2012 at 6:47 PM, Stefan Heijmans
heij...@rechtspraak.nl javascript: wrote:
No, i's not, it is correct, see
http://docs.puppetlabs.com/guides/scope_and_puppet.html
At the moment you 'include mysql' only the top scope package variable is
known, so there fore mysql package will be installed.
swap them around and mysql-server package will get installed.
but I am specifically referring to _not_ the top-scope variable by
using $mysql_server::package. This is a scope that doesn't have that
variable (yet, anyway). I don't expect Puppet to just jump to a higher
level scope (top-scope in this case) to go and look for my variable
there.
I agree, it looks like a bug to me. A variable reference should never
evaluate a variable that doesn't match the given name. I would file a
ticket.
The issue may be less straightforward than it first appears, however.
Consider the difference between $mysql_server::package and
$::mysql_server::package. In the vast majority of cases, I would expect
them to evaluate to the same thing (including manifesting the same bug in
this case). But what if there were also this class:
class mysql::mysql_server {
$package = 'mysql-server55'
}
Assume that mysql::mysql_server is declared before class mysql. What value
do you then expect when class mysql dereferences $mysql_server::package?
That is, do you get mysql-server from $::mysql_server::package or
mysql-server55 from $::mysql::mysql_server::package? I think you get the
latter, and I think that's reasonable. Moreover, I would guess that the
support for that behavior is where the bug is hiding.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/wGKqPfk4ZQgJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet passing an array to a define to move directories
Thank you for your answer Dave.
This is the intended purpose of having the puppet agent move those folders
every time it is called.
Would it be an easier (more proper) way of doing it?
Thanks,
Mike
On Monday, November 19, 2012 6:22:55 AM UTC-5, David Schmitt wrote:
You are passing an array (dir_name) into a single resource. Instead you
want to create three separate resources:
module_name::move { [ dir1, dir2, dir3 ]: ... }
Also, I feel compelled to point out that having verbs or actions as names
of resources is a big red warning flag, that you're doing something
outside
the intended design of puppet. e.g. are you aware that your define will
try
to move the directories every time you run the agent with this?
Best Regards, David
On Sun, 18 Nov 2012 23:14:29 -0800 (PST), mickael avedissian
xli...@gmail.com javascript: wrote:
Hi,
I'm trying to use puppet to move some folders from one directory to
another
in Windows.
That being said I have a parameterized define which looks like that:
define module_name::move ($dir_name, $arg2){
$dir_origin = c:/${dir_name}
$dir_destination = c:/tmp/${arg2}
file { $dir_destination:
ensure = 'directory',
mode = '755',
}
exec { $backup_folder :
command = cmd.exe /c move $dir_origin $dir_destination,
path = 'c:\windows\system32;c:\windows',
}
}
and I call the define as follow:
module_name::move { 'folder_name':
dir_name = ['dir1','dir2','dir3'],
arg2 = blah,
}
when I execute this code, puppet concatenate the value of $dir_name as
dir1dir2dir3 instead of running my define 3 separate times.
I would greatly appreciate getting some help on how I could reach my
purpose.
Thanks,
Mike
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/pP7RbRfgngIJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How do I uninstall Puppet on Mac?
Ah right. that may explain the issue then. in that case do you or anyone know how to remove all trace of this install on my Mac? I usually use AppZapper but there is no app created. I cannot see anything to help undo the install. I decided to install some CentOS VMs in VirtualBox to learn Puppet instead (should have done that from the start to be honest). On Monday, 19 November 2012 14:16:38 UTC, Jeff McCune wrote: On Sun, Nov 18, 2012 at 9:35 AM, Laurence Cope amityweb...@gmail.com javascript: wrote: Hi I followed the install instructions to install the dmg package on Mac. I got errors when setting up the group and users, cant find help on that. So I decided to not to use it on my Mac. I will set puppet up on Linux instead. This is likely bug 12833 [1] and will be fixed when Puppet 3.0.2 is released. [1] http://projects.puppetlabs.com/issues/12833 -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/lmwQFByIVOgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Package Provider Continuously Re-installing Packages
We have specified in our manifests some Package resources to install some self-extracting .exe's onto our Windows Puppet machines. Currently we are seeing that our agents are running these installers every Puppet run. We have specified 'ensure = installed' but they are re-installing anyway. We made sure that the installer's are 'behaving-correctly' by checking the registry under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall and confirmed that our installers have the appropriate data in there. We cannot figure out where else to check. Thanks, Reggie -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/m2YS1iIUZIYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet passing an array to a define to move directories
On 2012-11-19 16:22, mickael avedissian wrote:
Thank you for your answer Dave.
This is the intended purpose of having the puppet agent move those
folders every time it is called.
Would it be an easier (more proper) way of doing it?
Without knowing your actual requirements, a possible solution might
involve adding a scheduler task that will move the directories every 30
minutes. This would be much more explicit than whenever puppet is
running, which might be much more often (when
developing/testing/deploying) or much longer (when there's a problem on
the puppet master for example).
Best Regards, David (not Dave).
Thanks,
Mike
On Monday, November 19, 2012 6:22:55 AM UTC-5, David Schmitt wrote:
You are passing an array (dir_name) into a single resource. Instead you
want to create three separate resources:
module_name::move { [ dir1, dir2, dir3 ]: ... }
Also, I feel compelled to point out that having verbs or actions as
names
of resources is a big red warning flag, that you're doing something
outside
the intended design of puppet. e.g. are you aware that your define
will try
to move the directories every time you run the agent with this?
Best Regards, David
On Sun, 18 Nov 2012 23:14:29 -0800 (PST), mickael avedissian
xli...@gmail.com javascript: wrote:
Hi,
I'm trying to use puppet to move some folders from one directory to
another
in Windows.
That being said I have a parameterized define which looks like that:
define module_name::move ($dir_name, $arg2){
$dir_origin = c:/${dir_name}
$dir_destination = c:/tmp/${arg2}
file { $dir_destination:
ensure = 'directory',
mode = '755',
}
exec { $backup_folder :
command = cmd.exe /c move $dir_origin $dir_destination,
path = 'c:\windows\system32;c:\windows',
}
}
and I call the define as follow:
module_name::move { 'folder_name':
dir_name = ['dir1','dir2','dir3'],
arg2 = blah,
}
when I execute this code, puppet concatenate the value of
$dir_name as
dir1dir2dir3 instead of running my define 3 separate times.
I would greatly appreciate getting some help on how I could reach my
purpose.
Thanks,
Mike
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/pP7RbRfgngIJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Do you want a Puppet Conference in Berlin, Germany
On Mon, Nov 19, 2012 at 12:09 AM, Martin Alfke tux...@gmail.com wrote: On 19.11.2012, at 09:06, Geoff Galitz wrote: Hi. I'd be in (with enough notice, of course). I'd be even more in if the conference was on the other side of Germany near Cologne or even in Belgium. I'm assuming you already have a space you can use in Berlin, though? -G (located near Cologne) Hi Ralf, we plan to get the conference into the BCC (directly at Alexanderplatz, where Chaos Communication Congress took place until last year). But this is not confirmed yet. Due to the reason that 2013 schedule is filling up very fast we only have two options left: - February 2013 or - late November 2013 A PuppetCamp in Berlin would be great! We are currently planning several other PuppetCamps in Europe in February, so November might be a little better as long as it doesn't fall too close to the US Thanksgiving holiday (Nov 28 and 29), which might prevent you from getting speakers from Puppet Labs. Most PuppetCamps have us do some kind of opening session (State of Puppet) and possibly one other technical session. We can work together on these kinds of details. Thanks, Dawn Foster -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Dynamic Collection?
Ok, got it. Thanks for that clarification. I totally missed that distinction. Rajul On Mon, Nov 19, 2012 at 6:34 AM, jcbollinger john.bollin...@stjude.orgwrote: On Sunday, November 18, 2012 12:13:20 PM UTC-6, Rajul Vora wrote: From official documentation: User | (group == dba or group == sysadmin) or title == luke | You are missing Nick's point. In your example, you declare *secondary*groups for your users via their 'groups' properties, then you try to collect them based on a predicate testing the *primary* group (the 'group' property). These are separate, uncorrelated properties. John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Wmd0Z4rhkOUJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Rajul Vora -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Package Provider Continuously Re-installing Packages
Hi Reggie, On Mon, Nov 19, 2012 at 7:57 AM, Reginald Choudari adnanchowdhur...@gmail.com wrote: We have specified in our manifests some Package resources to install some self-extracting .exe's onto our Windows Puppet machines. Currently we are seeing that our agents are running these installers every Puppet run. We have specified 'ensure = installed' but they are re-installing anyway. We made sure that the installer's are 'behaving-correctly' by checking the registry under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall and confirmed that our installers have the appropriate data in there. We cannot figure out where else to check. Thanks, Reggie -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/m2YS1iIUZIYJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. Most likely, the package name in your manifest does not match the value of the DisplayName property in the registry, which is also the value displayed in Add/Remove Programs. A quick way to verify this is to install the package using puppet. Then run `puppet resource package name`, also with the name as displayed in Add/Remove Programs. You should see puppet report that the package is installed. [1] http://docs.puppetlabs.com/windows/writing.html#packagepackage -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Getting Started with Hiera
Yup, we have some work to do on this. I recently joined the Puppet Labs documentation team, and getting Hiera better documented is high on my list of priorities. If you don't mind spending the time watching a video of a talk, I can recommend Kelsey Hightower's presentation at PuppetConf '12: http://www.youtube.com/watch?v=z9TK-gUNFHkfeature=youtu.be It provides a walkthrough example that might help you get your arms around Hiera a little better. I've converted the slide deck to a PDF, but it's a little large so please email me directly if you'd like me to forward a copy to you. There are also a few notes on the Hiera github repo, including a note on how to make sure your hierarchy and data files are correctly configured: https://github.com/puppetlabs/hiera/tree/master/docs/tutorials Hope this helps a little, and we'll have more formal documentation out soon. Regards, Michael On Thursday, November 15, 2012 10:20:35 AM UTC-8, Worker Bee wrote: Hi Everyone; Can anyone direct me towards documentation on getting started with Hiera? SPecifically, I ma looking for an easy way to verify post-install functionality. I did visit the following page which is is blank... http://docs.puppetlabs.com/hiera/1/puppet.html Any help would be greatly appreciated! -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/7-0c7JmZA-IJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppet-dashboard - rake API not working
Yes, I noticed it in 1.2.13 ( https://groups.google.com/d/msg/puppet-users/-s07XIymxCo/Yp3DpRU4t6EJ) but not in 1.2.14. Fixed it by running the mentioned 'rake gems:refresh_specs' Stefan On Monday, November 19, 2012 10:11:35 AM UTC+1, Jacob wrote: Hello all, I am quite new to the puppet arena, but I am really impressed with puppet as a tool and the possibilities it gives you with regards to managing many systems. I am running dashboard 1.2.14 and am trying to query via the rake API: http://docs.puppetlabs.com/dashboard/manual/1.2/rake_api.html when I do, I get the following error: snip # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 'node:list' (in /var/log) config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rack-1.1.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem json_pure-1.5.1 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are deprecated. Use lib/tasks instead. (called from /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10) /snip ...I fail to find any info on this online ... has anyone else seen this? Thanks, //Jacob. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/3I-0_vYZfBAJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Getting Started with Hiera
I'd like to second Michael's suggestion. Kelsey's various presentations involving Hiera and data bindings were all excellent, and really cleared things up for me. Jeffrey. On Mon, Nov 19, 2012 at 11:57 AM, Michael Hall michael.h...@puppetlabs.comwrote: Yup, we have some work to do on this. I recently joined the Puppet Labs documentation team, and getting Hiera better documented is high on my list of priorities. If you don't mind spending the time watching a video of a talk, I can recommend Kelsey Hightower's presentation at PuppetConf '12: http://www.youtube.com/watch?v=z9TK-gUNFHkfeature=youtu.be It provides a walkthrough example that might help you get your arms around Hiera a little better. I've converted the slide deck to a PDF, but it's a little large so please email me directly if you'd like me to forward a copy to you. There are also a few notes on the Hiera github repo, including a note on how to make sure your hierarchy and data files are correctly configured: https://github.com/puppetlabs/hiera/tree/master/docs/tutorials Hope this helps a little, and we'll have more formal documentation out soon. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet verion 2.7 or 3?
On Fri, Nov 16, 2012 at 7:13 AM, vioilly oliverle...@gmail.com wrote: That's a another reason for me to go toward 3.0.1. I assume it is a stable release? The long answer... It's an officially supported release, if that's what you mean. I can't say there aren't any bugs though. =) We're actively developing the 3 major version, so you'll see 3.0.2 released soon, with bug fixes, and 3.1.0 released shortly after with new, backwards-compatible functionality. The short answer: Yes, it's stable and any issues are likely valid ones that we'll fix as quickly as possible. -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Package Provider Continuously Re-installing Packages
Ah this works perfectly, thanks a lot. Reggie On Monday, November 19, 2012 12:50:38 PM UTC-5, Josh Cooper wrote: Hi Reggie, On Mon, Nov 19, 2012 at 7:57 AM, Reginald Choudari adnancho...@gmail.com javascript: wrote: We have specified in our manifests some Package resources to install some self-extracting .exe's onto our Windows Puppet machines. Currently we are seeing that our agents are running these installers every Puppet run. We have specified 'ensure = installed' but they are re-installing anyway. We made sure that the installer's are 'behaving-correctly' by checking the registry under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall and confirmed that our installers have the appropriate data in there. We cannot figure out where else to check. Thanks, Reggie -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/m2YS1iIUZIYJ. To post to this group, send email to puppet...@googlegroups.comjavascript:. To unsubscribe from this group, send email to puppet-users...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. Most likely, the package name in your manifest does not match the value of the DisplayName property in the registry, which is also the value displayed in Add/Remove Programs. A quick way to verify this is to install the package using puppet. Then run `puppet resource package name`, also with the name as displayed in Add/Remove Programs. You should see puppet report that the package is installed. [1] http://docs.puppetlabs.com/windows/writing.html#packagepackage -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/gYEHPbcIM4IJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Seeking some Puppet advice for a newbie (specifically Virtualmin/CSF related)
HI Forgive me if this is such a newbie issue. I am learning Puppet to manage several servers we have. The tutorials on manifests etc. seem a bit simplistic for I want, if what I want can be achieved with Puppet. Our servers are web hosting servers. We use Virtualmin (and Webmin) to manage the server and virtual servers. installing Virtualmin takes care of installing all the software required for virtual servers and websites, like Apache MySQL, PHP, BIND, Postfix etc. So we dont install those separately. Virtualmin does it. To setup a server we create the VPS, install Virtualmin, configure it, install CSF (Firewall), configure it and then our monitoring system agent. This is the minimum. We may want to then install something like Varnish perhaps, or anything else. At the moment I copy another server and delete its virtual servers as I have everything configured. But in time the configs just move away from each other. So I also want a way to manage all the configs on all servers, so they are the same. CSF in particular. I wondered if all this can be done in Puppet. I have no idea if it can because I cannot find any examples of this. I wondered if this is very possible with Puppet so I can continue to learn, OR if not then I will give up now as I already spent a while on this. Thanks -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/VH01FFHKx5MJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet verion 2.7 or 3?
Great to hear that Jeff. Confirmed, 3.0.1 it is. Is there a bug list I can track? On Mon, Nov 19, 2012 at 6:53 PM, Jeff McCune j...@puppetlabs.com wrote: On Fri, Nov 16, 2012 at 7:13 AM, vioilly oliverle...@gmail.com wrote: That's a another reason for me to go toward 3.0.1. I assume it is a stable release? The long answer... It's an officially supported release, if that's what you mean. I can't say there aren't any bugs though. =) We're actively developing the 3 major version, so you'll see 3.0.2 released soon, with bug fixes, and 3.1.0 released shortly after with new, backwards-compatible functionality. The short answer: Yes, it's stable and any issues are likely valid ones that we'll fix as quickly as possible. -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] puppet verion 2.7 or 3?
On Mon, Nov 19, 2012 at 3:38 PM, Oliver Leach oliverle...@gmail.com wrote: Great to hear that Jeff. Confirmed, 3.0.1 it is. Is there a bug list I can track? The best way I've found to track what issues we know about and what version we plan to fix them in is available at: https://projects.puppetlabs.com/projects/puppet/roadmap Hope this helps, -Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Question about PuppetDB queries
Hi, Thanks for letting us know about the log messages you are seeing! A few thoughts: 1) Re: the first query that you sent (DELETE FROM catalogs...): this is the PuppetDB garbage collector, which cleans up unused data from the tables every so often. It's not entirely shocking that this query might take over 10 seconds on occasion, so this one is probably nothing to be too worried about--though we will be keeping an eye out on our end of things, and if this is something that users are seeing in their logs frequently, we'll probably at least make some changes to improve the way we're logging it. 2) The logging on that second query is horrible, that's definitely a bug on our end. I've created a ticket for it here: http://projects.puppetlabs.com/issues/17732 3) Now, perhaps more importantly, we'd like to figure out why the queries are running slow for you in the first place. As I mentioned, it's not entirely shocking/concerning that that first query would end up taking longer than 10 seconds to run, but the second one is fairly surprising. Could you possible provide us with some specs about your environment? What kind of hardware are you running PuppetDB on? Which database backend are you using? How many nodes do you have in your population, and approximately how many resources per node? (A screenshot of your PuppetDB dashboard web page might be useful if you don't mind sharing one.) If you need a faster response, please feel free to jump on IRC (Freenode, #puppet), and just mention the word 'puppetdb'. Thanks again for letting us know! On Monday, November 19, 2012 2:53:51 AM UTC-8, ak0ska wrote: Hello, We get a good amount of warnings regarding queries that couldn't be executed within the threshold. There are 2 types of queries that usually get logged with this warning, I just wanted to ask if these queries look normal, because we cannot really judge, as we're fairly new to PuppetDB. Especially the second one looks weird, and it also makes our logfile grow fast. Example for type 1 : http://pastebin.com/exNG2bCj Example for type 2 (this is actually one single entry in the log) : http://pastebin.com/ym9AHPSk Thanks in advance! Cheers, ak0ska -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/HKiNpIzrvdAJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Seeking some Puppet advice for a newbie (specifically Virtualmin/CSF related)
On 11/19/2012 08:57 PM, Laurence Cope wrote: I wondered if this is very possible with Puppet so I can continue to learn, OR if not then I will give up now as I already spent a while on this. Yes, you can manage firewall and everything else with puppet. Just write your own modules or use existing ones and you'll be fine. Prepare to learn and to be slow in the beginning with deploying servers - like 2-3 times slower than installing all manually. But it will pay of in the end, you'll see. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Seeking some Puppet advice for a newbie (specifically Virtualmin/CSF related)
Whe I ask what is a package, I mean is a package installed using yum in a repo. And if so, is it any repo installed on the server, or the default ones or what? For packages not in the default repo but somewhere else I guess I add that repo using puppet first then install the package? I don't know if Virtualmin is available as a package hence asking about exec. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/hy1-H9hYU7wJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Seeking some Puppet advice for a newbie (specifically Virtualmin/CSF related)
Hi,
Yes, you probably want to do something like this:
class virtualmin::install {
$version = '1.2.3-foo'
exec { 'get installer script':
command = 'wget http://software.virtualmin.com/gpl/scripts/install.sh',
cwd = '/tmp',
creates = '/tmp/install.sh',
}
file { '/tmp/install.sh':
mode = 0755,
# checksum = 'the_checksum_of_that_script_if_you_feed_paranoid'
}
exec { 'install it now':
command = '/tmp/install.sh',
unless = 'test -x /usr/local/virtualmin/bin/foo
/usr/local/virtualmin/bin/foo --version | grep $version',
require = File['/tmp/install.sh'],
}
}
hope this kind of makes sense and please excuse any errors this pseudocode
might give you :)
Cheers,
--
Ilya
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet dashboard over passenger: The environment must be purely alphanumeric, not ''
Hi Andrew, sorry I wasn't clear -- The config.ru is probably fine, the
problem is more likely in the Apache configuration (usually in
/etc/httpd/conf.d/) that sets up the two virtual hosts (One for the
puppetmaster and the other for Dashboard). There might be an overlapping
virtualhost definition or the like. If you have trouble unwinding it,
please make a gist on github or pastie.com that shows these Apache config
files.
On Friday, November 16, 2012 10:04:38 AM UTC-8, Andrew Gooding wrote:
This is the config.ru file that I have inside the folder
/usr/share/puppet-dashboard :
# a config.ru, for use with every rack-compatible webserver.
# SSL needs to be handled outside this, though.
# if puppet is not in your RUBYLIB:
# $LOAD_PATH.unshift('/opt/puppet/lib')
$0 = master
# if you want debugging:
# ARGV --debug
ARGV --rack
# Rack applications typically don't start as root. Set --confdir to
prevent
# reading configuration from ~/.puppet/puppet.conf
ARGV --confdir /etc/puppet
# NOTE: it's unfortunate that we have to use the CommandLine class
# here to launch the app, but it contains some initialization logic
# (such as triggering the parsing of the config file) that is very
# important. We should do something less nasty here when we've
# gotten our API and settings initialization logic cleaned up.
#
# Also note that the $0 = master line up near the top here is
# the magic that allows the CommandLine class to know that it's
# supposed to be running master.
#
# --cprice 2012-05-22
require 'puppet/application/master'
# we're usually running inside a Rack::Builder.new {} block,
# therefore we need to call run *here*.
run Puppet::Application[:master].run
Where should I apply the changes?
On Thursday, October 18, 2012 10:37:54 AM UTC-7, Eric Sorenson wrote:
Hi andrew, that error is one that comes from the puppet master process
itself when you connect to it with a regular HTTP client. So it looks like
your apache virtualhost setup is pointing connections to that port/host at
the puppetmaster config.ru, not dashboard. Does that help track down
the issue?
-=Eric
On Tuesday, October 16, 2012 12:50:59 PM UTC-7, Andrew Gooding wrote:
Hello,
I installed puppet-server, passenger and dashboard. I have tested every
step in between to make sure all is running well and not errors are
carrying forward. Dashboard worked well with my test in WEBrick.
After configure the dashboard with passenger I got the message” The
environment must be purely alphanumeric, not ''” instead of the dashboard.
I verified the configuration files and all look to be in place, but I
should be missing something.
This is my current environment:
CentOS release 6.3 x86_64
puppet-2.7.19-1.el6.noarch
puppet-server-2.7.19-1.el6.noarch
puppet-dashboard-1.2.12-1.el6.noarch
*** LOCAL GEMS ***
activemodel (3.2.8)
activerecord (3.2.8)
activesupport (3.2.8)
arel (3.0.2)
builder (3.0.3)
daemon_controller (1.0.0)
fastthread (1.0.7)
i18n (0.6.1)
json (1.4.6)
multi_json (1.3.6)
passenger (3.0.17)
rack (1.4.1)
rake (0.9.2.2, 0.8.7)
tzinfo (0.3.33)
# rpm -qa | grep ruby
ruby-devel-1.8.7.352-7.el6_2.x86_64
ruby-mysql-2.8.2-1.el6.x86_64
ruby-libs-1.8.7.352-7.el6_2.x86_64
ruby-irb-1.8.7.352-7.el6_2.x86_64
rubygems-1.3.7-1.el6.noarch
ruby-shadow-1.4.1-13.el6.x86_64
libselinux-ruby-2.0.94-5.3.el6.x86_64
ruby-augeas-0.4.1-1.el6.x86_64
rubygem-json-1.4.6-1.el6.x86_64
rubygem-rake-0.8.7-2.1.el6.noarch
ruby-ri-1.8.7.352-7.el6_2.x86_64
ruby-1.8.7.352-7.el6_2.x86_64
ruby-rdoc-1.8.7.352-7.el6_2.x86_64
rpm -qa | grep mysql
ruby-mysql-2.8.2-1.el6.x86_64
mysql-5.1.61-4.el6.x86_64
mysql-devel-5.1.61-4.el6.x86_64
mysql-libs-5.1.61-4.el6.x86_64
mysql-server-5.1.61-4.el6.x86_64
Any help will be welcome.
Thanks,
Andrew
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/mNTjwoteit0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] inconsistencies with arrays: want multiple requires
I've poked around the puppet docs, and google, and so far I'm stuck on an
apparent inconsistency of usage, when it comes to using arrays, and
variables, interchangably.
I should mention this is with puppet 3.0.1
If you use literal arrays, both of the following are possible and accepted
by puppet:
package{ ['pkg1', 'pkg2']:
blahblah
}
service{ foo:
require = Package['pkg1', 'pkg2'],
}
However. If I define a variable,
$pkglist=['pkg1','pkg2']
Then, while I CAN do
package{ $pkglist:
blahblah
}
It seems I cannot do
service{ foo:
require = Package $pkglist ,
}
This makes me sad :(
Can someone tell if if there is some language shenanigans I must do, to get
puppet to accept the last bit?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/aycc1VNnuKoJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] hiera-puppet
As of the release of Puppet 3.0.0, hiera-puppet has been incorporated into the puppet codebase. See ticket #11608 for more details[1]. The standalone hiera-puppet package is only needed for releases of puppet prior to 3.0.0[2]. The 1.x branch of hiera-puppet is for those older versions of puppet, and is only open for urgent bug-fixes. If you want to file a ticket or submit a pull request for hiera-puppet functionality, please do so against the puppet redmine project or git repository, respectively. If the issue needs to be backported to hiera-puppet 1.x, we will take care of that on our end. The hiera-puppet README.md has been updated with additional information and links[3]. Josh [1] http://projects.puppetlabs.com/issues/11608 [2] http://docs.puppetlabs.com/hiera/1/installing.html#step-2-install-the-puppet-functions [3] https://github.com/puppetlabs/hiera-puppet/blob/master/README.md -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Issue with service = disabled and stopped
Thanks for the explanation, I appreciate it. These services are provided by Redhat as are the init scripts, which report: # /etc/init.d/cups-config-daemon status cups-config-daemon is obsolete # /etc/init.d/hidd status hidd is stopped I can see where the first one is unexpected to Puppet. I am running: # puppet --version 2.7.19 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Solaris processor count facts - bug or feature?
Hi all, This relates to a discussion we are having in the Redmine ticket https://projects.puppetlabs.com/issues/11612. I am extending the processorcount, physicalprocessorcount and processorX facts that exist for Linux and Solaris. I personally find the behaviour of the processor facts on Solaris surprising - myhost# facter |grep proc physicalprocessorcount = 1 processor0 = SPARC64-VII processor1 = SPARC64-VII processor2 = SPARC64-VII processor3 = SPARC64-VII processor4 = SPARC64-VII processor5 = SPARC64-VII processor6 = SPARC64-VII processor7 = SPARC64-VII processorcount = 4 We can see that physicalprocessorcount is returning the number of physical CPUs which is good, the processorX array is getting populated with virtual CPUs, and processorcount is returning the number of cores. The command used to set processorcount is essentially kstat cpu_info |grep core_id |sort -u. However, I suspect Solaris sysadmins are more familiar with using commands like psrinfo, prtdiag, and mpstat to get CPU count, and these all report the number of CPUs as 8 rather than 4. If I was writing this from scratch I would have a fact called something like ProcessorCoreCount and have that report 4 and then a separate fact ProcessorCount that would report 8 - as psrinfo is doing. Therefore I am interested to know if others out there regard this behaviour as a 'bug or feature', and also get some feedback on how people are using these facts out there. Thanks in advance. Best regards, Alex Harvey -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/WlRmUVNCey4J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: inconsistencies with arrays: want multiple requires
I think you misunderstand what puppet is doing there. Variables are not a
literal character replacement, they have types.
I think what you want is
require = Package[$pkglist]
The [] in your variable assignment tells puppet it is an array.
The [] in the Package example I provided tells puppet you are referring to
packages that have already been defined and not trying to change the
Package type's defaults.
On Monday, November 19, 2012 4:45:55 PM UTC-7, Philip Brown wrote:
I've poked around the puppet docs, and google, and so far I'm stuck on an
apparent inconsistency of usage, when it comes to using arrays, and
variables, interchangably.
I should mention this is with puppet 3.0.1
If you use literal arrays, both of the following are possible and accepted
by puppet:
package{ ['pkg1', 'pkg2']:
blahblah
}
service{ foo:
require = Package['pkg1', 'pkg2'],
}
However. If I define a variable,
$pkglist=['pkg1','pkg2']
Then, while I CAN do
package{ $pkglist:
blahblah
}
It seems I cannot do
service{ foo:
require = Package $pkglist ,
}
This makes me sad :(
Can someone tell if if there is some language shenanigans I must do, to
get puppet to accept the last bit?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/h8Kx08grxvcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: inconsistencies with arrays: want multiple requires
Huh. I could have SWORN I tried that syntax already.
First thing,even. But... it works. Thanks for the reply :)
On Monday, November 19, 2012 5:31:25 PM UTC-8, joe wrote:
I think you misunderstand what puppet is doing there. Variables are not a
literal character replacement, they have types.
I think what you want is
require = Package[$pkglist]
The [] in your variable assignment tells puppet it is an array.
The [] in the Package example I provided tells puppet you are referring to
packages that have already been defined and not trying to change the
Package type's defaults.
On Monday, November 19, 2012 4:45:55 PM UTC-7, Philip Brown wrote:
However. If I define a variable,
$pkglist=['pkg1','pkg2']
Then, while I CAN do
package{ $pkglist:
blahblah
}
It seems I cannot do
service{ foo:
require = Package $pkglist ,
}
This makes me sad :(
Can someone tell if if there is some language shenanigans I must do, to
get puppet to accept the last bit?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/OMHClG4DVOYJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Announce: Puppet 2.7.20 Available
Puppet 2.7.20 is a maintenance release for Puppet in the 2.7.x series with bug fixes and backwards-compatible performance improvements back-ported from the 3.0.x series. Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-2.7.20.tar.gz Windows package is available at https://downloads.puppetlabs.com/windows/puppet-2.7.20.msi RPMs are available at https://yum.puppetlabs.com/el or /fedora Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/puppet-2.7.20.dmg Gems are available via rubygems at https://rubygems.org/downloads/puppet-2.7.20.gem or by using `gem install puppet --version=2.7.20` See the Verifying Puppet Download section at: https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 2.7.20: http://projects.puppetlabs.com/projects/puppet/ To take a look at fixes targeted for this release, check out http://projects.puppetlabs.com/versions/307 ## Contributors ## Adrien Thebo, Andrew Parker, Ashley Penney, Branan Purvine-Riley, Dan Bode, Daniel Pittman, Dominic Cleal, Dustin J. Mitchell, Eric Sorenson, Eric Stonfer, Gleb Arshinov, James Turnbull, Jeff McCune, Jeff Weiss, Josh Cooper, Ken Barber, Ken Dreyer, Lee Lowder, Markus Roberts, Matthaus Owens, Michael Stahnke, Moses Mendoza, Neil Hemingway, Nick Fagerlund, Patrick Carlisle, Roman Barczyński, S. Zachariah Sprackett, Sean E. Millichamp, Stefan Schulte, Todd Zullinger ## Special notes about 2.7.20 ## Puppet 2.7.20 address http://projects.puppetlabs.com/issues/15560, which means if you had specifically enabled `managehome = true` for user resources expecting it not to work on Windows, be aware that it **works now** for both creation with `ensure = present` AND deletion with `ensure = absent`. Previously deleted users will not have their orphaned home directories removed, however. Puppet 2.7.20 also addresses concerns regarding a change introduced in Puppet 2.7.16, b26699a (#10146) `-` is not legal in variable names., which disallowed the use of dashes in variable names. Puppet 2.7.20 introduces a configuration option, `allow_variables_with_dashes`, (http://docs.puppetlabs.com/references/2.7.latest/configuration.html#allowvariableswithdashes) which can be set to `true` to restore earlier behavior, although this is strongly discouraged. The option is set to false by default to maintain current behavior. (#10146) `-` in variable names should be deprecated! In commit b26699a2 I fixed an accidentally introduced change to the lexer, allowing `-` to be part of a variable name. That had lasted for a while and was surprisingly popular. It was also hugely ambiguous around `-` as minus, and led to all sorts of failures - unexpected interpolations to nothing - because of that. A much better strategy would have been to deprecate the feature, issue proper warnings, and include an option to allow users to toggle the behaviour. Initially defaulting that to permit, and eventually toggling over to deny, would have made the whole experience much smoother - even if this was totally documented as not working, and was a clear bug that it changed. So, thanks to prompting from Benjamin Irizarry, we do just that: introduce the configuration option, default it to deny to match current behaviour, but allow users the choice to change this back. Please be aware that allowing variables with `-` might break all sorts of things around, for example, Forge modules though. Most people write code to the documented standard, and their code might well totally fail to work with this changed away from the default! Signed-off-by: Daniel Pittman dan...@puppetlabs.com ## Puppet 2.7.20 Changelog ## Adrien Thebo (1): 367926a (#15264) Custom title patterns can fail cryptically. Andrew Parker (15): 65b35a8 (Maint) Simplify CONTRIBUTING.md 9e26fe0 (#10915) Fix tests to work with new parameter checking d2e5268 (#10915) Add test for provider throwing NoMethodError b48a172 (Maint) Fix syntax and semantic erros in test 5e3fbca (Maint) Remove fragile test dc50ec7 (#16922) Quote strings that contain : 13ab956 (#16791) Revert Merge branch 'perf/2.7.x/backport-activesupport-hook-disabling' of https://github.com/daniel-pittman/puppet into 2.7.x 1e5baee (#16791) Revert Maint: Fix intermittently failing spec test 3cda4f4 (#16791) Revert Merge branch 'feature/2.7.x/json-terminus-backport' of https://github.com/daniel-pittman/puppet into 2.7.x aba3c67 (#16791) Re-instate deprecated symbolize and symbolizehash! d892859 (#16791) Remove tests for unused behavior bd0caf5 (#17260) Warn when variables contain hyphens 5c61f32 (#17260) Include link to information about deprecation b5ed15b (#17458) Load
Re: [Puppet Users] Re: Issue with service = disabled and stopped
Both of these init scripts always return 0. Puppet assumes that the init script will return 0 as a status for a running service and nonzero for a stopped service. Because of this, when Puppet calls `service hidd status` to see if hidd needs to be stopped, it thinks it does, as status returns 0. hidd ships with a deficient init script. It makes the right calls to start, stop, and get the status of the hidd service, but it never does anything with the returns from those calls so it always falls through to the bottom of the script where 0 is returned. On Mon, Nov 19, 2012 at 4:37 PM, Forrie for...@gmail.com wrote: Thanks for the explanation, I appreciate it. These services are provided by Redhat as are the init scripts, which report: # /etc/init.d/cups-config-daemon status cups-config-daemon is obsolete # /etc/init.d/hidd status hidd is stopped I can see where the first one is unexpected to Puppet. I am running: # puppet --version 2.7.19 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Matthaus Owens Release Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: puppet-dashboard - rake API not working
Thanks :) Now I get snip # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 'node:list' (in /usr/share/puppet-dashboard) DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are deprecated. Use lib/tasks instead. (called from /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10) /snip Il giorno lunedì 19 novembre 2012 19:37:43 UTC+1, Stefan Heijmans ha scritto: Yes, I noticed it in 1.2.13 ( https://groups.google.com/d/msg/puppet-users/-s07XIymxCo/Yp3DpRU4t6EJ) but not in 1.2.14. Fixed it by running the mentioned 'rake gems:refresh_specs' Stefan On Monday, November 19, 2012 10:11:35 AM UTC+1, Jacob wrote: Hello all, I am quite new to the puppet arena, but I am really impressed with puppet as a tool and the possibilities it gives you with regards to managing many systems. I am running dashboard 1.2.14 and am trying to query via the rake API: http://docs.puppetlabs.com/dashboard/manual/1.2/rake_api.html when I do, I get the following error: snip # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 'node:list' (in /var/log) config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rack-1.1.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem json_pure-1.5.1 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are deprecated. Use lib/tasks instead. (called from /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10) /snip ...I fail to find any info on this online ... has anyone else seen this? Thanks, //Jacob. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Q-XcVfScapMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
