Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Ben Ford commented on an issue Re: 3.6.1 issues warning message for deprecation This also raises its nasty little head when running puppet resource. 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kurt Wall commented on an issue Re: 3.6.1 issues warning message for deprecation Gary Steven Setting disable_warnings=deprecations in puppet.conf or using puppet apply --disable_warnings deprecations ... might help. 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
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-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Andy Parker commented on an issue Re: 3.6.1 issues warning message for deprecation Gary Steven, I've opened PUP-2974. If you could provide a reproduction case in that ticket I'll make sure that it gets looked at. 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
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
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Rob Reynolds commented on an issue Re: 3.6.1 issues warning message for deprecation Jo Rhett Closing this issue doesn't mean that we are not in agreement with your thoughts, it simply means this ticket and work was completed and released. Let's file a new ticket once one of us has a better idea of how we should approach the issue. You jumped on board just a bit late to get anything changed prior to the 3.6.2 release, but that doesn't mean we can't find a better fix as we move towards the next release. 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
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Rob Reynolds commented on an issue Re: 3.6.1 issues warning message for deprecation Let's make sure we reference a link to the new ticket in this ticket so we don't lose focus on the conversation that we've had over here. 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Adrien Thebo commented on an issue Re: 3.6.1 issues warning message for deprecation Jo Rhett could you lay out some solutions for this problem that would work for your environment? Would finer grained disable_warnings help? Alternately, would it help if the log level for deprecation warnings could be tuned so deprecation warnings would be logged at `info` or `debug` instead of `warn`? Is the problem the fact that we're emitting a log message, or is the problem mainly due to these warnings showing up in the reports? On other words, how can we surface these issues in a manner that's user friendly and non-obtrusive, but still visible? 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
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Jo Rhett commented on an issue Re: 3.6.1 issues warning message for deprecation I am sorry for saying that I don't have a great solution off the top of my head. I just strongly feel that the current implementation isn't it My brain is elsewhere right now while I finish off the LM book, but I'll give it some thought this weekend. My current thinking: 1. Providing a warning in the server logs would be more useful in my mind than on the node. Most sites I know watch for errors on the server log and don't read the client log. So I'm not certain you are reaching who you think. 2. The few sites which do monitor the agent logs had their Splunk (or whatever) monitoring alarms go nuclear, at which point they found that it was a message they should see in RELEASE_NOTES instead which produced a large amount of annoyance. This caused high-priority tickets to get created to ensure that no other deprecation message ever causes this again – which means your channel of communication got silenced. As for what we can do in a positive manner: 1. Improve the process by which RELEASE_NOTES are updated. Far too many changes creep into releases with a mild remark that should have pointed to a clear description of the impact. This is why people are cautious to upgrade. If you want release notes to be read, you've got to make sure they are accurate. 2. Most people I know would like to have an easy way to say puppet apply --tell-me-what-sucks and receive the output. I'd put this in cron even a. I think this would require testing every role and profile independently Any option to scan the entire library and find all depreciations would be nice. 3. I've actually been trying to find time to build a net-snmp agent to query a running puppetmaster and provide a SNMP table available of current alarms per environment. This kind of table works very well with existing monitoring solutions, and avoids the 7k-lb hammer landing when a single warning appears. It doesn't need to be exactly this ^^^ but I'd like to encourage you to think in this manner. [warning]*[nodes] is never an appropriate way to communicate an issue. It's only informative for the smallest of sites. For anything bigger than my personal testlab it's overwhelming delivery far beyond it's informative value and will be disabled. A big issue of critical or emergency level – certainly. Any time a NOC spins on its tail and escalates a major monitoring failure and it turns out to be non-essential communication – that method of communication will be crippled. Messages of a non-essential nature should be made available on a periodic basis. Rate limit the message. Provide it within a singular structure containing a number-of-incidents, etc. It's not an easy problem to solve, especially given the one-by-one nature of Puppet. I'll keep thinking about it. Add Comment
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Andy Parker updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Andy Parker Flagged: Impediment Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Jo Rhett commented on an issue Re: 3.6.1 issues warning message for deprecation I don't believe this should be closed, for all the reasons I documented above. This change is causing large Puppet sites to disable monitoring of the agent entirely, or to filter out all depreciation messages – as the fix for this bug shows. This means that the warning message itself has no value, and thus serves no purpose other than to cause mid and large companies to get bludgeoned into the group with warning messages about no operational problem. I'll see if some of my PE customers can convince you of this. 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
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Kurt Wall Component/s: DOCS Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Eric Sorenson commented on an issue Re: 3.6.1 issues warning message for deprecation Jo Rhett I'll punch this up in the release notes and announce emails. There's a slew of similar deprecations coming as we near the end of the 3.x series so it's important to let everyone know what's going to change, but I totally empathize with you regarding the log spam. 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
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Andy Parker commented on an issue Re: 3.6.1 issues warning message for deprecation Dominic Cleal, I mostly agree with you, but we put in the message because it turned out that when we did change the behavior of the rpm provider some users got caught by surprise. Jo Rhett, I understand your frustration with the log spam, but I don't agree that this is an invalid means of communicating changes. There isn't anything I can do about the past versions, but you'll be able to turn off these messages going forward. The reason that I avoid relying only on release notes is because I know myself and I know what I've seen from others. For the most part, people don't read the documentation when trying to update software. Usually what ends up happening is that they try to update, all sorts of things that they never anticipated stop working, they fight with it for a while, and then they give up and never update. Given the number of changes, some subtle, some not so subtle, that we are building up for puppet 4, I think that having everyone read release notes, do a review of every way that they are using puppet, making changes, and hope that it will now work on the new version isn't a very reasonable expectation. This lead us, and me, to put in warnings to inform users when they are doing something that will be going away or changing. So why have them turned on by default? I want users to upgrade. I want them to be using the newest features and giving feedback. I don't want users waiting until the last moment to try to rid themselves of all of the old features that they were using. In order to do this we have puppet issue the deprecation warnings by default so that everyone knows what is changing. We often have the deprecation warning point to more information, when the message itself won't provide enough. We have feature flags to enable the new behavior so that users can use it and get off of the deprecated functionality. Finally we are working to make sure the the largest changes between major versions are mostly about just removing deprecated functionality and removing feature flags. Add Comment Puppet / PUP-2650 3.6.1 issues warning message for deprecation
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Jo Rhett commented on an issue Re: 3.6.1 issues warning message for deprecation I'm right with you on the communication. Love it. Singing to the choir. 7,000+ systems telling me every time they update isn't a choir, it's an overwhelming, thundering catastrophe. It becomes a TURN IT OFF NOW! mandate in any operational situation. Production, remember? We can't have one system drowning out important alerts with unimportant (today) communications about (future) changes. So I don't think you are going to achieve your goal of communication. I believe you are going to force everyone to blind themselves, and thus you have removed a channel to warn people. This will not achieve your goal. 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-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Jo Rhett commented on an issue Re: 3.6.1 issues warning message for deprecation If you are going to continue this path, please at least provide documentation for what the user's revised expectations should be. Hiding this in a JIRA issue (as is typical) is completely insufficient for such a big change in development style and production policy at active sites. 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
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Rob Reynolds commented on an issue Re: 3.6.1 issues warning message for deprecation Passed CI on https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Stable/job/Puppet-Package-Acceptance-stable/431 , https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-stable-vcloud-and-github/293/ (Windows) and https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Solaris-stable-vcloud-and-github/261/ (Solaris) 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
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Kurt Wall Assignee: KurtWall Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kurt Wall commented on an issue Re: 3.6.1 issues warning message for deprecation Joshua Partlow This is not passing review in master at SHA=81e1b5fa3d05ac861fe4e9de389d925aa857f74f. --disable_warnings is an invalid option and I still see the deprecation warning for catalog_format. # bundle exec puppet apply -e 'notice(hi)' --catalog_format nonesuch --disable_warnings deprecations Warning: Setting 'catalog_format' is deprecated; use 'preferred_serialization_format' instead. (at /root/puppet/lib/puppet/settings.rb:1294:in `set') Warning: Setting 'catalog_format' is deprecated; use 'preferred_serialization_format' instead. (at /root/puppet/lib/puppet/settings.rb:564:in `block (2 levels) in parse_config') Error: Could not parse application options: invalid option: --disable_warnings 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-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Andy Parker assigned an issue to Adrien Thebo Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Andy Parker Assignee: AdrienThebo Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Kylo Ginsberg Sprint: Week2014-5-28to2014-6-4 ,Week2014-6-4to2014-6-11 Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Andy Parker updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Andy Parker Flagged: Impediment Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Adrien Thebo commented on an issue Re: 3.6.1 issues warning message for deprecation Merged in 8c5313a. 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Jo Rhett commented on an issue Re: 3.6.1 issues warning message for deprecation I still think that having puppet kick out warning messages every run is the wrong thing to do. If you are going to hack in a feature, then disable the warning messages and allow them to be enabled if desired. There are Release Notes and they have their purposes. Having 7,000 servers tell me every 30 minutes about a deprecation notice is NEVER a valid communication method. 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
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Jo Rhett commented on an issue Re: 3.6.1 issues warning message for deprecation Furthermore, `disable_warnings` is only valid in 6.2+ so it doesn't solve the problem that we can't put this into puppet configuration files unless we use a template, thus breaking sites which use concat or a fixed file. 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 group at http://groups.google.com/group/puppet-bugs. For
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Adrien Thebo Assignee: AdrienThebo Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Adrien Thebo commented on an issue Re: 3.6.1 issues warning message for deprecation Functional review steps: Ensure that running `puppet resource package --disable_warnings deprecations` on platforms that have the `allow_virtual` parameter do not emit deprecation warnings. The following should also work: └ bexec puppet apply -e 'notice(hi)' --disable_warnings deprecations --catalog_format loldeprecated Notice: Scope(Class[main]): hi Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.01 seconds Notice: Finished catalog run in 0.10 seconds └ bexec puppet apply -e 'notice(hi)' --catalog_format loldeprecated Warning: Setting 'catalog_format' is deprecated; use 'preferred_serialization_format' instead. (at /home/adrien/eng/projects/platform/puppet/lib/puppet/settings.rb:1296:in `set') Notice: Scope(Class[main]): hi Notice: Compiled catalog for grey.somethingsinistral.net in environment production in 0.01 seconds Notice: Finished catalog run in 0.10 seconds (The --disable_warnings deprecations must be before the deprecated setting to ensure it can be set in time to disable the warnings for the other setting) 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...
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Joshua Partlow Assignee: JoshuaPartlow Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Rob Reynolds commented on an issue Re: 3.6.1 issues warning message for deprecation Kylo Ginsberg - what would the default be? 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg commented on an issue Re: 3.6.1 issues warning message for deprecation Okay after some more discussion we ended up with the idea of a --disable-warnings setting which could take a list of settings but currently only supports deprecations. 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Kylo Ginsberg Fix Version/s: 3.6.2 Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Kylo Ginsberg Story Points: 1 Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Joshua Cooper Sprint: Week2014- 5 6 - 28 4 to2014-6- 4 11 Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Kylo Ginsberg Sprint: Week2014- 6 5 - 4 28 to2014-6- 11 4 Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Kylo Ginsberg Sprint: Week2014-5-28to2014-6-4 Add Comment 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg commented on an issue Re: 3.6.1 issues warning message for deprecation After some [discussion](https://groups.google.com/forum/?utm_medium=emailutm_source=footer#!msg/puppet-users/QadW3Px9GEU/Y50Lhrf0fJsJ) on #puppet-dev, the conclusion was to add an ignore-deprecation-warnings setting, which defaults to false. 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 group at
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Paul Seymour created an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Issue Type: Bug Affects Versions: 3.6.1 Assignee: Unassigned Created: 23/May/14 2:57 AM Priority: Normal Reporter: Paul Seymour 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 `set_default') Add Comment
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Dominic Cleal commented on an issue Re: 3.6.1 issues warning message for deprecation While I appreciate the changes to virtual packages noted in the release notes are slightly complex, this warning (any time a package + yum resource is used) probably isn't necessary for most users. It seems to me that virtual package support is regarded as a positive change in the upcoming Puppet 4, so I don't think a warning on each run is needed to inform users that they might be missing out on it. I'd ask for the log level to be changed to info or notice, or for the deprecation warning to be removed entirely. I think the release notes are clear and probably sufficient: http://docs.puppetlabs.com/puppet/latest/reference/release_notes.html#changes-to-rpm-behavior-with-virtual-packages. I'm unsure that users should have to follow the recommendation to set a system-wide default for allow_virtual to quieten this message. 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-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Chuck Schweizer commented on an issue Re: 3.6.1 issues warning message for deprecation Also setting allow_virtual = true only works if all of your Puppet Masters and Agent are at least 3.6.1. It would be very nice if there wasn't a warning on this message. 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Aaron Zauner commented on an issue Re: 3.6.1 issues warning message for deprecation what's the reasoning behind this being a warning message? thanks. 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 group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
