Re: [Puppet Users] Re: How do I set global noop?
Thanks Justin,
Yes MCollective would be great, just have to find the time.
Rene: I have gone with your solution at the moment. I still think it's a
bug that doing it on the Resource resource doesn't work, hopefully someone
will look into those bugs.
Cheers,
Sam
On Sunday, 28 July 2013 02:11:25 UTC+10, Justin Brown wrote:
Sam,
You should setup MCollective. You can implement a simple plugin that
changes the global noop setting in puppet.conf and restarts the
daemon.
That will give you the best scalability, and you have fine-grained
control in MCollective on which hosts run using metadata in your
Puppet classes and facts.
Regards,
Justin
On Sat, Jul 27, 2013 at 10:52 AM, rvlinden
rene.vand...@gmail.com javascript: wrote:
Sam,
You could make some changes to you site.pp and set some defaults like
this
Exec {
schedule = $::globalvars_schedule,
noop = $::globalvars_noop,
}
File {
schedule = $::globalvars_schedule,
noop = $::globalvars_noop,
}
Group {
schedule = $::globalvars_schedule,
noop = $::globalvars_noop,
}
Mount {
schedule = $::globalvars_schedule,
noop = $::globalvars_noop,
}
Package {
schedule = $::globalvars_schedule,
noop = $::globalvars_noop,
}
Service {
schedule = $::globalvars_schedule,
noop = $::globalvars_noop,
}
User {
schedule = $::globalvars_schedule,
noop = $::globalvars_noop,
}
. and more .
Make sure that all puppet types you use within you modules are covered
in
the site.pp and have the noop = $::globalvars_noop added.
The final step is to set the topscope variable 'globalvars_noop'
somewhere
(for example hiera, or Puppet console) and your node will be run with
noop.
No need to touch any puppet config on the clients, and very easy to
manage
:-)
Regards,
Rene vd Linden
Blog: https://www.rvanderlinden.net/wordpress
On Tuesday, July 23, 2013 1:29:24 AM UTC+2, Sam Morrison wrote:
I'm trying to set a global noop but it doesn't seem possible,
There are 2 bugs open about this which to me look pretty serious as the
expected behaviour isn't the case.
http://projects.puppetlabs.com/issues/21286
http://projects.puppetlabs.com/issues/6549
If anyone has a work around (that doesn't include modifying puppet.conf
file) I would be very interested.
Cheers,
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...@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.
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.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: How do I set global noop?
Yeah but then when we push out noop = true in puppet.conf how do we then push out noop = false via puppet if they're all in noop. Managing on the server is the only way to do it in a safe and scalable way (we have 500+ nodes) On Thu, Jul 25, 2013 at 10:18 PM, Klavs Klavsen kl...@enableit.dk wrote: well - perhaps you can put noop = true or something in puppet.conf on the clients ? -- You received this message because you are subscribed to a topic in the Google Groups Puppet Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/HzjRMtQlHRU/unsubscribe. To unsubscribe from this group and all its topics, 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. 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. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: How do I set global noop?
On Wednesday, 24 July 2013 03:12:10 UTC+10, Ellison Marks wrote: How are you running puppet? If cron or mcollective, you can add a --noop flag to the command line somewhere. We're just using it the standard way running it as a daemon -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] How do I set global noop?
I'm trying to set a global noop but it doesn't seem possible, There are 2 bugs open about this which to me look pretty serious as the expected behaviour isn't the case. http://projects.puppetlabs.com/issues/21286 http://projects.puppetlabs.com/issues/6549 If anyone has a work around (that doesn't include modifying puppet.conf file) I would be very interested. Cheers, 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. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: apt-get update before installing a package. The right way?
On Saturday, 23 March 2013 00:50:11 UTC+11, jcbollinger wrote:
On Thursday, March 21, 2013 6:16:07 PM UTC-5, Sam Morrison wrote:
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.
That is indeed a gotcha with using resource defaults, but its not usually
a (necessary) problem for packages. You could consider looking at which
packages are declaring their own 'require's, and why. They probably don't
need to do, except as a means to achieve more or less the same thing you're
after.
In a pinch, you can always wrap package declarations in definitions so
that the defined type carries the explicit 'require' and the package just
inherits the default require, but really, I'm having trouble seeing why it
would be necessary.
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.
I'm not big on stages, in large part because they significantly magnify
the risk of cycles, but more fundamentally because they inherently place
many more constraints on resource application order than are needed. There
is nothing you can do with stages that you cannot also do with ordinary
resource relationships, though using ordinary relationships may be a lot
more work for the manifest author.
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.
If there were a suitable a selection predicate you could use in your
collector then that might help you out. For example:
Exec['apt_update'] - Package | tag == 'classes_I_care_about' |
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.
I guess you're saying that you want to make everything work without
modifying any third-party modules. That might not be possible, especially
if (as I suppose) it is a requirement that the solution be flexible and
robust. Your experience with run stages may, in fact, be telling you that
there is *no* resource-application order consistent with all your
declarations that applies all apt sources and keys before all packages.
One simple way that could be true would be if any apt sources or keys were
themselves installed via packages.
I actually like the resource defaults approach, but you need to audit your
manifests, including third-party modules, to ensure that Package
declarations do not provide their own 'require's. You can allow Packages
to do so only to the extent that they are supplying their own means to your
end, including if they need to override your general rule. That's the only
reason they should need to 'require' anyway.
For the longer term, you could consider filing a feature request that
would help you out. For example, a collector selection criterion or
alternative collector syntax that collects concrete resources but does not
realize virtual ones. Actually, I think there may already be at least one
ticket that bears on that (separating resource collection from realization).
John
Thank for the info John and Brian,
Separating resource collection from realization would be great. I found
http://projects.puppetlabs.com/issues/7240 so hopefully that can be
implemented somehow.
I've ended up going with stages for now. I had to modify the handful of
modules that declare apt sources and keys and put these resources into
their own class within the module. Then I added these class to a stage that
runs before main,
I think stages can work as long as you keep it simple.
Cheers,
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.
[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.
[Puppet Users] Restricting hosts to a certain environment
Hi, I'm wanting to restrict hosts to a certain environment. Eg only hosts in the range 192.168.0.0/24 can use the production environment Similar with test env etc. Is this possible with auth.conf? Thanks, Sam -- 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/-/E2HMQ3fE568J. 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: Installing puppet-dashboard on ubuntu precise
Hi Daniele, Yeah you are probably right. I can't uninstall the other one as it is a dependance on mod-passenger. I'm not really familiar with ruby, Is there a way I can override the search path? I don't have RUBYLIBDIR set in my environment. Cheers, Sam On Friday, 17 August 2012 17:41:49 UTC+10, Daniele Sluijters wrote: Hi, Are you sure there's no rack 1.3.5 somewhere around your system? If there is it is probably found in the $RUBYLIBDIR path before the one installed from gem so you're still seeing the error. If not, then it's getting interesting... -- Daniele Sluijters On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote: Hi, I'm trying to install dashboard on precise and I get the below error. I'm using the latest version that is available in the puppet apt repository. The package rdoc is installed (it's just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn't specify? I don't know ruby that well so finding it hard to debug. Also it's well after 2011-11-01 is that a problem too? Thanks, Sam root@admin:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate --trace NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems
Re: [Puppet Users] Re: Installing puppet-dashboard on ubuntu precise
I'd rather not do that as mod-passenger is needed by something else (puppetmaster) Is there no way I can make dashboard use the gem version as opposed to the standard one? Is that what RUBYLIBDIR is for? Cheers, Sam On Monday, 20 August 2012 11:43:11 UTC+10, Ashish Jaiswal wrote: Hi Sam, I would rather suggest uninstalling mod-passenger and then do a fresh install, rather going into all this mess.. Regards, System Admin Ashish Jaiswal On Monday 20 August 2012 07:03:54 AM IST, Sam Morrison wrote: Hi Daniele, Yeah you are probably right. I can't uninstall the other one as it is a dependance on mod-passenger. I'm not really familiar with ruby, Is there a way I can override the search path? I don't have RUBYLIBDIR set in my environment. Cheers, Sam On Friday, 17 August 2012 17:41:49 UTC+10, Daniele Sluijters wrote: Hi, Are you sure there's no rack 1.3.5 somewhere around your system? If there is it is probably found in the $RUBYLIBDIR path before the one installed from gem so you're still seeing the error. If not, then it's getting interesting... -- Daniele Sluijters On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote: Hi, I'm trying to install dashboard on precise and I get the below error. I'm using the latest version that is available in the puppet apt repository. The package rdoc is installed (it's just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn't specify? I don't know ruby that well so finding it hard to debug. Also it's well after 2011-11-01 is that a problem too? Thanks, Sam root@admin:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate --trace NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec
Re: [Puppet Users] Installing puppet-dashboard on ubuntu precise
Thanks Ashish, I was hoping to not have to install any gems, it comes as a debian package so I was expecting that it would work with the packages available. Precise comes with rack 1.3.5 so wondering if I can get it to work with that somehow. How comes it says rdoc though? Is there any way to find out the real requirements for puppet-dashboard? Is there some kind of checking I can disable? I would be nice if these specific dependencies were put in the debian package as I always find it a struggle to install anything that involves ruby. The puppet and puppetmaster packages work great so it would be good to get the puppet-dashboard package up to the same standard. Has anyone got this working without installing gems? Any debs for the required versions around? Cheers, Sam On Wednesday, 15 August 2012 16:45:20 UTC+10, Ashish Jaiswal wrote: Hi, I just ran into the same problem few days back, see whether you have installed rack 1.1.0 you can check by gem list and if possible uninstall the existing rack which ever version it is and then install it with this command gem install rack -v=1.1.0 snip server:/usr/share/puppet-dashboard/script# gem list *** LOCAL GEMS *** daemon_controller (1.0.0) fastthread (1.0.7) passenger (3.0.15) rack (1.1.2, 1.1.0) rake (0.9.2.2) /snip Regards, System Admin Ashish Jaiswal On Wednesday 15 August 2012 10:47:38 AM IST, Sam Morrison wrote: Hi, I'm trying to install dashboard on precise and I get the below error. I'm using the latest version that is available in the puppet apt repository. The package rdoc is installed (it's just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn't specify? I don't know ruby that well so finding it hard to debug. Also it's well after 2011-11-01 is that a problem too? Thanks, Sam root@admin:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate --trace NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8
[Puppet Users] Re: Installing puppet-dashboard on ubuntu precise
Hi Daniele, Thanks a lot for the info, I'll follow the bug and give your workaround a go. Cheers, Sam On Thursday, 16 August 2012 23:09:20 UTC+10, Daniele Sluijters wrote: Hi, The issue is probably that the Puppet package is requiring librack-ruby. In the case of Debian Squeeze this neatly resolves to 1.1.0 and there are no issues. Dashboard should be fixed to work with more recent versions of Rack though as Wheezy ships with 1.4.1 so the issue will be more prominent. What you can try for now is to uninstall the Ubuntu package and grab the Debian librack-ruby and install that through dpkg. It's probably going to want to upgrade librack-ruby the next time you run apt-get upgrade so you might have to hold the package if you go down this road. The issues are caused by endor/rails/railties/lib/rails/gem_depedency.rb and vendor_gem_source_index.rb that use deprecated functions. The fix should be fairly simple but someone actually has to get up and do it. The issue is being tracked in http://projects.puppetlabs.com/issues/9296so I suggest you update that ticket. -- Daniele Sluijters On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote: Hi, I'm trying to install dashboard on precise and I get the below error. I'm using the latest version that is available in the puppet apt repository. The package rdoc is installed (it's just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn't specify? I don't know ruby that well so finding it hard to debug. Also it's well after 2011-11-01 is that a problem too? Thanks, Sam root@admin:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate --trace NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01
[Puppet Users] Re: Installing puppet-dashboard on ubuntu precise
OK so I tried the debian package way but that got too hard with package conflicts. There is librack-ruby which seems to be the same as ruby-rack but not sure, ruby-rack depends on passenger so I don't want to go down that path. So next step was to try via installing the gem, I did: gem install rack -v=1.1.0 But I still get exactly the same error: root@admin:/usr/share/puppet-dashboard# gem list *** LOCAL GEMS *** rack (1.1.0) Something else I'm missing? Thanks, Sam On Friday, 17 August 2012 09:58:06 UTC+10, Sam Morrison wrote: Hi Daniele, Thanks a lot for the info, I'll follow the bug and give your workaround a go. Cheers, Sam On Thursday, 16 August 2012 23:09:20 UTC+10, Daniele Sluijters wrote: Hi, The issue is probably that the Puppet package is requiring librack-ruby. In the case of Debian Squeeze this neatly resolves to 1.1.0 and there are no issues. Dashboard should be fixed to work with more recent versions of Rack though as Wheezy ships with 1.4.1 so the issue will be more prominent. What you can try for now is to uninstall the Ubuntu package and grab the Debian librack-ruby and install that through dpkg. It's probably going to want to upgrade librack-ruby the next time you run apt-get upgrade so you might have to hold the package if you go down this road. The issues are caused by endor/rails/railties/lib/rails/gem_depedency.rb and vendor_gem_source_index.rb that use deprecated functions. The fix should be fairly simple but someone actually has to get up and do it. The issue is being tracked in http://projects.puppetlabs.com/issues/9296so I suggest you update that ticket. -- Daniele Sluijters On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote: Hi, I'm trying to install dashboard on precise and I get the below error. I'm using the latest version that is available in the puppet apt repository. The package rdoc is installed (it's just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn't specify? I don't know ruby that well so finding it hard to debug. Also it's well after 2011-11-01 is that a problem too? Thanks, Sam root@admin:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate --trace NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE
[Puppet Users] Installing puppet-dashboard on ubuntu precise
Hi, I'm trying to install dashboard on precise and I get the below error. I'm using the latest version that is available in the puppet apt repository. The package rdoc is installed (it's just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn't specify? I don't know ruby that well so finding it hard to debug. Also it's well after 2011-11-01 is that a problem too? Thanks, Sam root@admin:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate --trace NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. rake aborted! no such file to load -- rdoc/task
[Puppet Users] Could not evaluate: Field 'key' is required when exporting ssh_authorized_keys
I seem to have a weird error when trying to collect ssh keys and installing
them on our backup server.
On all hosts I have:
@@ssh_authorized_key { root@$fqdn:
type = ssh-rsa,
key = $rootsshkey,
tag = 'host',
user = backups,
}
Then on my backup server I have:
Ssh_authorized_key | tag == 'host' |
When running puppet on the backup server I get a whole lot of:
notice: /Stage[main]/Backup/Ssh_authorized_key[r...@example.org]/ensure:
created
err: /Stage[main]/Backup/Ssh_authorized_key[r...@example.org]: Could not
evaluate: Field 'key' is required
Upon subsequent puppet runs it will work eventually until all the keys are
installed. It seems to work for 1-7 keys at a time then fail for the rest.
The amount of broken ones gets smaller and smaller each time.
Any clues?
Cheers,
Sam
--
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/-/zTztpiZmBzcJ.
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] Multiple template fallbacks
Hi,
In a file resource I want to be able to specify multiple template contents.
If the 1st template doesn't exist use the 2nd listed and so on. Much like
how the source attribute works.
Basically this:
file { /tmp/somefile.txt:
ensure = present,
content = [
template(somefile-$fqdn.erb),
template(somefile.erb),
]
mode= 644,
owner = root,
group = root,
}
Which doesn't work. Is there a way to do this in puppet?
Thanks,
Sam
--
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/-/mVbZoOdhVp8J.
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] Multiple template fallbacks
Thanks Wolf, This works perfectly. Cheers, Sam -- 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/-/oayiKvapyZUJ. 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.
