Jira (PUP-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title Josh Cooper commented on PUP-8493 Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original In Platform 6, we are going to unvendor the old semantic_puppet from puppet, update the bundled version in puppet-agent to the latest 1.x, and allow puppetserver to use that same gem. See PA-1885 for more info. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8537) Validator incorrectly reports result of regexp match as being forgotten
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8537 Validator incorrectly reports result of regexp match as being forgotten Issue Type: Bug Assignee: Unassigned Created: 2018/03/08 11:05 PM Priority: Normal Reporter: Thomas Hallgren The following manifest errors when evaluated using puppet apply: 'cdf' =~ /^([a-z])(.*)/ notice($2) The error is: This '=~' _expression_ has no effect. A value was produced and then forgotten (one or more preceding expressions may have the wrong form) This is not correct since the result of the match is stored in numeric variables $1 ... $n and can be used. Turning the comparison into an assignment, i.e.:
Jira (PUP-3262) By default, the cadir should be separated from the ssldir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3262 By default, the cadir should be separated from the ssldir Change By: Josh Cooper Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3262) By default, the cadir should be separated from the ssldir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3262 By default, the cadir should be separated from the ssldir Change By: Josh Cooper Sub-team: Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7834) Change all calls to YAML.load into YAML.safe_load
Title: Message Title Josh Cooper commented on PUP-7834 Re: Change all calls to YAML.load into YAML.safe_load Now that we have a 6.0 branch (master), I'd prefer to land this PR there instead of 5.y. LGTM. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7834) Change all calls to YAML.load into YAML.safe_load
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7834 Change all calls to YAML.load into YAML.safe_load Change By: Josh Cooper Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6996) Puppet automatically creates the production environment with the incorrect permissions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6996 Puppet automatically creates the production environment with the incorrect permissions Change By: Josh Cooper Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6996) Puppet automatically creates the production environment with the incorrect permissions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6996 Puppet automatically creates the production environment with the incorrect permissions Change By: Josh Cooper Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6996) Puppet automatically creates the production environment with the incorrect permissions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6996 Puppet automatically creates the production environment with the incorrect permissions Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1383) Azure Instance Metadata
Title: Message Title Owen Rodabaugh updated an issue Facter / FACT-1383 Azure Instance Metadata Change By: Owen Rodabaugh CS Priority: Needs Priority Major CS Impact: Users of the Puppet Azure module do not have parity with the Puppet AWS module. They are forced to download a separate forge module to get this functionality. CS Severity: 4 - Major CS Business Value: 5 - $$ CS Frequency: 3 - 25-50% of Customers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-167) I want to pass a pql query instead of a list of nodes.
Title: Message Title Michael Smith commented on BOLT-167 Re: I want to pass a pql query instead of a list of nodes. I think the next step in this concept will be designing a way to add more external sources. So far we've built a script for creating an inventory from PuppetDB, and this ticket has turned into supporting running simple actions (not plans) with a PuppetDB query. In general the inventory approach is more flexible and makes sense for multiple sources. The other idea we've floated for using external queries in a way that can be used with plans is to have a special syntax highlighting a query extension that we then transform into a list of targets, much like we use protocols for transports. We could then support multiple query sources, perhaps as 'pdb(...)', 'aws(...)', etc. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1354) Facter ec2_userdata handles binary data incorrectly
Title: Message Title Travis Fields commented on FACT-1354 Re: Facter ec2_userdata handles binary data incorrectly Any movement on this ticket, it is biting us a bit now. Would prefer to not go down the revert to PSON or fact blocking route. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3834) remove webrick/rack support from Puppet
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-3834 remove webrick/rack support from Puppet Change By: Maggie Dreyer Epic Colour: ghx-label-1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3830) Command Queue Grows Steadily Over Time not related to load
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3830 Command Queue Grows Steadily Over Time not related to load Change By: Rob Browning Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3830) Command Queue Grows Steadily Over Time not related to load
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3830 Command Queue Grows Steadily Over Time not related to load Change By: Rob Browning Release Notes Summary: PuppetDB should now correctly account for incoming commands that cannot be processed in the queue depth metric. Previously they were ignored, which could cause the depth to appear to grow over time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3861) Fix PDB 5.1 and 5.2 rspec tests that started failing a week or two before 2018-03-06
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3861 Fix PDB 5.1 and 5.2 rspec tests that started failing a week or two before 2018-03-06 Change By: Rob Browning Fix Version/s: PDB 5.2.1 Fix Version/s: PDB 5.1.5 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3861) Fix PDB 5.1 and 5.2 rspec tests that started failing a week or two before 2018-03-06
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3861 Fix PDB 5.1 and 5.2 rspec tests that started failing a week or two before 2018-03-06 Change By: Rob Browning Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Eric Sorenson commented on PUP-6964 Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency This needs to get fixed in the 5.5.x series, or no one will be able to reasonably use 4.x functions in modules. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8267) Rewrite acceptance rake tasks to leverage beaker subcommand support
Title: Message Title Josh Cooper commented on PUP-8267 Re: Rewrite acceptance rake tasks to leverage beaker subcommand support Merged into 4.10.x in https://github.com/puppetlabs/puppet/commit/3daae58ffbda36ff94107c8771fddb1d73b23a00 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3872) (maint) Update to ezbake 1.8.1
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3872 (maint) Update to ezbake 1.8.1 Issue Type: Bug Assignee: Unassigned Created: 2018/03/08 3:12 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8486) Warning for undefined variables is slow in jruby
Title: Message Title Patrick Carlisle commented on PUP-8486 Re: Warning for undefined variables is slow in jruby Coming back to this, it looks like it's the calls to lookupvar here that can fail without a catch https://github.com/puppetlabs/puppet/blob/master/lib/hiera/scope.rb#L23-L25 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3871) PE Console fact_x !~ \w+ broken
Title: Message Title Travis Fields updated an issue PuppetDB / PDB-3871 PE Console fact_x !~ \w+ broken Change By: Travis Fields Attachment: Screen Shot 2018-03-08 at 2.27.39 PM.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3871) PE Console fact_x !~ \w+ broken
Title: Message Title Travis Fields commented on PDB-3871 Re: PE Console fact_x !~ \w+ broken The screen shots are from the exact same cluster, minus the Puppet Infrastructure of course. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3871) PE Console fact_x !~ \w+ broken
Title: Message Title Travis Fields updated an issue PuppetDB / PDB-3871 PE Console fact_x !~ \w+ broken Change By: Travis Fields Attachment: Screen Shot 2018-03-08 at 2.25.03 PM.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3871) PE Console fact_x !~ \w+ broken
Title: Message Title Travis Fields created an issue PuppetDB / PDB-3871 PE Console fact_x !~ \w+ broken Issue Type: Bug Assignee: Unassigned Components: PuppetDB Created: 2018/03/08 2:26 PM Environment: RHEL 7 boxes Labels: console pe Priority: Normal Reporter: Travis Fields When using the console to try and filter out items that don't have a value for a given fact or an empty string in previous version 2016.4.3 we were able to simple place into the console ` !~ \w+` and it would return this result, presuming that missing the fact also met this criteria, however with 2017.3.4 this does not seem to be the case. Add Comment
Jira (BOLT-349) Update release automation to tag bolt-vanagon and publish packages
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-349 Update release automation to tag bolt-vanagon and publish packages Change By: Michael Smith Bolt-vanagon currently requires manual version tagging + release to begin building system packages. Depending on the expected release cadence, we'd like to automate tagging + building packages when we release Bolt gem. Depending on when we decide to release packages, this may or may not be automatable. Automate:- Update the component commit to the specified tag.- Tag bolt-vanagon.- Kick off the package pipeline- Once successfully completed, push to GithubThis may be similar to work the Platform OS team has done to automate releases of puppet-agent. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-348) Add automated tests of system packages
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-348 Add automated tests of system packages Change By: Michael Smith We should ideally have some basic testing of built system packages that gets run before releasing them. This could potentially be part of the Orchestrator tests. Tests should cover: * Running bolt command/task/script/file upload * Running bolt plan * Running bolt [task|plan] show We should re-run the same acceptance suite we use (to validate the gem) with packages. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8421) Add error handing to Yum provider
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8421 Add error handing to Yum provider Change By: Jacob Helwig Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8421) Add error handing to Yum provider
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8421 Add error handing to Yum provider Change By: Jacob Helwig Team: Platform OS Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8421) Add error handing to Yum provider
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8421 Add error handing to Yum provider Change By: Jacob Helwig Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3870) Remove elasticsearch support from PDP for now
Title: Message Title Jeff Yarnell assigned an issue to Unassigned PuppetDB / PDB-3870 Remove elasticsearch support from PDP for now Change By: Jeff Yarnell Assignee: Rob Browning Sprint: Data Platform 2018-03-14 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7400) yumrepo provider should support username and password
Title: Message Title Melissa Stone updated an issue Puppet / PUP-7400 yumrepo provider should support username and password Change By: Melissa Stone Release Notes Summary: Yumrepo now supports a username and password field. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7400) yumrepo provider should support username and password
Title: Message Title Eric Delaney commented on PUP-7400 Re: yumrepo provider should support username and password Melissa Stone Can you add release notes? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7400) yumrepo provider should support username and password
Title: Message Title Eric Delaney commented on PUP-7400 Re: yumrepo provider should support username and password Merged to 5.5.x at https://github.com/puppetlabs/puppet/commit/e9d9eb1bc83061adfe3e9cf0f688ad4dc36889ee Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3870) Remove elasticsearch support from PDP for now
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3870 Remove elasticsearch support from PDP for now Change By: Rob Browning Given all the recent churn, the balance has shifted against it being worth the effort to carry this along when it's not being used, as compared to the effort of resurrecting the support later if/when we need it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3870) Remove elasticsearch support from PDP for now
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3870 Remove elasticsearch support from PDP for now Issue Type: Bug Assignee: Rob Browning Created: 2018/03/08 1:28 PM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8534) Remove configtimeout setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8534 Remove configtimeout setting Change By: Josh Cooper Summary: Removed Remove configtimeout setting Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-377) Add the ability to pass secrets file via environment variables
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-377 Add the ability to pass secrets file via environment variables Change By: Michael Smith One of the design criteria for the Discovery Edge service, which operates on the network edges of the customers infrastructure, executing Discovery providers and tasks, is to not persist secrets to disk. The edge fetches secrets over a secure communication layer (HTTP/2+TLS) and keeps them in memory. In order to execute a task using Bolt, one currently has to persist the secret (key file) to disk in order to pass it to Bolt using the --private-key parameter. The request is to enable passing secrets like sensitive configuration, such as keyfile content as well as and passwords etc , via environment variables. only Environment variables have content size limits. On Windows that's 32KiB for the entire environment block, on Linux it's 128KiB for a single value. Our solution should allow passing one a single RSA key (commonly 4KB) to Bolt. integration Integration with secrets store would be nice but out of scope .A proposed solution for this is to allow passing an inventory file as stringified JSON in an environment variable. The inventory file config section allows setting passwords, and would need to be extended to support including key file contents. Open question: do we need to support combining the inventory file in an environment variable and as a file. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-8536) If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment
Title: Message Title Henrik Lindberg commented on PUP-8536 Re: If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment As per the current specification of puppet this is not an error as it is allowed to have code that contributes to the top scope in autoloaded code. (We have tests that ensures that it is possible to open and append code). We have various tickets covering handling of these issues. One is for not allowing any code outside of the expected loaded entity when autoloading (this is enforced for newer constructs such as the 4.x functions). For init.pp this is tricky since there it is expected that a module may stick code that gets evaluated outside of the scope of the module's main class. Because of this, there is a long fuse to getting this changed with a deprecation cycle and wait for a major release and naturally also getting a fix for this problem prioritized high enough to make it all the way. Meanwhile, using puppet-lint and having it check for code outside classes is highly recommended. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8536) If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-8536 If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment Change By: Paul Schaffer Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8536) If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment
Title: Message Title Paul Schaffer updated an issue Puppet / PUP-8536 If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment Change By: Paul Schaffer Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6747) yum_repo required quoted true/false values
Title: Message Title Eric Delaney commented on PUP-6747 Re: yum_repo required quoted true/false values Even on puppet version 4.3.2, I can't reproduce the exact problem that was reported. What I did find is that there was a problem with setting a value to false PUP-5682 which was fixed in 4.4.0, which I find was the original problem. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6747) yum_repo required quoted true/false values
Title: Message Title Eric Delaney updated an issue Puppet / PUP-6747 yum_repo required quoted true/false values Change By: Eric Delaney Fix Version/s: PUP 5.3.1 Fix Version/s: PUP 4.10.5 Fix Version/s: PUP 4.10.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8536) If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment
Title: Message Title
Paul Schaffer created an issue
Puppet / PUP-8536
If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment
Issue Type:
Improvement
Affects Versions:
PUP 5.3.3
Assignee:
Unassigned
Created:
2018/03/08 11:38 AM
Priority:
Normal
Reporter:
Paul Schaffer
Puppet Version: 5.3.3 Puppet Server Version: 2017.3.2 If a module's class is prematurely closed in code, it will apply the remaining code to every node in an environment. To reproduce the issue: Create a module called testmod, and set testmod's init.pp to the following:
class testmod {
notify { 'hello_world':
message => 'I am supposed to be here.'
}
}
Jira (PUP-8535) Backport ruby warning rake task
Title: Message Title Josh Cooper created an issue Puppet / PUP-8535 Backport ruby warning rake task Issue Type: Task Assignee: Unassigned Created: 2018/03/08 11:19 AM Fix Versions: PUP 5.3.x Priority: Normal Reporter: Josh Cooper We added a rake task to check for ruby warnings in puppet#master, but it doesn't catch issues that are merged into older branches and then merged up to master. It would be better to catch the issues at PR time. This ticket is to backport the warnings rake task and update the travis CI matrix to execute the new check. Add Comment
Jira (PUP-7307) Tidy should support 'purge' or update file resource
Title: Message Title Justin commented on PUP-7307 Re: Tidy should support 'purge' or update file resource Thanks for the fix Johnson Earls! To the puppet team - will the documentation also be updated via this ticket or should I open a new ticket? Currently the tidy documentation does not state that it only works for unmanaged files. So I was expecting a 'purge' attribute or something similar to how the file resource works. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8505) re-enable server required tests to run in the agent pipeline
Title: Message Title Josh Cooper commented on PUP-8505 Re: re-enable server required tests to run in the agent pipeline Merged to 5.3.x in https://github.com/puppetlabs/puppet/commit/61c382735d75df460c8d2e22817bcafec255e5bd Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8505) re-enable server required tests to run in the agent pipeline
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8505 re-enable server required tests to run in the agent pipeline Change By: Josh Cooper Fix Version/s: PUP 5.3.z Fix Version/s: PUP 5.5.0 Fix Version/s: PUP 5.3.6 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7307) Tidy should support 'purge' or update file resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7307) Tidy should support 'purge' or update file resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: Josh Cooper Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7307) Tidy should support 'purge' or update file resource
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: Josh Cooper Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7307) Tidy should support 'purge' or update file resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: Josh Cooper Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-371) Docs for installing Bolt from packages
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-371 Docs for installing Bolt from packages Change By: Michael Smith Fix Version/s: Bolt Next Fix Version/s: BOLT 0.17.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8519 Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG Change By: Henrik Lindberg Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8519 Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG Change By: Henrik Lindberg Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8494) Issue based errors are formatted too early and arguments are lost.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8494 Issue based errors are formatted too early and arguments are lost. Change By: Henrik Lindberg Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8494) Issue based errors are formatted too early and arguments are lost.
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8494 Issue based errors are formatted too early and arguments are lost. Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3600) Create support for binary content on the File type
Title: Message Title Matthew Gyurgyik commented on PUP-3600 Re: Create support for binary content on the File type Henrik Lindberg yes, exactly what I meant. The file get created, but its content contains the base64 text. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7400) yumrepo provider should support username and password
Title: Message Title Melissa Stone assigned an issue to Unassigned Puppet / PUP-7400 yumrepo provider should support username and password Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3600) Create support for binary content on the File type
Title: Message Title Henrik Lindberg commented on PUP-3600 Re: Create support for binary content on the File type This once worked but that there are no acceptance tests that detected the regression. We have since made a number of changes to safe serialization and data and special handling of a Binary instance got lost as those changes took place. The right path forward is for us to make sure that --rich_data works as it should in the agent-master scenario. Now it should work using a puppet apply. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3600) Create support for binary content on the File type
Title: Message Title Henrik Lindberg commented on PUP-3600 Re: Create support for binary content on the File type Matthew Gyurgyik Do you mean you get the Base64 text in the file? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8534) Removed configtimeout setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-8534 Removed configtimeout setting Issue Type: Task Assignee: Unassigned Created: 2018/03/08 9:26 AM Priority: Normal Reporter: Josh Cooper The configtimeout setting is deprecated has been superseded by http_connect_timeout and http_read_timeout. It should be removed in 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8533) Remove dead ignorecache setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-8533 Remove dead ignorecache setting Issue Type: Task Assignee: Unassigned Created: 2018/03/08 9:25 AM Priority: Normal Reporter: Josh Cooper The ignorecache setting is deprecated and does nothing. Remove in 6 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8532) Remove pluginsync setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-8532 Remove pluginsync setting Issue Type: Task Assignee: Unassigned Created: 2018/03/08 9:24 AM Priority: Normal Reporter: Josh Cooper The agent's pluginsync behavior is controlled based on whether it is using a cached catalog or not. The pluginsync setting is deprecated, and should be removed in 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8531) Remove app_management setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-8531 Remove app_management setting Issue Type: Task Assignee: Unassigned Created: 2018/03/08 9:22 AM Priority: Normal Reporter: Josh Cooper The app_management setting is already deprecated and is always on. Remove it in 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8530) Remove trusted_server_facts setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-8530 Remove trusted_server_facts setting Issue Type: Task Assignee: Unassigned Created: 2018/03/08 9:21 AM Priority: Normal Reporter: Josh Cooper The trusted_server_facts setting is already deprecated and does nothing (since trusted facts are always enabled). The setting should be removed in 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8529) Remove data_binding_terminus setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8529 Remove data_binding_terminus setting Change By: Josh Cooper The data_binding_terminus setting is and environment_data_provider settings are already deprecated and should be removed now that Hiera 5 is done. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8529) Remove data_binding_terminus setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-8529 Remove data_binding_terminus setting Issue Type: Bug Assignee: Unassigned Created: 2018/03/08 9:19 AM Priority: Normal Reporter: Josh Cooper The data_binding_terminus setting is already deprecated and should be removed now that Hiera 5 is done. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8528) Remove WriteOnlyYaml node terminus
Title: Message Title Josh Cooper created an issue Puppet / PUP-8528 Remove WriteOnlyYaml node terminus Issue Type: Bug Assignee: Unassigned Created: 2018/03/08 9:17 AM Priority: Normal Reporter: Josh Cooper The WriteOnlyYaml node terminus was deprecated in 4.10.5 in commit f0890af6656de0fc16c85230f0596644e9ebcd29. It should be removed in 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-377) Add the ability to pass secrets file via environment variables
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-377 Add the ability to pass secrets file via environment variables Issue Type: New Feature Assignee: Unassigned Created: 2018/03/08 9:12 AM Priority: Normal Reporter: Yasmin Rajabi One of the design criteria for the Discovery Edge service, which operates on the network edges of the customers infrastructure, executing Discovery providers and tasks, is to not persist secrets to disk. The edge fetches secrets over a secure communication layer (HTTP/2+TLS) and keeps them in memory. In order to execute a task using Bolt, one currently has to persist the secret (key file) to disk in order to pass it to Bolt using the --private-key parameter. The request is to enable passing secrets like keyfile content as well as passwords etc, via environment variables. only passing one key integration with secrets store would be nice but out of scope Add Comment
Jira (BOLT-376) Add CSR attribute management tasks to the bootstrap tasks module
Title: Message Title Adam Buxton commented on BOLT-376 Re: Add CSR attribute management tasks to the bootstrap tasks module i've started this here https://github.com/abuxton/puppetlabs-bootstrap/tree/bolt-376 hopefully, i can follow up. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8267) Rewrite acceptance rake tasks to leverage beaker subcommand support
Title: Message Title Josh Cooper commented on PUP-8267 Re: Rewrite acceptance rake tasks to leverage beaker subcommand support Reverted again in 9bba755b74 due to BKR-1430 which breaks CI for Japanese Windows due to % in the file path. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8519 Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG Change By: Henrik Lindberg Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8519 Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG Change By: Henrik Lindberg Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8459) ENC acceptance tests didn't catch regression
Title: Message Title Josh Cooper commented on PUP-8459 Re: ENC acceptance tests didn't catch regression Merged to 5.3.x in https://github.com/puppetlabs/puppet/commit/5402e846a6a63fb606e4e9965e3c7902627ebf5b Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-376) Add CSR attribute management tasks to the bootstrap tasks module
Title: Message Title Adam Buxton updated an issue Puppet Task Runner / BOLT-376 Add CSR attribute management tasks to the bootstrap tasks module Change By: Adam Buxton The Puppet bootstrap task does not provide a function for csr set up, each csr prioritising the pp_role csr attribute should be available as a task to generate the csr we could then wrap these tasks in a plan to generate a new SSL with csr attributes. we could simply implement an abstraction of the example [https://puppet.com/docs/puppet/5.3/ssl_attributes_extensions.html#aws-attributes-and-extensions-population-example] with the curl request added. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Henrik Lindberg commented on PUP-6964 Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency I pulled this from the PUP 5.5.0 release as we are not quite there yet with the implementation as there are concerns about performance that we can only speculate about. Seems a bit risky to merge based on speculation alone. We are also still debating what the a more optimal solution would be - if the individual caches per module are positive (trading memory for speed) or if they are negative (takes both memory and unnecessary cycles). We may also have to look at 3.x function loading since the current behavior is try 4.x load first, if that fails try 3.x. That happens on every call to a 3.x function (with the 4.x lookup being optimized/cached). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Change By: Henrik Lindberg Fix Version/s: PUP 5.5.0 Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8521) Prepare JIRA for release (Puppet Platform 5.5.0)
Title: Message Title Kenn Hussey commented on PUP-8521 Re: Prepare JIRA for release (Puppet Platform 5.5.0) Fixed in puppet-agent 5.5.0 https://tickets.puppetlabs.com/issues/?filter=31510 Introduced in puppet-agent 5.5.0 https://tickets.puppetlabs.com/issues/?filter=31511 Fixed in Puppet Platform 5.5.0 https://tickets.puppetlabs.com/issues/?filter=31512 Introduced in Puppet Platform 5.5.0 https://tickets.puppetlabs.com/issues/?filter=31513 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3852) PuppetDB query nodes based on fact broken
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3852 PuppetDB query nodes based on fact broken Change By: Kenn Hussey Fix Version/s: PDB 5.2.z Fix Version/s: PDB 5.2.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3856 PQL specifying both type and title for class makes pql not find existing class Change By: Kenn Hussey Fix Version/s: PDB 5.2.z Fix Version/s: PDB 5.2.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8520) Puppet Platform 5.5.0 Release - 2018-03-20
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8520 Puppet Platform 5.5.0 Release - 2018-03-20 Change By: Kenn Hussey Team/s: Data Platform,Platform Core,Platform OS,Release Engineering Summary: Puppet Platform 5.5.0 Release - 2018-03-20 Epic Name: Puppet Platform 5.5.0 Release - 2018-03-20 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8527) hiera5 cannot merge arrays from hiera3_backend
Title: Message Title
Massimiliano Adamo updated an issue
Puppet / PUP-8527
hiera5 cannot merge arrays from hiera3_backend
Change By:
Massimiliano Adamo
*Puppet Version: 5.4.0* *Puppet Server Version: 5.2.0* *OS Name/Version: CentOS 7.3*Array merge in Hiera 5, using a hiera3_backend always throws the error: Could not run: Hiera type mismatch: expected Hash and got ArrayIn my case I use Redis hiera3_backend.I add an Array to Redis as following: { { quote} massimiliano = ['I_am_from_Redis'] {quote } } I add an Array to Yaml: { { quote} massimiliano: - 'I_am_from_Yaml' {quote } } and I run: { { quote} puppet lookup --merge deep --explain --node test-filesender.example.org massimiliano {quote } } *Desired Behavior:*get a merged array: { { quote} Merged result: [ }} {{ "I_am_from_Redis", }} {{ "I_am_from_Yaml" }} {{ ] {quote } } *Actual Behavior:* { { quote} puppet lookup --merge deep --explain --node test-filesender.example.org massimiliano }} {{ Error: Could not run: Hiera type mismatch: expected Hash and got Array {quote } } This is caused by _resolution_type_ currently not in use with hiera 5: { { quote} def lookup(key, scope, order_override, resolution_type) {quote } } Since it's not in use with Hiera5, it use Hash as default and I expect this issue to happen with every hiera3_backend. *Workaround:*Determine the key_type on the fly: {quote} key_type = key.class {quote} and then: { { quote} case key_type }} {{ when :Array }} {{ raise Exception, "Hiera type mismatch: expected Array and got #\{new_answer.class}" unless new_answer.is_a? Array or new_answer.is_a? String }} {{ answer ||= [] }} {{ answer = answer.concat(new_answer).uniq }} {{ {quote } }
Add Comment
Jira (PUP-8527) hiera5 cannot merge arrays from hiera3_backend
Title: Message Title
Massimiliano Adamo updated an issue
Puppet / PUP-8527
hiera5 cannot merge arrays from hiera3_backend
Change By:
Massimiliano Adamo
Summary:
{brief summary of issue} hiera5 cannot merge arrays from hiera3_backend
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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-8527) {brief summary of issue}
Title: Message Title
Massimiliano Adamo updated an issue
Puppet / PUP-8527
{brief summary of issue}
Change By:
Massimiliano Adamo
Attachment:
error.txt
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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-8527) {brief summary of issue}
Title: Message Title
Massimiliano Adamo updated an issue
Puppet / PUP-8527
{brief summary of issue}
Change By:
Massimiliano Adamo
Attachment:
error.txt
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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-8527) {brief summary of issue}
Title: Message Title
Massimiliano Adamo updated an issue
Puppet / PUP-8527
{brief summary of issue}
Change By:
Massimiliano Adamo
Attachment:
lookup_with_trace.txt
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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-8527) {brief summary of issue}
Title: Message Title
Massimiliano Adamo created an issue
Puppet / PUP-8527
{brief summary of issue}
Issue Type:
Bug
Affects Versions:
PUP 5.4.0
Assignee:
Thomas Hallgren
Components:
Hiera & Lookup
Created:
2018/03/08 6:27 AM
Priority:
Normal
Reporter:
Massimiliano Adamo
Puppet Version: 5.4.0 Puppet Server Version: 5.2.0 OS Name/Version: CentOS 7.3 Array merge in Hiera 5, using a hiera3_backend always throws the error: Could not run: Hiera type mismatch: expected Hash and got Array In my case I use Redis hiera3_backend. I add an Array to Redis as following: massimiliano = ['I_am_from_Redis'] I add an Array to Yaml: {{massimiliano: - 'I_am_from_Yaml'}} and I run: {{puppet lookup --merge deep --explain --node test-filesender.example.org massimiliano }} Desired Behavior: get a merged array: {{ Merged result: [}} "I_am_from_Redis", "I_am_from_Yaml" {{ ]}} Actual Behavior: puppet lookup --merge deep --explain --node test-filesender.example.org massimiliano Error: Could not run: Hiera type mismatch: expected Hash and got Array This is caused by resolution_type currently not in use with hiera 5: def lookup(key, scope, order_override, resolution_type) Since it's not in use with Hiera5, it use Hash as default and I expect this issue to happen with every hiera3_backend. Workaround: Determine the key_type on the fly: key_type = key.class and then: {{ case key_type}} when :Array raise Exception, "Hiera type mismatch: expected Array and got #{new_answer.class}" unless new_answer.is_a? Array or new_answer.is_a? String answer ||= [] answer = answer.concat(new_answer).uniq
Jira (PDB-3866) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.1)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3866 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.1) Issue Type: Task Assignee: Russell Mull Created: 2018/03/08 6:26 AM Due Date: 2018/03/13 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment
Jira (PDB-3865) Merge-up, branch, and create pipelines (PuppetDB 5.2.1)
Title: Message Title
Kenn Hussey created an issue
PuppetDB / PDB-3865
Merge-up, branch, and create pipelines (PuppetDB 5.2.1)
Issue Type:
Task
Assignee:
Russell Mull
Created:
2018/03/08 6:26 AM
Due Date:
2018/03/13
Priority:
Normal
Reporter:
Kenn Hussey
(Initial planned release date: 2018-03-20) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
5.1.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.1.x/
4.4.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/4.4.x/
4.2.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/4.2.3.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Jira (PDB-3869) Update winston (PuppetDB 5.2.1)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3869 Update winston (PuppetDB 5.2.1) Issue Type: Task Assignee: Russell Mull Created: 2018/03/08 6:26 AM Due Date: 2018/03/21 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3868) Check builds, promote to PE (PuppetDB 5.2.1)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3868 Check builds, promote to PE (PuppetDB 5.2.1) Issue Type: Task Assignee: Russell Mull Created: 2018/03/08 6:26 AM Due Date: 2018/03/17 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job. Adding a new tab to Jenkins: If needed hit the + tab in the link above, select "list view", and add the following rule to the regex section that matches the build you're preparing. Example: (?!experimental).*puppetdb.*5.2.x
Jira (PDB-3867) Bump versions, push directly, and tag (PuppetDB 5.2.1)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3867 Bump versions, push directly, and tag (PuppetDB 5.2.1) Issue Type: Task Assignee: Russell Mull Created: 2018/03/08 6:26 AM Due Date: 2018/03/16 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) (if you're making the first release off a new branch you may already have done some of this) Remove the -SNASPHOT portion of the verison in project.clj in both puppetdb and pe-puppetdb-extensions. Push each repo directly to the branch you're releasing (making a PR will break things horribly) Go into the 'release-new' hipchat room to make yourself some tags ! tag puppetdb at with ! tag pe-puppetdb-extensions at with
Jira (PUP-8524) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8524 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/03/08 6:24 AM Due Date: 2018/03/19 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-8525) Update Confluence and JIRA based on release (Puppet Platform 5.5.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8525 Update Confluence and JIRA based on release (Puppet Platform 5.5.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/03/08 6:24 AM Due Date: 2018/03/21 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description
Jira (PUP-8523) Prepare release announcement (Puppet Platform 5.5.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8523 Prepare release announcement (Puppet Platform 5.5.0) Issue Type: Task Assignee: Garrett Guillotte Created: 2018/03/08 6:24 AM Due Date: 2018/03/19 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) Please paste the text of the announcement in the 'Send announcement' ticket. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-8526) Communicate scope and timeline of next release (Puppet Platform 5.5.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8526 Communicate scope and timeline of next release (Puppet Platform 5.5.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/03/08 6:24 AM Due Date: 2018/03/21 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-8521) Prepare JIRA for release (Puppet Platform 5.5.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8521 Prepare JIRA for release (Puppet Platform 5.5.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/03/08 6:24 AM Due Date: 2018/03/14 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 3) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 4) Update the “master” filters for Puppet Platform 5.5.0 and puppet-agent 5.5.0 to reference the “Fixed in” filters created above. 5) Update the community feedback filter for Puppet Platform X.y to reference the “Introduced in” filter created above.
Jira (PUP-8522) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8522 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/03/08 6:24 AM Due Date: 2018/03/14 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-03-20) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-8520) Puppet Platform 5.5.0 Release - 2018-03-20
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8520 Puppet Platform 5.5.0 Release - 2018-03-20 Issue Type: Epic Assignee: Kenn Hussey Created: 2018/03/08 6:24 AM Due Date: 2018/03/20 Priority: Normal Reporter: Kenn Hussey Puppet Platform 5.5.0 Release - 2018-03-20 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
