> > What's the 2.2 error? > Also FYI we're doing zero testing with ruby 2.2 at this time.
Hi Kaylo, The error that I'm getting is this one: err: Failed to apply catalog: Invalid parameter allow_virtual at /etc/puppet/environments/production/modules/puppet/manifests/install.pp:5 And zero testing with ruby 2.2? Well that's the version that comes with the latest version of Mac OS X (Mavericks) and Amazon AWS Linux.. Not sure what other flavors of Unix come with this by default. But based on that alone maybe it's time? Maybe look into what other new distros are on 2.2? I know you guys are busy, but as we all know, you can't stop the wheels of time from grinding forward! ;) Thanks Tim On Tue, Oct 7, 2014 at 12:14 PM, Kylo Ginsberg <[email protected]> wrote: > On Tue, Oct 7, 2014 at 7:26 AM, Tim Dunphy <[email protected]> wrote: > >> Hey guys, >> >> I kept getting this annoying warning in the output of my puppet runs: >> >> >> Warning: The package type's allow_virtual parameter will be changing its >> default value from false to true in a future release. If you do not want >> to >> allow virtual packages, please explicitly set allow_virtual to false. >> (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default') >> >> >> So I found this article: >> >> https://inuits.eu/blog/puppet-361-depreciation-warning >> >> That suggesting putting this value in your site.pp for your environment: >> >> Package { >> allow_virtual => true, >> } >> >> Which DOES suppress that annoying output on the majority of the hosts. >> But a few of them have ruby 2.2 installed on some of the newer OSs. >> >> And all the hosts with the newer ruby throw the following error instead >> of performing clean puppet runs like the hosts with the older rubies (1.8.7 >> and 1.9.3). >> > > What's the 2.2 error? > > Also FYI we're doing zero testing with ruby 2.2 at this time. > > Kylo > > >> >> And I notice that I can't get puppet to work on the ruby 2.2 hosts even >> after deleting that allow_virtual override from my site.pp. >> >> So how do I fix the nodes with the newer ruby? Is there any value I can >> set that will make that annoying error message go away, yet allow the >> puppet server to play nicely with all the nodes? >> >> -- > Kylo Ginsberg | [email protected] | irc: kylo | twitter: @kylog > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CALsUZFFHoWCm_pTVu%2BzxXKD9F_boSpFQgVJDsqt7weZaP%3D273A%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CALsUZFFHoWCm_pTVu%2BzxXKD9F_boSpFQgVJDsqt7weZaP%3D273A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAOZy0ekFX5vHStdxWNjkCGV3wdpaYiLJ375F%2BT3tQ7bF-K0wcQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
