Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title
Gary Steven commented on an issue
Re: 3.6.1 issues warning message for deprecation
While that might help it introduces the larger problem of blocking ALL deprecation messages which I do not want to do. How would I be aware of future changes or problems if I turn off all deprecation messages. The real issue is agent vs apply behave differently.
in site.pp if I specify Package { allow_virtual = false }
I do not see the message anymore using 'puppet agent --test' but always see it using 'puppet apply /etc/puppet.manifests/site.pp'.
One would expect these to behave the same and return the same results which they do not today.
Add Comment
Puppet / PUP-2650
3.6.1 issues warning message for deprecation
Message is issued from agent runs at the warning level for a deprecation message. 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...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2974) Cannot turn off allow_virtual warning in puppet apply
Title: Message Title Gary Steven commented on an issue Re: Cannot turn off allow_virtual warning in puppet apply I think I found the root cause of the deprecation warning appearing in my situation. I have a Puppet module which can be found at https://github.com/stankevich/puppet-python It appears there is a custom fact to hold the version of python installed. The custom fact is determined using the snippet below. If I had to guess this is caused by Facter running prior to Puppet to collect and expose all the facts to Puppet and the Package setting I have in site.pp is not being inherited at this point. pkg = Puppet::Type.type(:package).new(:name = python) While this is not a common way to collect the information for a custom fact and I should open up the issue with the module author now, it does seem odd that this can occur and maybe is part of a larger problem. Thank you for your assistance in helping to pin point the culprit. Add Comment Puppet / PUP-2974 Cannot turn off allow_virtual warning in puppet apply According to comments on PUP-2650, the suggested fix for the allow_virtual warning doesn't work when puppet apply is used.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title
Gary Steven commented on an issue
Re: 3.6.1 issues warning message for deprecation
The 'fix' of adding Package { allow_virtual = false }
in /etc/puppet/manifests/site.pp does not appear to work in master-less (puppet apply) mode and I always get the warning message. Is there a work around for this scenario?
Add Comment
Puppet / PUP-2650
3.6.1 issues warning message for deprecation
Message is issued from agent runs at the warning level for a deprecation message. 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...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this
