annoying "allow_virtual parameter" warning

[Tim Dunphy]

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).

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?

Thanks

Tim

Please help! 

Is there any universal solution for this problem?

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

[Kylo Ginsberg]

On Tue, Oct 7, 2014 at 7:26 AM, Tim Dunphy <bluet...@gmail.com> 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 | ky...@puppetlabs.com | irc: kylo | twitter: @kylog

[Tim Dunphy]

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 

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CALsUZFFHoWCm_pTVu%2BzxXKD9F_boSpFQgVJDsqt7weZaP%3D273A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Kylo Ginsberg]

On Tue, Oct 7, 2014 at 12:31 PM, Tim Dunphy <bluet...@gmail.com> wrote:

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)

Hmm, my OS X 10.9.5 reports:

ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin13]

While I believe ruby 2.2 is still in preview:

https://www.ruby-lang.org/en/news/2014/09/18/ruby-2-2-0-preview1-released/

Kylo

 

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.

--

[Tim Dunphy]

Hmm, my OS X 10.9.5 reports:
ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin13]
While I believe ruby 2.2 is still in preview:
https://www.ruby-lang.org/en/news/2014/09/18/ruby-2-2-0-preview1-released/
Kylo

Yeah it's interesting that Mac OS X includes a preview version of ruby. I was also surprised to find it on my Amazon AWS Linux instances in EC2. I wonder if there are any more linux distros out there using it? I haven't really checked into it. 

But I found that I pretty much have to live with that annoying allow_virtual parameter warning. To fix the Amazon Linux nodes I had to do the whole remove cert then re-add routing. After taking out the 

Package {
  allow_virtual => true, 

}

Setting from site.pp for my production environment. Better to have the warning than to break puppet. :)

Thanks

Tim 

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CALsUZFEJjZP2_3XqgLUbrgC7KgZdi8e2TFZ2mkV%3Dx%2BVkZ%3DZnqw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Spencer Krum]

Hi Tim,

Some people are working around the first issue by doing a:

if verscmp($::puppetversion, 3.6.0) {

   Package { allow_virtual => true,
}

You could do that, and possibly a comparison to the rubyversion fact as well.

Thanks,
Spencer

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAOZy0emniTshPmaGBopXKtAgMfhi7j_Z9%2BYXwBejbn2J3-cv%2BA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
Spencer Krum
(619)-980-7820

[Tim Dunphy]

Hi Spencer

Some people are working around the first issue by doing a:
if verscmp($::puppetversion, 3.6.0) {
   Package { allow_virtual => true,
}

You could do that, and possibly a comparison to the rubyversion fact as well.

Thats' FANTASTIC!!! I put that in my production environment's site.pp. And now all my puppet nodes are working without that annoying warning message! Thank you for that!

Also would someone mind weighing in on my puppetboard thread? LOL I'm dying to solve that one as well. 

Thank you ALL!!

Tim 

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CADt6FWM7tCzamus4sJP8JNacsJui2WSt_1ujx%2BOZnnrzif_THA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Spencer Krum]

What puppetboard thread?

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAOZy0emfcaQP4bYperzRV0iA4kEiGk9Rqk2iJXOy3J4j%2BjeGOg%40mail.gmail.com.

[Tim Dunphy]

Hi Spencer, 

 Oh I called it "puppetboard unable to reach puppetb" and sent it to the puppet users group. Any help there would be fantastic!

Thanks!

Tim

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CADt6FWM9Vnq3i2YQ7Q_56vxXKC3L_o14NhWfsd0UuqQ0By-Gxw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.