Jira (FACT-2604) virt-what resolver
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2604 virt-what resolver Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357834.1588775263000.64231.1589793600029%40Atlassian.JIRA.
Jira (FACT-2617) Fix for tests/external_facts/external_fact_stderr_messages_output_to_stderr.rb
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2617 Fix for tests/external_facts/external_fact_stderr_messages_output_to_stderr.rb Change By: Bogdan Irimie Summary: Fix for tests/external_facts . / external_fact_stderr_messages_output_to_stderr.rb Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.358946.1589550376000.64216.1589789760052%40Atlassian.JIRA.
Jira (FACT-2617) Fix for tests/external_facts/external_fact_stderr_messages_output_to_stderr.rb
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2617 Fix for tests/external_facts/external_fact_stderr_messages_output_to_stderr.rb Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.358946.1589550376000.64220.1589790300026%40Atlassian.JIRA.
Jira (PDB-4741) Report type AST processor does not allow nil expressions
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4741
Report type AST processor does not allow nil expressions
Change By:
Austin Blatt
We allow nil expressions in extract statements in AST, but the AST processor added for filtering reports by type does not support nil expressions.The following query is generated by the console when querying to a package count when there is no filtering being done on {{package_name}}.{ { code} } ["from" "package_inventory"["extract" ["package_name" "version" "provider" ["function" "count"]] ["and" ["=" ["node" "active"] "true"] ["in" ["package_name" "version" "provider"] ["from""packages"["extract" ["package_name" "version" "provider"] nil]["order_by" ["package_name" "version" "provider"]]["limit" 100]["offset" 0 ["group_by" "package_name" "version" "provider"]]]{ { code} } That query will fail with the message {{Unrecognized ast clause ["in" ["package_name" "version" "provider"] ["from" "packages" ["extract" ["package_name" "version" "provider"] nil]}} because {{nil}} is not one of the allowed _expression_ formats in {{maybe-add-agent-report-filter}}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2618) Incorrect log format on non-executable external fact scripts
Title: Message Title
Garrett Guillotte updated an issue
Facter / FACT-2618
Incorrect log format on non-executable external fact scripts
Change By:
Garrett Guillotte
[~ciprian.badescu] in https://github.com/puppetlabs/facter/commit/76a7bab5c75ff0b1b6a46cc7242582c24adf701d:{quote}Before this change, the log message format is wrong and the following is logged in case external facts file is not proper executable:{code}2020-04-09 15:07:49.499276 ERROR puppetlabs.facter - error while processing "%1%" for external facts: %2%{code}After this fix, the proper message will be logged:{code}2020-04-09 15:10:49.546980 ERROR puppetlabs.facter - error while processing "/opt/puppetlabs/facter/facts.d/a.sh" for external facts: child process returned non-zero exit status (8).{code}{quote}Filing this as a bug ticket and resolving it so we can reference this fix.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (PUP-10420) Observe waitforlock when acquiring the ssl lock
Title: Message Title Melissa Stone commented on PUP-10420 Re: Observe waitforlock when acquiring the ssl lock passed ci with puppet-agent 6.15.0.214.g79310b7c Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.355521.1586889868000.65173.1589841060028%40Atlassian.JIRA.
Jira (PDB-4741) Report type AST processor does not allow nil expressions
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4741 Report type AST processor does not allow nil expressions Issue Type: Bug Assignee: Austin Blatt Created: 2020/05/18 1:32 PM Fix Versions: PDB 6.11.0 Priority: Normal Reporter: Austin Blatt We allow nil expressions in extract statements in AST, but the AST processor added for filtering reports by type does not support nil expressions. The following query is generated by the console when querying to a package count when there is no filtering being done on package_name. code ["from" "package_inventory" ["extract" ["package_name" "version" "provider" ["function" "count"]] ["and" ["=" ["node" "active"] "true"] ["in" ["package_name" "version" "provider"] ["from" "packages" ["extract" ["package_name" "version" "provider"] nil] ["order_by" ["package_name" "version" "provider"]] ["limit" 100] ["offset" 0 ["group_by" "package_name" "version" "provider"]]] code That query will fail with the message Unrecognized ast clause ["in" ["package_name" "version" "provider"] ["from" "packages" ["extract" ["package_name" "version" "provider"] nil] because nil is not one of the allowed _expression_ formats in maybe-add-agent-report-filter Add Comment
Jira (PDB-4741) Report type AST processor does not allow nil expressions
Title: Message Title Austin Blatt commented on PDB-4741 Re: Report type AST processor does not allow nil expressions Also, the new processor does not recognize the "offset" paging option. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359169.1589833973000.65008.1589834940054%40Atlassian.JIRA.
Jira (PUP-5600) Add "none" parameter to catalog_cache_terminus configuration reference
Title: Message Title Charlie Sharpsteen commented on PUP-5600 Re: Add "none" parameter to catalog_cache_terminus configuration reference Josh Cooper PUP-10160 addresses --noop catalog getting unintentionally applied, but doesn't address the need to prevent Sensitive data from being written to disk. It is a bit of an edge case concern, but having the ability to toggle it off can save many hours of meetings and arguments with some auditors. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.109309.1449873923000.64870.1589829660089%40Atlassian.JIRA.
Jira (PUP-5600) Add "none" parameter to catalog_cache_terminus configuration reference
Title: Message Title Josh Cooper commented on PUP-5600 Re: Add "none" parameter to catalog_cache_terminus configuration reference Ah sorry Charlie Sharpsteen I missed your comment. Feel free to reopen if you think it'd be useful. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.109309.1449873923000.64913.1589831940023%40Atlassian.JIRA.
Jira (PUP-10499) Out-of-sync no-op resources should cause dependent resources to skip
Title: Message Title Rob Braden updated an issue Puppet / PUP-10499 Out-of-sync no-op resources should cause dependent resources to skip Change By: Rob Braden Team: Compliance Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.358347.1589223608000.64718.1589824380278%40Atlassian.JIRA.
Jira (PUP-10499) Out-of-sync no-op resources should cause dependent resources to skip
Title: Message Title Rob Braden updated an issue Puppet / PUP-10499 Out-of-sync no-op resources should cause dependent resources to skip Change By: Rob Braden Team: Compliance Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.358347.1589223608000.64717.1589824380235%40Atlassian.JIRA.
Jira (PUP-10499) Out-of-sync no-op resources should cause dependent resources to skip
Title: Message Title Rob Braden updated an issue Puppet / PUP-10499 Out-of-sync no-op resources should cause dependent resources to skip Change By: Rob Braden Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.358347.1589223608000.64716.1589824380191%40Atlassian.JIRA.
Jira (PUP-10500) Puppet settings catalog requires codedir to be a directory
Title: Message Title Molly Waggett commented on PUP-10500 Re: Puppet settings catalog requires codedir to be a directory Now that CODEMGMT-1272 is resolved, I can no longer reproduce this issue. Your analysis seems accurate, Josh Cooper. Closing. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357903.1588789984000.64703.1589824140128%40Atlassian.JIRA.
Jira (PUP-10503) hiera glob files not included in order
Title: Message Title Rob Braden updated an issue Puppet / PUP-10503 hiera glob files not included in order Change By: Rob Braden Team: Froyo Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.358492.158931013.64710.1589824260040%40Atlassian.JIRA.
Jira (PUP-10407) "Unable to set ownership" error with logdest on agents running as root
Title: Message Title Melissa Stone commented on PUP-10407 Re: "Unable to set ownership" error with logdest on agents running as root merged into 5.5.x with https://github.com/puppetlabs/puppet/commit/f884c251f98deb28da7c61b83e7bf80e16d2e046 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.353908.1585812512000.64658.1589822460127%40Atlassian.JIRA.
Jira (PUP-10491) Allow adding descriptive or administrative information to resources
Title: Message Title Rob Braden updated an issue Puppet / PUP-10491 Allow adding descriptive or administrative information to resources Change By: Rob Braden Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357687.1588699805000.64719.1589824440037%40Atlassian.JIRA.
Jira (PUP-10289) Route HttpPool.connection through http client
Title: Message Title Melissa Stone commented on PUP-10289 Re: Route HttpPool.connection through http client merged into master at https://github.com/puppetlabs/puppet/commit/6e15b158bc3cfc9c094bebb79d302f54b4593fd2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.345755.1581357737000.64586.1589819820035%40Atlassian.JIRA.
Jira (PUP-5600) Add "none" parameter to catalog_cache_terminus configuration reference
Title: Message Title Josh Cooper commented on PUP-5600 Re: Add "none" parameter to catalog_cache_terminus configuration reference This is no longer necessary because the agent doesn't update its cached catalog when running in noop mode, see PUP-10160. I'm going to close this ticket. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.109309.1449873923000.64693.1589823780029%40Atlassian.JIRA.
Jira (PDB-4738) Bump versions, push directly, and tag (PuppetDB 6.11.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4738 Bump versions, push directly, and tag (PuppetDB 6.11.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/05/18 7:57 AM Due Date: 2020/05/22 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Check that puppetdb and pe-puppetdb-extensions are on the same version of clj-parent, and that is the same clj-parent version that puppetserver will release with. Disable automatic promotions: If a PE release branch has not been cut, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing.
Jira (PDB-4736) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.11.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4736 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.11.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/05/18 7:57 AM Due Date: 2020/05/19 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) Ensure all tickets referenced in the commit log have a the release's fixVersion, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by checking out the branches you will be releasing, ensuring they are in sync with the upstream puppetlabs repo and running the rake task bundle install; bundle exec rake release:reconcile[NEXT_VER,LAST_VER] This assumes you have the puppetdb repo as the cwd and the pe repo at ../pe-puppetdb-extensions. These can be overridden by the PDB_PATH and PDB_PE_PATH environment variables. The rake task will explain any mismatches that exist between Jira and the repos and ask you to investigate any tickets that do not start with a PDB ticket, (maint), (docs), or (i18n) Add Comment
Jira (PDB-4739) Check builds, promote to PE (PuppetDB 6.11.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4739 Check builds, promote to PE (PuppetDB 6.11.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359092.1589813857000.64348.1589813880967%40Atlassian.JIRA.
Jira (PDB-4735) Merge-up, branch, and create pipelines (PuppetDB 6.11.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4735 Merge-up, branch, and create pipelines (PuppetDB 6.11.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359088.1589813844000.64340.1589813880615%40Atlassian.JIRA.
Jira (PDB-4735) Merge-up, branch, and create pipelines (PuppetDB 6.11.0)
Title: Message Title
Eric Griswold created an issue
PuppetDB / PDB-4735
Merge-up, branch, and create pipelines (PuppetDB 6.11.0)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2020/05/18 7:57 AM
Due Date:
2020/05/19
Priority:
Normal
Reporter:
Eric Griswold
(Initial planned release date: 2020-05-27) 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.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> master
Important: Do this for both the core puppetdb repo and the pe-puppetdb-extensions repo! These should be submitted as PRs and merged after tests pass, if there's anything remotely interesting about the merges. If the merges are boring, then direct push is fine. Then, prepare the branch for release:
Jira (PDB-4736) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.11.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4736 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.11.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359089.1589813848000.64342.1589813880703%40Atlassian.JIRA.
Jira (PUP-10520) Publish documentation and updates and release notes (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10520 Publish documentation and updates and release notes (Puppet Platform 6.16.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359067.1589813768000.64324.1589813820383%40Atlassian.JIRA.
Jira (PUP-10521) Send release announcement (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10521 Send release announcement (Puppet Platform 6.16.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359069.1589813775000.64326.1589813820474%40Atlassian.JIRA.
Jira (PUP-10523) Communicate scope and timeline of next release (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10523 Communicate scope and timeline of next release (Puppet Platform 6.16.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/05/18 7:56 AM Due Date: 2020/05/28 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) 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-10518) Prepare release announcement (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10518 Prepare release announcement (Puppet Platform 6.16.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359064.1589813759000.64320.1589813820208%40Atlassian.JIRA.
Jira (PUP-10519) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10519 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.16.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359066.1589813765000.64322.1589813820295%40Atlassian.JIRA.
Jira (PUP-10522) Update Confluence and JIRA based on release (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10522 Update Confluence and JIRA based on release (Puppet Platform 6.16.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359070.1589813778000.64328.1589813820563%40Atlassian.JIRA.
Jira (PUP-10523) Communicate scope and timeline of next release (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10523 Communicate scope and timeline of next release (Puppet Platform 6.16.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359071.1589813781000.64330.1589813820651%40Atlassian.JIRA.
Jira (PUP-10520) Publish documentation and updates and release notes (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10520 Publish documentation and updates and release notes (Puppet Platform 6.16.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/05/18 7:56 AM Due Date: 2020/05/27 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-10521) Send release announcement (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10521 Send release announcement (Puppet Platform 6.16.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2020/05/18 7:56 AM Due Date: 2020/05/27 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.16.0 is now available".
Jira (PUP-10519) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10519 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.16.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/05/18 7:56 AM Due Date: 2020/05/26 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) 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 #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-10522) Update Confluence and JIRA based on release (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10522 Update Confluence and JIRA based on release (Puppet Platform 6.16.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/05/18 7:56 AM Due Date: 2020/05/28 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) 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
Jira (PUP-10514) Puppet Platform 6.16.0 Release - 2020-05-27
Title: Message Title Eric Griswold created an issue Puppet / PUP-10514 Puppet Platform 6.16.0 Release - 2020-05-27 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/05/18 7:55 AM Due Date: 2020/05/27 Priority: Normal Reporter: Eric Griswold Puppet Platform 6.16.0 Release - 2020-05-27 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10516) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10516 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.16.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/05/18 7:55 AM Due Date: 2020/05/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) 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 Slack) 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-10515) Prepare JIRA and Confluence for release (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10515 Prepare JIRA and Confluence for release (Puppet Platform 6.16.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/05/18 7:55 AM Due Date: 2020/05/20 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) 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) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) 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. 4) 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. 5) Update the “master” filters for Puppet Platform 6.16.0 and puppet-agent 6.16.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-10517) Prepare documentation updates and release notes (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10517 Prepare documentation updates and release notes (Puppet Platform 6.16.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/05/18 7:55 AM Due Date: 2020/05/22 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-10516) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10516 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.16.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359062.1589813753000.64315.1589813760315%40Atlassian.JIRA.
Jira (PUP-10517) Prepare documentation updates and release notes (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10517 Prepare documentation updates and release notes (Puppet Platform 6.16.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359063.1589813756000.64317.1589813760403%40Atlassian.JIRA.
Jira (PUP-10518) Prepare release announcement (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-10518 Prepare release announcement (Puppet Platform 6.16.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/05/18 7:55 AM Due Date: 2020/05/26 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Claire Cadman for review and any important hyperlinks. 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-10515) Prepare JIRA and Confluence for release (Puppet Platform 6.16.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-10515 Prepare JIRA and Confluence for release (Puppet Platform 6.16.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359061.158981375.64313.1589813760227%40Atlassian.JIRA.
Jira (BOLT-1549) Puppet data types not synced to target nodes
Title: Message Title Bert Hajee created an issue Puppet Task Runner / BOLT-1549 Puppet data types not synced to target nodes Issue Type: Bug Affects Versions: BOLT 1.29.0 Assignee: Unassigned Created: 2020/05/18 8:33 AM Priority: Normal Reporter: Bert Hajee In https://github.com/puppetlabs/bolt/blob/master/lib/bolt/applicator.rb#L33-L37 the files are marked that are required for running an apply on a target node. Right now it doesn't contain the puppet data types defined in the directory types with extension .pp. As a result of that puppet code that requires these puppet data types not only for catalog compilation but also for run time type checking, cannot run in a bolt apply block. This is related to https://tickets.puppetlabs.com/browse/PUP-7197. However, this is more harmful. We have installed the the [oci_config|https://forge.puppet.com/enterprisemodules/oci_config] on a puppetserver to let this puppetserver work like a gateway between the puppet world and the Oracle Cloud. Many of the custom types available in this module rely on Puppet data types. It works great when you run an apply on the local puppetserver. But when we want to use the power of Bolt with it, we run into this issue: /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/puppet-resource_api-1.8.13/lib/puppet/resource_api/data_type_handling.rb:49:in `mungify_core': Parameter source_details failed on Oci_core_volume[blockvolumecloning (root)/ohisc/TRUSTON/BV_TRO9_BO]: oci_core_volume.source_details references an unresolved type 'Oci_config::VolumeSourceDetails' (file: /etc/puppetlabs/code/environments/block_volume_copying/modules/profile/plans/afterclone/clone_volume.pp, line: 38) (Puppet::ResourceError) from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/puppet-resource_api-1.8.13/lib/puppet/resource_api/data_type_handling.rb:22:in `mungify' from /tmp/d20200518-22643-zj5onk/modules/easy_type/lib/easy_type/extended_parameter.rb:41:in `coerce' A very simple solution would be to add
Jira (PDB-4739) Check builds, promote to PE (PuppetDB 6.11.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4739 Check builds, promote to PE (PuppetDB 6.11.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/05/18 7:57 AM Due Date: 2020/05/22 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) 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 with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. If a release branch has already been cut Rebuild the pacakge promotion job with the release branch set instead of master or 2018.1.x. Once it's promoted to the release branch checkout the release branch of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb bundle exec rake report:packages If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/].
Jira (PDB-4740) Update winston (PuppetDB 6.11.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4740 Update winston (PuppetDB 6.11.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359094.1589813863000.64350.1589813881055%40Atlassian.JIRA.
Jira (PDB-4737) Draft release notes (PuppetDB 6.11.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4737 Draft release notes (PuppetDB 6.11.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/05/18 7:57 AM Due Date: 2020/05/25 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) Write release notes for the release based on the tickets found in the previous step. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown. Request review from the docs team by pinging @clairecadman in the opened PR, at least one day before Ready to Ship The opened PR should be approved prior to a go\/no-go. Release notes must be ready before a go. Docs are built daily and at release time. If notes need to be published out of band ask in `#prod-docs`.
Jira (PDB-4740) Update winston (PuppetDB 6.11.0)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-4740 Update winston (PuppetDB 6.11.0) Issue Type: Task Assignee: Zachary Kent Created: 2020/05/18 7:57 AM Due Date: 2020/05/28 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2020-05-27) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4738) Bump versions, push directly, and tag (PuppetDB 6.11.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4738 Bump versions, push directly, and tag (PuppetDB 6.11.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359091.1589813854000.64346.1589813880879%40Atlassian.JIRA.
Jira (PDB-4737) Draft release notes (PuppetDB 6.11.0)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-4737 Draft release notes (PuppetDB 6.11.0) Change By: Eric Griswold Epic Link: PUP-10514 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359090.1589813851000.64344.1589813880791%40Atlassian.JIRA.
Jira (FACT-2618) Incorrect log format on non-executable external fact scripts
Title: Message Title Jean Bond commented on FACT-2618 Re: Incorrect log format on non-executable external fact scripts Thanks for the heads up, Garrett Guillotte. Claire Cadman, could you please add this release note for Facter? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359015.158959065.64476.1589815800167%40Atlassian.JIRA.
Jira (PDB-4706) Update report sync query to handle report types
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4706 Update report sync query to handle report types Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356904.1588014416000.65225.1589845860144%40Atlassian.JIRA.
