Jira (PUP-4379) Future parser interpolation with [] after variable prefixed with underscore
Title: Message Title Hailee Kenney commented on PUP-4379 Re: Future parser interpolation with [] after variable prefixed with underscore Merged into puppet/3.x in 2acc90a puppet/3.x merged into pe-puppet/3.8.x in caa665e Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title Chris Denneen commented on PUP-1131 Re: Puppet raises error when trying to set owner to non-existant user Installed 3.7.5 on Solaris 2.6 with rubygems. Getting this via trace: bash-2.05# puppet agent -t --noop --verbose --debug --trace Debug: Failed to load library 'selinux' for feature 'selinux' Debug: Failed to load library 'shadow' for feature 'libshadow' Debug: Puppet::Type::User::ProviderPw: file pw does not exist Debug: Puppet::Type::User::ProviderLdap: true value when expecting false Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/uuidgen does not exist Debug: Puppet::Type::User::ProviderUseradd: file chage does not exist Debug: Puppet::Type::User::ProviderPw: file pw does not exist Debug: Puppet::Type::User::ProviderLdap: true value when expecting false Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/uuidgen does not exist Debug: Puppet::Type::User::ProviderUseradd: file chage does not exist Error: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: undefined method `exists?' for nil:NilClass /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/type/user.rb:382:in `exists?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:800:in `service_user_available?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `send' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `safe_to_use_settings_value?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:43:in `value' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:106:in `owner' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:160:in `to_resource' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:916:in `to_catalog' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:912:in `each' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:912:in `to_catalog' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:982:in `use' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application/agent.rb:404:in `setup' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:378:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:507:in `plugin_hook' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:378:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/util.rb:488:in `exit_on_fail' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:378:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/util/command_line.rb:146:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/util/command_line.rb:92:in `execute' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/bin/puppet:8 /usr/local/bin/puppet:23:in `load' /usr/local/bin/puppet:23 Error: Could not prepare for execution: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: undefined method `exists?' for nil:NilClass undefined method `exists?' for nil:NilClass /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/type/user.rb:382:in `exists?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:800:in `service_user_available?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `send' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `safe_to_use_settings_value?'
Jira (PUP-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title
Chris Denneen commented on PUP-1131
Re: Puppet raises error when trying to set owner to non-existant user
I've manually added puppet user and group. I've manually added /etc/puppet/puppet.conf, and /var/lib/puppet/ {bucket,clientbucket,lib,log,run,ssl,state,yaml}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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-4390) Regression: Windows service provider fails to retrieve current state on 2003
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4390 Regression: Windows service provider fails to retrieve current state on 2003 Change By: Rob Reynolds Component/s: Windows Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4390) Regression: Windows service provider fails to retrieve current state on 2003
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4390 Regression: Windows service provider fails to retrieve current state on 2003 Change By: Rob Reynolds Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4390) Regression: Windows service provider fails to retrieve current state on 2003
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-4390 Regression: Windows service provider fails to retrieve current state on 2003 Change By: Rob Reynolds Scope Change Reason: FoundaregressionrelatedtoWindows2003 Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4196) agent command line options ignored running under systemd
Title: Message Title Melissa Stone updated an issue Puppet / PUP-4196 agent command line options ignored running under systemd Change By: Melissa Stone Sprint: RE2015-05-06 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4390) Regression: Windows service provider fails to retrieve current state on 2003
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-4390 Regression: Windows service provider fails to retrieve current state on 2003 Change By: Ethan Brown Assignee: EthanBrown Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PDB-1421) PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1421 PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/04/10 3:28 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) add upgrading from v3 document to stable branch Author: Wyatt Alt Company: Github ID: wkalt Pull Request 1347 Discussion Pull Request 1347 File Diff Pull Request Description This adds the upgrading from v3 document to our stable branch, for better visibility to users. (webhooks-id: 878025164833eb22cb4a4704105a3df9)
Jira (PDB-1421) PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt
Title: Message Title gepetto-bot commented on PDB-1421 Re: PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt wkalt commented: this was a change suggested by @MosesMendoza. The stable branch has much better user visibility than master, so to the extent that we can communicate these changes from the stable docs, we should. We need to be careful that we are sure that everything mentioned in this document will remain true through release time, and we should be sure to cut out mention of any changes that we may yet revert. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4389) Write acceptance test for puppet agent service
Title: Message Title Kurt Wall commented on PUP-4389 Re: Write acceptance test for puppet agent service Closed the wrong one. :-\ Reopened. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-408) Puppet package acceptance is sufficient for a smoke test
Title: Message Title Kurt Wall updated an issue Puppet / PUP-408 Puppet package acceptance is sufficient for a smoke test Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-408) Puppet package acceptance is sufficient for a smoke test
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-408 Puppet package acceptance is sufficient for a smoke test Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (FACT-952) Update or remove man page
Title: Message Title Michael Smith created an issue Facter / FACT-952 Update or remove man page Issue Type: Bug Assignee: Unassigned Created: 2015/04/10 4:12 PM Fix Versions: FACT 3.0.0 Labels: DOCS Priority: Normal Reporter: Michael Smith The man page at man/man8 hasn't been updated since February 2014. We need to update it for Facter 3. Add Comment
Jira (FACT-951) Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-951 Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono Change By: Michael Smith Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4391) tag collecting is broken in 3.7
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4391
tag collecting is broken in 3.7
Change By:
Henrik Lindberg
whenusingacollectortogetresourcestaggedwithacertainvalueifthe'calling'classhasthesamenameALLresourcesarecollected.3.6thiswasnotthecase,nordoIseehowitiseitherusefulormakessensetobethecase.forexample {code} ==site.pp==nodedefault{includenoticegroups::matches}==modules/noticegroups/manifests/matches.pp==classnoticegroups::matches{includenoticesNotices::Anotice|tag==matches|}==modules/notices/manifests/anotice.pp==definenotices::anotice{notify{$title:}}==modules/notices/manifests/data.pp==classnotices::data{@notices::anotice{'meanttobemade':tag=['matches'],}@notices::anotice{'NOTmeanttobemade':tag=['doesnotmatch'],}}==modules/notices/manifests/init.pp==classnotices{includenotices::data} {code} under3.6Igetjustthe {code} notices::anotice{'meanttobemade'} {code} realized,under3.7botharerealizedifIchange {{ noticegroups::matches }} to {{ noticegroups::iwantmatches }} IgetjusttheonerealizedThisisbrokenbehaviourimho
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 (FACT-951) Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono
Title: Message Title Michael Smith commented on FACT-951 Re: Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono Missed updating Windows build script. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4391) tag collecting is broken in 3.7
Title: Message Title Henrik Lindberg commented on PUP-4391 Re: tag collecting is broken in 3.7 Neil Prockter Is this with or without future parser? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PDB-1420) Broken links on 2.3 API page
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1420 Broken links on 2.3 API page Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PDB-1420) Broken links on 2.3 API page
Title: Message Title Wyatt Alt commented on PDB-1420 Re: Broken links on 2.3 API page David McCauley Thanks for pointing this out. I updated those links and resolved a couple other inconsistencies. Be aware that the documentation for our latest release is here: https://docs.puppetlabs.com/puppetdb/latest/ The docs you're linking to are for our unreleased development branch (slated for the PDB 3.0 release). Wyatt Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4391) tag collecting is broken in 3.7
Title: Message Title Henrik Lindberg assigned an issue to Neil Prockter Puppet / PUP-4391 tag collecting is broken in 3.7 Change By: Henrik Lindberg Assignee: NeilProckter Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PDB-1420) Broken links on 2.3 API page
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1420 Broken links on 2.3 API page Change By: Wyatt Alt Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PDB-1421) PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1421 PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt Change By: Wyatt Alt Assignee: WyattAlt Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PDB-1421) PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1421 PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt Change By: Wyatt Alt Sprint: PuppetDB2015-04-22 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4388) Remove /etc/default/puppet on Debian
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-4388 Remove /etc/default/puppet on Debian Change By: William Hopper Assignee: WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 (PDB-1421) PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt
Title: Message Title gepetto-bot commented on PDB-1421 Re: PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1031/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4387) Cyan colored notices
Title: Message Title Henrik Lindberg commented on PUP-4387 Re: Cyan colored notices Do we really want the cyan color back for Notice? It has been without color for quite some time now. (I for one would not like it back) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-3425) resource_type face search/find returns empty results
Title: Message Title Henrik Lindberg commented on PUP-3425 Re: resource_type face search/find returns empty results Eric Sorenson Earlier things just worked most of the time when the various parts of the system decided on their own to resolve in which environment to operate. The problem with that was that not all parts of the system had the same understanding (or possibility to correctly understand) in which environment they should do the processing in. That was one source to all the pains in getting support for directory environments right (i.e. all of a sudden some command would execute some part of the workload in the wrong environment; we have seen many tickets on that theme). For that reason, we now require that the logic that is at the start/edge of a transaction (an application, a request, etc.) to configure the puppet context with the appropriate values; the :current_environment is one such context value that is used by many parts of the system, but is not an absolute requirement to have it set. The requirement also helps find the places where the :current_environment should have been set (it would earlier potentially have grabbed the wrong environment). I guess this could be considered an API change, not for Faces, but for Puppet. Most logic does not have to deal with the context and environment because they are working within a request from an agent, or other operations that involve a node object where environment is set in the node. My guess is that that is the reason we have not seen reports about this earlier. I think How to set up which environment to use is needed in documentation and that it should describe the different scenarios (is an environment needed at all, is something else setting it up, how to find, load and ask for information from an environment). I am not aware if we have anything like that today - you would need to reverse engineer how other commands do this, or read up on a lot of low level class documentation to figure this out. I do think documentation is the best fix for this problem as I have a hard time seeing a general fix to the faces framework that would not at the same time cause other problems similar to those we have had in the past. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4391) tag collecting is broken in 3.7
Title: Message Title Henrik Lindberg commented on PUP-4391 Re: tag collecting is broken in 3.7 I believe that there were fixes that changed that behavior because it was considered broken otherwise (not everything collected as expected). The semantics of a collection is all resource already present or present in the future in the same compilation that matches the criteria. Thus if something is collected into a context that will cause the resource to be tagged with all name segments. If a resource is explicitly tagged with a string matching one of the segments that is automatically applied, there is no way to tell the two apart. To be safe you should use explicit tags that do not clash with the automatically assigned tags - irrespective of what those rules are since you do not typically have full control over which tags that are actually set when the code is used (esp. if you are publishing a module). Unfortunately there is not detailed specification of how tags should work and this makes it debatable if one behavior or the other is correct. Some think tagging is too pervasive, other want extensive tagging. It is also difficult to find safe unique keys since there is always a risk that something is included or used in a fashion that causes it to be tagged with an unwanted tag. (One reason being that tags cannot be name-spaced, another that you cannot query for included directly/indirectly by ... as opposed to just using tags. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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.
