Jira (PUP-6766) calling_all_functions test fails on master
Title: Message Title William Hopper commented on PUP-6766 Re: calling_all_functions test fails on master That test was modified yesterday, but the change passed CI at least once and seems unrelated. https://github.com/puppetlabs/puppet/commit/832d27d4d745bbc8e65b2433020f3c2e15acedf2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6766) calling_all_functions test fails on master
Title: Message Title William Hopper created an issue Puppet / PUP-6766 calling_all_functions test fails on master Issue Type: Bug Assignee: Unassigned Created: 2016/09/30 4:57 PM Environment: puppet#master, all platforms Priority: Normal Reporter: William Hopper The full error output: 16:49:29 Failed Tests Cases: 16:49:29 Test Case tests/parser_functions/calling_all_functions.rb reported: # 16:49:29 Expected /Map:\ Scope\(Class\[main\]\):\ \[7,\ 8,\ 9\]/ to match "\e[mNotice: Scope(Class[main]): sayeth Assert_type: Scope(Class[main]): Valar morghulis\e[0m\n\e[mNotice: Scope(Class[main]): 1\e[0m\n\e[mNotice: Scope(Class[main]): 2\e[0m\n\e[mNotice: Scope(Class[main]): 3\e[0m\n\e[mNotice:
Jira (PDOC-106) Acceptance tests for strings JSON output
Title: Message Title William Hopper commented on PDOC-106 Re: Acceptance tests for strings JSON output PR at https://github.com/puppetlabs/puppet-strings/pull/106 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-106) Acceptance tests for strings JSON output
Title: Message Title William Hopper commented on PDOC-106 Re: Acceptance tests for strings JSON output Immediately after creating this ticket I looked at https://github.com/puppetlabs/puppet-strings/blob/master/spec/unit/puppet-strings/json_spec.rb and realized JSON output is already covered in specs. I'm going to add a small test to ensure the --emit-json options are working, and we'll be pretty much set. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6712) Make reference to Resource Type in dependency work as reference realized instances
Title: Message Title Henrik Lindberg commented on PUP-6712 Re: Make reference to Resource Type in dependency work as reference realized instances I updated the description to reflect what can be implemented. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6712) Make reference to Resource Type in dependency work as reference realized instances
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6712 Make reference to Resource Type in dependency work as reference realized instances Change By: Henrik Lindberg Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6712) Make reference to Resource Type in dependency work as reference realized instances
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6712
Make reference to Resource Type in dependency work as reference realized instances
Change By:
Henrik Lindberg
Make it possible to use dependencies between resource types with the semantically equivalance of using a collector of all, but with the difference that virtual resources are not realized.For example:{code:puppet}Yumrepo -> Package{code}Which would be semantically equivalent to:{code:puppet}Yumrepo <| |> -> Package <| |>{code}with the exception that the former does not realize virtual resources.Likewise, it should be allowed to use an array of resource type references such that:{code:puppet}[ A, B ] -> C{code}is equivalent to{code:puppet}A -> CB -> C{code}The evaluation of "the set of resource instances" does not follow evaluation order (just like the collector does).Implementation wise, this probably requires a new kind of collector (one never seen by users).ORIGINAL(The original idea is not implementable, but shows the origin of the idea). There are a number of use cases where lots of different resource types need to require and notify the same things... eg{code}Foo <||> -> Resource_one<||> ~> Bar<||>Foo <||> -> Resource_two<||> ~> Bar<||>Foo <||> -> Resource_three<||> ~> Bar<||>Foo <||> -> Resource_four<||> ~> Bar<||>{code}A couple of real world examples of this are:https://github.com/crayfishx/puppet-firewalld/blob/3.1.4/manifests/init.pp#L163-L169https://github.com/voxpupuli/puppet-splunk/blob/4.0.0/manifests/init.pp#L189-L248The current chaining syntax is quite repetitive, it would make more sense if you could include arrays in resource chaining, so this:{code} Service['firewalld'] -> Firewalld_zone <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_rich_rule <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_service <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_port <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_direct_chain <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_direct_rule <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_direct_passthrough <||> ~> Exec['firewalld::reload']{code}Could be written more cleanly as something like:{code} Service['firewalld'] -> [ Firewalld_zone <||>, Firewalld_rich_rule <||>, Firewalld_service <||>, Firewalld_port <||>, Firewalld_direct_chain <||>, Firewalld_direct_rule <||>, Firewalld_direct_passthrough <||> ] ~> Exec['firewalld::reload']{code}So a chain to an array of references will apply the relationship to all members of the array.
Add Comment
Jira (FACT-1492) FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016
Title: Message Title
Moses Mendoza commented on FACT-1492
Re: FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016
Maggie Dreyer I think that is indeed what we want.
As you noted, for the server platforms [os][release][full] and [os][release][major] we've done the year (+ release number if present) string, and we want to keep that behavior for Windows Server 2016.
E.g., we should get back
{os => {"release"=>{"major"=>"2016", "full"=>"2016"}}}
AFAICT the only distinction between long and short versions on the server platforms comes from the kernel version facts, ie on Server 2012 R2:
kernelmajversion => 6.3
kernelrelease => 6.3.9600
kernelversion => 6.3.9600
For Windows 10 (and other consumer versions) I believe we should indeed use the first integer of the kernel version as the value for os release major, ie facter should return
{os => {"release"=>{"major"=>"10", "full"=>"10.0.10586"}}}
and for kernel
Jira (PUP-6712) Make reference to Resource Type in dependency work as reference realized instances
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6712 Make reference to Resource Type in dependency work as reference realized instances Change By: Henrik Lindberg Summary: Arrays Make reference to Resource Type in resource chaining dependency work as reference realized instances Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6765) Using produce/consume results in 'Attempt to redefine entity' errors
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-6765 Using produce/consume results in 'Attempt to redefine entity' errors Issue Type: Bug Assignee: Thomas Hallgren Created: 2016/09/30 3:45 PM Fix Versions: PUP 4.8.0 Priority: Normal Reporter: Thomas Hallgren Using generated pcore resource types in combination with app management produce/consume declarations fails with 'Attempt to redefine entity' errors. Add Comment This
Jira (PUP-1038) puppet fails if template contains invalid utf-8
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1038 puppet fails if template contains invalid utf-8 Change By: Ethan Brown Labels: i18n redmine utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1191) Puppet should not reset locale
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1191 Puppet should not reset locale Change By: Ethan Brown Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1191) Puppet should not reset locale
Title: Message Title Ethan Brown commented on PUP-1191 Re: Puppet should not reset locale Bringing into epic PUP-6718 - likely this is already fixed and can be closed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1191) Puppet should not reset locale
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1191 Puppet should not reset locale Change By: Ethan Brown Labels: i18n redmine utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6705) Add Sensitive type to Puppet Serialization
Title: Message Title Henrik Lindberg commented on PUP-6705 Re: Add Sensitive type to Puppet Serialization I thought more about this - and it is really more about the current implementation of Sensitive support in a Resource. We should test what happens when a Sensitive instance is inside an array (with other values), in a hash, or in an Object. I am uncertain if the current implementation does a deep recursion or not, and if it does how it discerns between the sensitive and non sensitive parts of such a structure. (Guess is that it does not do this). That means that an opt_in would make that work as it would then transport the Sensitive instance to the agent where the type/provider implementation would have to know how to use that. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1492) FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Facter / FACT-1492 FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016 Change By: Moses Mendoza Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6753) Puppet log functions should return Undef rather than a Puppet::Util::Log object
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6753 Puppet log functions should return Undef rather than a Puppet::Util::Log object Change By: Henrik Lindberg Acceptance Criteria: * The logging functions should return undef Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6753) Puppet log functions should return Undef rather than a Puppet::Util::Log object
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6753
Puppet log functions should return Undef rather than a Puppet::Util::Log object
Change By:
Henrik Lindberg
Release Notes Summary:
All of the logging functions (like 'notice', 'debug') leaked a puppet internal value to the Puppet Language. Under rare circumstances the returned value could be used to produce a string value. This is now fixed so that the logging functions always returns {{undef}} as intended.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Make CI job to add PO files to repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Make CI job to add PO files to repo Change By: Geoff Nichols Sprint: AP Grooming Top 10 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6762) SPIKE - How and when do we get PO files from Transifex?
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6762 SPIKE - How and when do we get PO files from Transifex? Change By: Geoff Nichols Sprint: AP Grooming Top 10 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) SPIKE - Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 SPIKE - Find a workflow for POT file generation Change By: Geoff Nichols Sprint: AP Grooming Top 10 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6474 Incorporate gettext_setup gem into puppet Change By: Geoff Nichols Sprint: AP Grooming Top 11-20 10 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6763) Make CI job to update POT file
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6763 Make CI job to update POT file Change By: Geoff Nichols Sprint: AP Grooming Top 10 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1031) Improve Puppet's handling of non-ASCII character encodings
Title: Message Title Ethan Brown commented on PUP-1031 Re: Improve Puppet's handling of non-ASCII character encodings Closing this epic as all tickets have been sorted / prioritized into other related epics. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1804) Improve testing around \u in puppet language
Title: Message Title Ethan Brown commented on PUP-1804 Re: Improve testing around \u in puppet language Henrik Lindberg I'm removing the PUP-1031 epic in an effort to close that off. This seems like a ticket that belongs in a separate language (or similar) related epic like the ones that we've created at PUP-6718 / PUP-6719 / PUP-6720. I'd suggest creating that new epic and having it block the LOC-11 epic. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1804) Improve testing around \u in puppet language
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1804 Improve testing around \u in puppet language Change By: Ethan Brown Labels: i18n utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1800) Ruby downcase does not handle all unicode letters
Title: Message Title Ethan Brown commented on PUP-1800 Re: Ruby downcase does not handle all unicode letters Henrik Lindberg I'm removing the PUP-1031 epic in an effort to close that off. This seems like a ticket that belongs in a separate language (or similar) related epic like the ones that we've created at PUP-6718 / PUP-6719 / PUP-6720. I'd suggest creating that new epic and having it block the LOC-11 epic. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Ethan Brown commented on PUP-776 Re: Deprecate non-UTF-8 encodings for textual content Puppet 4 introduced UTF-8 as the default for everything, and it as documented as such. We didn't officially enforce it until the 4.4.0 release as part of PUP-5728 / PUP-5879 . There might be a few other tickets in PUP-3746 that were applicable as well. I'm going to close this ticket as I don't believe there's any actual work here to be done anymore, in an effort to close out the PUP-1031 epic (or sort remaining tix to PUP-6718 PUP-6719 or PUP-6720 as appropriate). If someone disagrees, feel free to re-open - but I think we're good on this one. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Ethan Brown updated an issue Puppet / PUP-776 Deprecate non-UTF-8 encodings for textual content Change By: Ethan Brown Labels: deprecation i18n redmine utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-736) Encoding mis-matches cause package prefetching to fail
Title: Message Title Ethan Brown updated an issue Puppet / PUP-736 Encoding mis-matches cause package prefetching to fail Change By: Ethan Brown Labels: customer encoding i18n redmine utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1386) puppet agents complain about master not-being UTF-8
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1386 puppet agents complain about master not-being UTF-8 Change By: Ethan Brown Labels: customer i18n redmine utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3377) Puppet fails to manage file resources containing invalid UTF-8
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3377 Puppet fails to manage file resources containing invalid UTF-8 Change By: Ethan Brown Labels: i18n utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5728) Change default parsing of manifest files to UTF-8
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5728 Change default parsing of manifest files to UTF-8 Change By: Ethan Brown Labels: i18n utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1441) --show_diff causes crashes on files with UTF-8 content
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1441 --show_diff causes crashes on files with UTF-8 content Change By: Ethan Brown Labels: i18n type_augeas type_file utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1055) "invalid byte sequence" with service provider upstart
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1055 "invalid byte sequence" with service provider upstart Change By: Ethan Brown Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1055) "invalid byte sequence" with service provider upstart
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1055 "invalid byte sequence" with service provider upstart Change By: Ethan Brown Labels: i18n redmine utf-8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3075) PuppetDB doesn't die when presented with an empty certificate file and starts using 200% CPU
Title: Message Title Wyatt Alt commented on PDB-3075 Re: PuppetDB doesn't die when presented with an empty certificate file and starts using 200% CPU Trevor Vaughan Thanks for reporting – I looked into this today. It actually affects all of Puppet's services on systemd, and is a side effect of the Restart parameter added here: https://github.com/puppetlabs/ezbake/commit/f7c9704ae563ebf1d331a48c33099e4be5da1c3b. The rationale behind the decision was that it's the desired behavior in most cases, although I don't have specifics. Since it's not a PDB issue I'm going to close this as wontfix. If you feel strongly about it feel free to raise a ticket on the EZ project and explain your point of view there. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Make CI job to add PO files to repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Make CI job to add PO files to repo Change By: Geoff Nichols Acceptance Criteria: Job exists in ci-job-configs and is deployed to POC pipeline. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6764) Make CI job to add PO files to repo
Title: Message Title Geoff Nichols created an issue Puppet / PUP-6764 Make CI job to add PO files to repo Issue Type: Task Assignee: Unassigned Created: 2016/09/30 1:48 PM Priority: Normal Reporter: Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-6763) Make CI job to update POT file
Title: Message Title Geoff Nichols created an issue Puppet / PUP-6763 Make CI job to update POT file Issue Type: Task Assignee: Unassigned Created: 2016/09/30 1:46 PM Priority: Normal Reporter: Geoff Nichols Make CI job to update the POT files after string changes in code. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6761) SPIKE - Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 SPIKE - Find a workflow for POT file generation Change By: Geoff Nichols Summary: SPIKE - Find a workflow for POT file generation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6762) SPIKE - How and when do we get PO files from Transifex?
Title: Message Title Geoff Nichols created an issue Puppet / PUP-6762 SPIKE - How and when do we get PO files from Transifex? Issue Type: Task Assignee: Unassigned Created: 2016/09/30 1:43 PM Priority: Normal Reporter: Geoff Nichols Design a workflow for getting files from Transifex to us. Does the Transifex integration use a push or pull model? If push model, what are the security implications and design to mitigate? Add Comment
Jira (PDOC-106) Acceptance tests for strings JSON output
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-106 Acceptance tests for strings JSON output Change By: William Hopper Sprint: PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 Find a workflow for POT file generation Change By: Geoff Nichols * Find answer to question "What is the directory structure for translation (PO and POT) files?"* Design a workflow for POT file generation* For the POC, this should be a close as possible to the workflow used for other languages. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3067) Switch command logging from message id to '-'
Title: Message Title Dan Lidral-Porter assigned an issue to Dan Lidral-Porter PuppetDB / PDB-3067 Switch command logging from message id to '-' Change By: Dan Lidral-Porter Assignee: Dan Lidral-Porter Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 Find a workflow for POT file generation Change By: Geoff Nichols * Design a workflow for POT file generation * For the POC, this should be a close as possible to the workflow used for other languages. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 Find a workflow for POT file generation Change By: Geoff Nichols * * For the POC, this should be a close as possible to the workflow used for other languages. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 Find a workflow for POT file generation Change By: Geoff Nichols Acceptance Criteria: For the POC, this should be a close as possible Workflow documented and proposed to the workflow used for other languages. discuss@agent-and-platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-106) Acceptance tests for strings JSON output
Title: Message Title William Hopper assigned an issue to William Hopper Puppet Strings / PDOC-106 Acceptance tests for strings JSON output Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 Find a workflow for POT file generation Change By: Geoff Nichols Summary: Find a workflow for PO POT file generation Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) Find a workflow for PO file generation
Title: Message Title Geoff Nichols created an issue Puppet / PUP-6761 Find a workflow for PO file generation Issue Type: Task Assignee: Unassigned Created: 2016/09/30 1:32 PM Priority: Normal Reporter: Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols Team: Agent & Platform Epic Status: To Do Epic Name: End-to-end POC for string externalization in Puppet Status: Accepted Designing Workflow: Scrum Teams Engineering Epic Workflow Issue Type: Task Epic Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols Team/s: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols h5. In scope:* Wrap one simple string* in the puppet repo with the _() gettext function * Create a CI job that uses the gettext-setup gem tooling to generate a POT file, and a PO file for Japanese* Add the puppet repo to the Transifex integration and test that the PO file is automatically pulled into Transifex when updates are made to it (Larissa)* When the PO file reaches 100% translated and reviewed in Transifex, it is automatically updated in the puppet repo (Larissa)* Add a setting to check the user's locale and display supported languages or default to English* Test on an OS that has the environment set to Japanese* Consider stripping the line numbers out of the POT file to reduce churn*Simple string means a string that isn't composed or concatenated* Talk to [~libby] about the CI jobs she is creating for Clojure and _javascript_h5. Out of scope* An opt-out option to turn off localized strings, but this should be considered for another ticket. * Add a setting to check the user's locale and display supported languages or default to English Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols h5. In scope: * Wrap one simple string* in the puppet repo with the _() gettext function * Create a CI job that uses the gettext-setup gem tooling to generate a POT file, and a PO file for Japanese* Add the puppet repo to the Transifex integration and test that the PO file is automatically pulled into Transifex when updates are made to it (Larissa)* When the PO file reaches 100% translated and reviewed in Transifex, it is automatically updated in the puppet repo (Larissa)* Add a setting to check the user's locale and display supported languages or default to English* Test on an OS that has the environment set to Japanese* Consider stripping the line numbers out of the POT file to reduce churn*Simple string means a string that isn't composed or concatenated* Talk to [~libby] about the CI jobs she is creating for Clojure and _javascript_ * h5. Out of scope is an * An opt-out option to turn off localized strings, but this should be considered for another ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols * Wrap one simple string* in the puppet repo with the _() gettext function * Create a CI job that uses the gettext-setup gem tooling to generate a POT file, and a PO file for Japanese * Add the puppet repo to the Transifex integration and test that the PO file is automatically pulled into Transifex when updates are made to it (Larissa) * When the PO file reaches 100% translated and reviewed in Transifex, it is automatically updated in the puppet repo (Larissa) * Add a setting to check the user's locale and display supported languages or default to English * Test on an OS that has the environment set to Japanese * Consider stripping the line numbers out of the POT file to reduce churn*Simple string means a string that isn't composed or concatenated * Talk to [~libby] about the CI jobs she is creating for Clojure and _javascript_ * Out of scope is an opt-out option to turn off localized strings, but this should be considered for another ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-3075) PuppetDB doesn't die when presented with an empty certificate file and starts using 200% CPU
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-3075 PuppetDB doesn't die when presented with an empty certificate file and starts using 200% CPU Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-106) Acceptance tests for strings JSON output
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-106 Acceptance tests for strings JSON output Change By: William Hopper Story Points: 3 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-88) Create a test plan for ensuring strings support going forward
Title: Message Title William Hopper commented on PDOC-88 Re: Create a test plan for ensuring strings support going forward Notes from sync with EricT: The level of spec tests and HTML acceptance present with the PR linked above is sufficient. The higher priority is adding acceptance-level tests for JSON output, as this is what will be consumed by the forge. See PDOC-106. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-106) Acceptance tests for strings JSON output
Title: Message Title William Hopper created an issue Puppet Strings / PDOC-106 Acceptance tests for strings JSON output Issue Type: Bug Assignee: Unassigned Created: 2016/09/30 11:30 AM Priority: Normal Reporter: William Hopper Since the JSON output of strings is what will be consumed by the forge, we want to add some more robust acceptance tests to ensure that no regressions occur. We can setup a schema and run tests similar to Facter's JSON schema test. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3077) Integrate Ezbake service reload and logback/logrotate changes into PuppetDB
Title: Message Title Jeremy Barlow updated an issue PuppetDB / PDB-3077 Integrate Ezbake service reload and logback/logrotate changes into PuppetDB Change By: Jeremy Barlow Summary: Integrate Ezbake service reload and logback/logrotate changes into PuppetDB We'd like to integrate the following Ezbake / packaging-related changes made recently for Puppet Server into PuppetDB:* As was recently done in SERVER-1490 for Puppet Server, we'd like to integrate support the Ezbake service reload changes into OSS in PuppetDB. * As was done in SERVER-366 for Puppet Server, migrate logging config from logrotate to logback in order to help users limit maximum disk usage. This ticket covers that both pieces of work. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3077) Integrate Ezbake service reload changes into PuppetDB
Title: Message Title Jeremy Barlow commented on PDB-3077 Re: Integrate Ezbake service reload changes into PuppetDB Ryan Senior - Chris Price, Joe Pinsonault, and I were planning on just taking this on for all projects as part of our overall HUP / service reload epic so I'd hope you wouldn't need to pull a PuppetDB maintainer into this for anything but consulting. I'd definitely like to hear your thoughts though on what PuppetDB-specific testing you think we might need to do in order to validate this integration (specific one-off integration test runs or what-not) before we'd put it into mainline code. I'd also like to hear your thoughts on what branch(es) would be appropriate to target. Just master? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3077) Integrate Ezbake service reload changes into PuppetDB
Title: Message Title Jeremy Barlow created an issue PuppetDB / PDB-3077 Integrate Ezbake service reload changes into PuppetDB Issue Type: Task Assignee: Unassigned Created: 2016/09/30 10:19 AM Priority: Normal Reporter: Jeremy Barlow As was recently done in SERVER-1490 for Puppet Server, we'd like to integrate the Ezbake service reload changes into OSS PuppetDB. This ticket covers that work. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6760) Solaris pkg provider does not correctly handle expiring cert
Title: Message Title Sean McDonald commented on PUP-6760 Re: Solaris pkg provider does not correctly handle expiring cert This is causing failures in https://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_pe-acceptance-tests_integration-system_pe_full-agent-upgrade-secondary_nightly_2016.4.x/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3057) release 4.2.3 to PE davis only
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3057 release 4.2.3 to PE davis only Change By: Wyatt Alt Sprint: Hopper FF 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3057) release 4.2.3 to PE davis only
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3057 release 4.2.3 to PE davis only Change By: Wyatt Alt Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3057) release 4.2.3 to PE davis only
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3057 release 4.2.3 to PE davis only Change By: Wyatt Alt Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3057) release 4.2.3 to PE davis only
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3057 release 4.2.3 to PE davis only Change By: Wyatt Alt Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6760) Solaris pkg provider does not correctly handle expiring cert
Title: Message Title Branan Riley updated an issue Puppet / PUP-6760 Solaris pkg provider does not correctly handle expiring cert Change By: Branan Riley Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3057) release 4.2.3 to PE davis only
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3057 release 4.2.3 to PE davis only Change By: Wyatt Alt Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6760) Solaris pkg provider does not correctly handle expiring cert
Title: Message Title Branan Riley updated an issue Puppet / PUP-6760 Solaris pkg provider does not correctly handle expiring cert Change By: Branan Riley Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6760) Solaris pkg provider does not correctly handle expiring cert
Title: Message Title Branan Riley commented on PUP-6760 Re: Solaris pkg provider does not correctly handle expiring cert This is a regression of PUP-643 . Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6760) Solaris pkg provider does not correctly handle expiring cert
Title: Message Title Branan Riley updated an issue Puppet / PUP-6760 Solaris pkg provider does not correctly handle expiring cert Change By: Branan Riley Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6760) Solaris pkg provider does not correctly handle expiring cert
Title: Message Title Branan Riley created an issue Puppet / PUP-6760 Solaris pkg provider does not correctly handle expiring cert Issue Type: Bug Assignee: Unassigned Created: 2016/09/30 9:56 AM Priority: Normal Reporter: Branan Riley The pkg provider is failing with the following when a certificate is near expiration: Error: /Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure: change from 1.5.3,5.11-1:20160720T002950Z to 1.6.2.163.938 failed: Unknown line format pkg: Certificate '/var/pkg/ssl/afdb2b56593e6ede1a95c11354c467b3b4cb' for publisher 'solarisstudio', needed to access 'https://pkg.oracle.com/solarisstudio/release/', will expire in '26' days. Add Comment
Jira (FACT-1511) Add a command line subcommand to list all cacheable fact groups
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Facter / FACT-1511 Add a command line subcommand to list all cacheable fact groups Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1509) Add command line option to ignore fact cache
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Facter / FACT-1509 Add command line option to ignore fact cache Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-348) Facter should provide a convenient way to cache values
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Facter / FACT-348 Facter should provide a convenient way to cache values Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1512) Add command line flags related to fact blocking
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Facter / FACT-1512 Add command line flags related to fact blocking Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3066) Add a tracer message to the AMQ upgrade code
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3066 Add a tracer message to the AMQ upgrade code Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6754) Fix puppet faces to allow uppercase flags
Title: Message Title Lori Landesman commented on PUP-6754 Re: Fix puppet faces to allow uppercase flags Susan McNerney No. This is being done for general consistency across the product, to follow the standard described at https://github.com/puppetlabs/puppet-nogui/blob/master/patterns/command_taxonomy.md Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6754) Fix puppet faces to allow uppercase flags
Title: Message Title Susan McNerney commented on PUP-6754 Re: Fix puppet faces to allow uppercase flags Lori Landesman did this require any more UX input to proceed? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-524) determine strategy for something like eyaml for hocon
Title: Message Title Chris Price updated an issue Hiera / HI-524 determine strategy for something like eyaml for hocon Change By: Chris Price Team: Puppet Developer Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Chris Price Sub-team: emerald Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3054) Externalize user facing strings in the tk-webserver-jetty9 repo
Title: Message Title Chris Price updated an issue PuppetDB / PDB-3054 Externalize user facing strings in the tk-webserver-jetty9 repo Change By: Chris Price Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3055) Externalize user facing strings in the trapperkeeper repo
Title: Message Title Chris Price updated an issue PuppetDB / PDB-3055 Externalize user facing strings in the trapperkeeper repo Change By: Chris Price Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1441) --show_diff causes crashes on files with UTF-8 content
Title: Message Title Kristyna Streitova commented on PUP-1441 Re: --show_diff causes crashes on files with UTF-8 content Hi, we have a customer that encountered PUP-1441 which seems to be now a part of " highest priority issues" within PUP-6718. I would like to ask if you have any ETA for the fix. Is it possible to say now if it's an extensive patch or not? Thank you! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Chris Price updated an issue Puppet / PUP-6698 Puppet server 2.5.0 does not properly handle exported file resources Change By: Chris Price Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Robert Rosengren created an issue Puppet / PUP-6759 systemd provider does not understand "indirect" status / tries to turn off service on each run Issue Type: Bug Affects Versions: PUP 3.8.8 Assignee: Kylo Ginsberg Components: Catalog Application, Types and Providers Created: 2016/09/30 4:37 AM Environment: RedHat 7.X - systemd Labels: systemd provider Priority: Normal Reporter: Robert Rosengren Following occurs with each puppet run, which causes annoyance: Service[rpcbind]/enable: enable changed 'true' to 'false' The rpcbind service returns "indirect" as a status to is-enabled _*/bin/systemctl is-enabled rpcbind indirect*_
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Angel L. Mateo commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources The problem is still present with puppet-agent 1.7.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
