That should be fine as long as you're only running on Ruby 1.9. A fix for
this issue went into our 2.7.x branch yesterday [
https://github.com/puppetlabs/puppet/commit/933844567fbe4078cb76f2c089ced1cb6c4170b7].
I'd love to hear if that solves your problems, although I think on 1.9.2
it's functional
This is a bug in the error message (
http://projects.puppetlabs.com/issues/13299). The correct command is
'puppet agent --enable'.
--
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
It looks like an incompatibility between puppet-lint and ruby 1.9, which
removed the String#each method that was in earlier versions.
On Wed, Apr 18, 2012 at 11:30 PM, Joseph wrote:
> Hi, this is not strictly puppet related but I am hoping someone here
> who uses puppet-lint can tell me what is
On Fri, Sep 28, 2012 at 2:29 PM, Forrie wrote:
> I'm not at PuppetConf, unfortunately. In this case, all I did was a
> simple CentOS "service puppetmaster restart" as I have in the past.
>
> But, I wonder if the fact there are older versions still present might
> contribute to this -- though it
To diagnose this you'll want to get a full stack trace. Since the error is
on the master you run the master with --trace and then find the stack trace
in the log.
On Tue, Jun 18, 2013 at 11:08 AM, Greg Chavez wrote:
> I upgrade our infrastructure (mostly RHEL5, some RHEL6) from 3.1 to
> puppet-
> Is it possible to tell facter to ignore certain facts? Couldn't find a
> config file for it and not sure how puppet tells it to gather facts.
>
>
There's no configuration right now. I think you have a pretty reasonable
case, and you should file a feature request at
http://projects.puppetlabs.com
On Tue, Sep 17, 2013 at 1:14 AM, Andrei-Florian Staicu <
andrei.sta...@gmail.com> wrote:
> Any idea if this is a recognized bug?
I don't think it is. Please file a bug report at
projects.puppetlabs.comand we can investigate this further.
--
You received this message because you are subscribed
Do either of you happen to have multiple versions of the puppet installed
on the master? One through rubygems and one through yum? I've only been
able to reproduce this so far when I accidentally ran a 3.3.0 master that
loaded some code from 3.2.4.
If not, can you run the master with --trace and -
