Jira (PUP-6704) Handle return type added in PUP-5623
Title: Message Title Josh Cooper commented on PUP-6704 Re: Handle return type added in PUP-5623 puppet strings supports return_type, see the most recent change in PDOC-229 so I'm going to close this as a dup. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.151947.1473896817000.54367.1623390840034%40Atlassian.JIRA.
Jira (PUP-6634) environment.conf should use standard syntax for POSIX and Windows
Title: Message Title Josh Cooper commented on PUP-6634 Re: environment.conf should use standard syntax for POSIX and Windows The most common case is to use colon, which works as expected on POSIX. Would could accept colon (in addition to semicolon) when running on Windows. Colons could cause confusion for things like foo:bar as o:bar is the path bar relative to the current directory on drive o. Supporting semicolons (and colon) on POSIX seems pretty easy, we'd just need to split the modulepath on either [:;]. See Puppet::Node::Environment.split_path. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.147623.1471448915000.54366.1623390300041%40Atlassian.JIRA.
Jira (PUP-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-6575 Disambiguate puppet agent -t and puppet apply -t with quick feedback Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.144896.1470248733000.54362.1623389460082%40Atlassian.JIRA.
Jira (PUP-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback
Title: Message Title Josh Cooper commented on PUP-6575 Re: Disambiguate puppet agent -t and puppet apply -t with quick feedback I think this might be useful, but we don't have any plans on working on it. I'm going to close this due to lack of activity. Please reopen if needed. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.144896.1470248733000.54361.1623389460035%40Atlassian.JIRA.
Jira (PUP-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-6575 Disambiguate puppet agent -t and puppet apply -t with quick feedback Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.144896.1470248733000.54360.1623389400052%40Atlassian.JIRA.
Jira (PUP-5801) exec resource may lose return code if command terminated
Title: Message Title Josh Cooper commented on PUP-5801 Re: exec resource may lose return code if command terminated This issue hasn't seen any activity in a long time, and this situation seems fairly uncommon. I'm going to close for now. Please reopen if it is still an issue. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.114824.1454414198000.54358.1623387900023%40Atlassian.JIRA.
Jira (PUP-4884) PMT won't install a module on windows if module_working_dir contains backslashes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4884 PMT won't install a module on windows if module_working_dir contains backslashes Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.89342.1436984308000.54354.1623387240210%40Atlassian.JIRA.
Jira (PUP-4884) PMT won't install a module on windows if module_working_dir contains backslashes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4884 PMT won't install a module on windows if module_working_dir contains backslashes Change By: Josh Cooper Team: Puppet Developer Experience Coremunity Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.89342.1436984308000.54353.1623387240188%40Atlassian.JIRA.
Jira (PUP-4369) generate() harmful in some circumstances, docs do not make this clear
Title: Message Title Josh Cooper commented on PUP-4369 Re: generate() harmful in some circumstances, docs do not make this clear In PUP-6949, it was suggested to have the function accept a lambda, and have stdout, stderr and exit code passed to it (more like popen). That's probably the ideal solution, while not combining stdout and stderr is a good start. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.74355.142793314.54349.1623381420043%40Atlassian.JIRA.
Jira (PUP-4369) generate() harmful in some circumstances, docs do not make this clear
Title: Message Title
Josh Cooper commented on PUP-4369
Re: generate() harmful in some circumstances, docs do not make this clear
The generate function unfortunately doesn't pass combine: false when calling Puppet::Util::Execution.execute, so stdout & stderr are combined and can lead to surprises:
❯ cat -p generator.sh
#!/bin/sh
>&2 echo "error"
echo "success"
exit 0
❯ bx puppet apply -e "notice(generate('/home/josh/work/puppet/generator.sh'))"
Notice: Scope(Class[main]): error
success
Notice: Compiled catalog for ...
I can't think of any reason why someone might be relying on stdout and stderr to be combined, so the fix may be as simple as passing combine: false...
Jira (PUP-4337) OpenBSD package provider does not correctly fail for packages that don't exist
Title: Message Title Josh Cooper commented on PUP-4337 Re: OpenBSD package provider does not correctly fail for packages that don't exist It sounds like this issue was fixed upstream, so as long as pkg_add returns non-zero if the package doesn't exist, then puppet will do the right thing in https://github.com/puppetlabs/puppet/blob/2f14ddd269c26cba36771d9b3464c2c29422e46a/lib/puppet/provider/package/openbsd.rb#L167-L172. Since this hasn't been updated in a long time, I'm going to close this, but please reopen if it is still an issue. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.73789.1427634897000.54254.1623367620022%40Atlassian.JIRA.
Jira (PUP-3496) Ability to set default provider or require `provider` to be set
Title: Message Title Josh Cooper commented on PUP-3496 Re: Ability to set default provider or require `provider` to be set One way to implement 'always default' is to confine based on a fact and pass a regex as the value: defaultfor :osfamily => /.*/ The above is a bit of a hack. I can imagine having a DSL method something like always_defaultfor that causes default_match to always return true. Also as an aside, we added the ability to specify notdefaultfor. Several service providers take advantage of that since the default provider changes based on OS version, eg upstart vs systemd. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.55789.1413919002000.54231.1623367080094%40Atlassian.JIRA.
Jira (PUP-3399) The file resource should autorequire any 'source' items that are on the local system.
Title: Message Title Josh Cooper commented on PUP-3399 Re: The file resource should autorequire any 'source' items that are on the local system. It looks like Adrien meant to close this, doing that now. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.53831.1412705455000.54219.1623366540174%40Atlassian.JIRA.
Jira (PUP-2358) "puppet apply" throws SELinux errors if $HOME is mounted via NFS
Title: Message Title Josh Cooper commented on PUP-2358 Re: "puppet apply" throws SELinux errors if $HOME is mounted via NFS This is most likely due to puppet trying to manage internal directories and files. To disable that, run puppet with --no-settings_catalog. I'm going to close this, feel free to reopen if it is still an issue. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.33043.1398357448000.54214.1623366360035%40Atlassian.JIRA.
Jira (PUP-8410) It is difficult to return a hash from a plan, or function
Title: Message Title Josh Cooper commented on PUP-8410 Re: It is difficult to return a hash from a plan, or function FWIW the hash vs resource _expression_ issue is filed as PUP-6832 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.234238.1517437181000.54208.1623366120032%40Atlassian.JIRA.
Jira (PUP-8261) Restore refactored Solaris SMF acceptance tests to consolidate them
Title: Message Title Josh Cooper commented on PUP-8261 Re: Restore refactored Solaris SMF acceptance tests to consolidate them We've made improvements to puppet CI so that tests run relatively quickly and we've dropped a number of EOL Solaris platforms, so I'm going to close this. Feel free to reopen if there is still a need for this. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.227054.1513616376000.54196.1623365040106%40Atlassian.JIRA.
Jira (PUP-4288) excessive logging of fail()
Title: Message Title Josh Cooper commented on PUP-4288 Re: excessive logging of fail() I agree this is ugly and annoying, but we don't have plans on fixing this anytime soon. I'm going to close this, but feel free to reopen if you'd like to submit a pull request or see an easy way to fix this. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.72954.142727404.54194.1623364860077%40Atlassian.JIRA.
Jira (PDB-5155) Bump versions, push directly, and tag (PuppetDB 7.4.1)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5155 Bump versions, push directly, and tag (PuppetDB 7.4.1) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.403017.1623356049000.53926.1623356100469%40Atlassian.JIRA.
Jira (PDB-5157) Update winston (PuppetDB 7.4.1)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5157 Update winston (PuppetDB 7.4.1) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.403020.1623356061000.53930.1623356100645%40Atlassian.JIRA.
Jira (PDB-5156) Check builds, promote to PE (PuppetDB 7.4.1)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5156 Check builds, promote to PE (PuppetDB 7.4.1) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.403018.1623356052000.53928.1623356100556%40Atlassian.JIRA.
Jira (PDB-5154) Draft release notes (PuppetDB 7.4.1)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5154 Draft release notes (PuppetDB 7.4.1) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.403016.1623356045000.53924.1623356100380%40Atlassian.JIRA.
Jira (PDB-5152) Merge-up, branch, and create pipelines (PuppetDB 7.4.1)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5152 Merge-up, branch, and create pipelines (PuppetDB 7.4.1) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.403014.1623356038000.53920.1623356100199%40Atlassian.JIRA.
Jira (PDB-5153) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.4.1)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5153 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.4.1) Issue Type: Task Assignee: Austin Blatt Created: 2021/06/10 1:14 PM Due Date: 2021/06/10 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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-5154) Draft release notes (PuppetDB 7.4.1)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5154 Draft release notes (PuppetDB 7.4.1) Issue Type: Task Assignee: Austin Blatt Created: 2021/06/10 1:14 PM Due Date: 2021/06/20 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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-5153) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.4.1)
Title: Message Title Eric Griswold updated an issue PuppetDB / PDB-5153 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.4.1) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.403015.1623356042000.53922.1623356100292%40Atlassian.JIRA.
Jira (PDB-5156) Check builds, promote to PE (PuppetDB 7.4.1)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5156 Check builds, promote to PE (PuppetDB 7.4.1) Issue Type: Task Assignee: Austin Blatt Created: 2021/06/10 1:14 PM Due Date: 2021/06/13 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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-5155) Bump versions, push directly, and tag (PuppetDB 7.4.1)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5155 Bump versions, push directly, and tag (PuppetDB 7.4.1) Issue Type: Task Assignee: Austin Blatt Created: 2021/06/10 1:14 PM Due Date: 2021/06/13 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) (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-5157) Update winston (PuppetDB 7.4.1)
Title: Message Title Eric Griswold created an issue PuppetDB / PDB-5157 Update winston (PuppetDB 7.4.1) Issue Type: Task Assignee: Austin Blatt Created: 2021/06/10 1:14 PM Due Date: 2021/06/23 Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11116) Communicate scope and timeline of next release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-6 Communicate scope and timeline of next release (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/10 1:13 PM Due Date: 2021/06/23 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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-11115) Update Confluence and JIRA based on release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-5 Update Confluence and JIRA based on release (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/10 1:13 PM Due Date: 2021/06/23 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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-11115) Update Confluence and JIRA based on release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-5 Update Confluence and JIRA based on release (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402998.1623355981000.53916.1623356040144%40Atlassian.JIRA.
Jira (PUP-11116) Communicate scope and timeline of next release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-6 Communicate scope and timeline of next release (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402999.1623355984000.53918.1623356040232%40Atlassian.JIRA.
Jira (PDB-5152) Merge-up, branch, and create pipelines (PuppetDB 7.4.1)
Title: Message Title
Eric Griswold created an issue
PuppetDB / PDB-5152
Merge-up, branch, and create pipelines (PuppetDB 7.4.1)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2021/06/10 1:13 PM
Due Date:
2021/06/10
Priority:
Normal
Reporter:
Eric Griswold
(Initial planned release date: 2021-06-22) 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 (PUP-11109) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11109 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402990.1623355949000.53904.1623355980306%40Atlassian.JIRA.
Jira (PUP-11114) Send release announcement (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-4 Send release announcement (Puppet Platform 7.8.0) Issue Type: Task Assignee: Jacklyn Kinsler Created: 2021/06/10 1:12 PM Due Date: 2021/06/22 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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 7.8.0 is now available".
Jira (PUP-11113) Publish documentation and updates and release notes (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-3 Publish documentation and updates and release notes (Puppet Platform 7.8.0) Issue Type: Task Assignee: Christine Yoon Created: 2021/06/10 1:12 PM Due Date: 2021/06/22 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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-11111) Prepare release announcement (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-1 Prepare release announcement (Puppet Platform 7.8.0) Issue Type: Task Assignee: Christine Yoon Created: 2021/06/10 1:12 PM Due Date: 2021/06/21 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Christine Yoon 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-11113) Publish documentation and updates and release notes (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-3 Publish documentation and updates and release notes (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402995.1623355969000.53912.1623355980592%40Atlassian.JIRA.
Jira (PUP-11112) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-2 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402994.1623355965000.53910.1623355980504%40Atlassian.JIRA.
Jira (PUP-11107) Puppet Platform 7.8.0 Release - 2021-06-22
Title: Message Title Eric Griswold created an issue Puppet / PUP-11107 Puppet Platform 7.8.0 Release - 2021-06-22 Issue Type: Epic Assignee: Aidan Nathanson Created: 2021/06/10 1:12 PM Due Date: 2021/06/22 Priority: Normal Reporter: Eric Griswold Puppet Platform 7.8.0 Release - 2021-06-22 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11111) Prepare release announcement (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-1 Prepare release announcement (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402992.1623355957000.53908.1623355980417%40Atlassian.JIRA.
Jira (PUP-11112) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-2 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/10 1:12 PM Due Date: 2021/06/21 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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-11109) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11109 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/10 1:12 PM Due Date: 2021/06/11 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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-11108) Prepare JIRA and Confluence for release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-11108 Prepare JIRA and Confluence for release (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402989.1623355945000.53902.1623355980288%40Atlassian.JIRA.
Jira (PUP-11108) Prepare JIRA and Confluence for release (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-11108 Prepare JIRA and Confluence for release (Puppet Platform 7.8.0) Issue Type: Task Assignee: Aidan Nathanson Created: 2021/06/10 1:12 PM Due Date: 2021/06/11 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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 7.8.0 and puppet-agent 7.8.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-11110) Prepare documentation updates and release notes (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold created an issue Puppet / PUP-0 Prepare documentation updates and release notes (Puppet Platform 7.8.0) Issue Type: Task Assignee: Christine Yoon Created: 2021/06/10 1:12 PM Due Date: 2021/06/13 Labels: release Priority: Normal Reporter: Eric Griswold (Initial planned release date: 2021-06-22) 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-11114) Send release announcement (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-4 Send release announcement (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402997.1623355976000.53914.1623355980694%40Atlassian.JIRA.
Jira (PUP-11110) Prepare documentation updates and release notes (Puppet Platform 7.8.0)
Title: Message Title Eric Griswold updated an issue Puppet / PUP-0 Prepare documentation updates and release notes (Puppet Platform 7.8.0) Change By: Eric Griswold Epic Link: PUP-11107 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402991.1623355953000.53906.1623355980358%40Atlassian.JIRA.
Jira (PUP-7755) [research] workflow replacement for per-environment (plugin-sync) facts
Title: Message Title Josh Cooper commented on PUP-7755 Re: [research] workflow replacement for per-environment (plugin-sync) facts We don't have plans on changing how facts can be distributed per environment, so I'm going to close this. However, we do have plans on making that process more efficient, especially when an agent is provisioned or changes to environments. See PUP-11032. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.199066.1499288017000.53877.1623354960032%40Atlassian.JIRA.
Jira (PUP-7315) rspec: add test for hiera interpolated options
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7315 rspec: add test for hiera interpolated options Change By: Josh Cooper Sprint: Agent 2017-05-03 , Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.179034.148891506.53874.1623354660089%40Atlassian.JIRA.
Jira (PUP-7315) rspec: add test for hiera interpolated options
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-7315 rspec: add test for hiera interpolated options Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.179034.148891506.53873.1623354660042%40Atlassian.JIRA.
Jira (PUP-7298) SUGGESTION: Add return code to error message on file resources
Title: Message Title Josh Cooper commented on PUP-7298 Re: SUGGESTION: Add return code to error message on file resources The http client code has been rewritten since this was filed. The current behavior is that we print the error (as before): Error: /Stage[main]/Main/File[/tmp/foo.html]: Could not evaluate: Could not retrieve information from environment production source(s) https://puppet.com/notareallink When running with debug, we print additional information about all HTTP calls: Debug: Creating new connection for https://puppet.com:443 Debug: Starting connection for https://puppet.com:443 Debug: Using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 Debug: HTTP HEAD https://puppet.com/notareallink returned 404 Not Found Debug: Caching connection for https://puppet.com:443 Error: /Stage[main]/Main/File[/tmp/foo.html]: Could not evaluate: Could not retrieve information from environment production source(s) https://puppet.com/notareallink While it would be nice to surface additional information about the error in non-debug runs, we don't have plans on implementing that, so I'm going to close this. Please reopen if you'd like to submit a pull request. Feel free to reach out on slack if you have questions.
Jira (PUP-7184) Puppet::FileSystem should implement `readlines`
Title: Message Title
Josh Cooper commented on PUP-7184
Re: Puppet::FileSystem should implement `readlines`
We're only using readlines in a few providers (none of which are windows) and relying on ruby's default external encoding isn't great, we don't have other reports that I know of on non-en_US locales, so I'm going to close this. Please reopen if there is still a need for this:
$ git grep readlines lib
lib/puppet/provider/package/openbsd.rb:File.open("/etc/pkg.conf", "rb").readlines.each do |line|
lib/puppet/provider/service/rcng.rb: File.open(rcfile).readlines.each do |line|
lib/puppet/provider/service/rcng.rb: File.open(rcfile).readlines.each do |line|
lib/puppet/provider/user/user_role_add.rb:@shadow_entry = File.readlines(target_file_path).
lib/puppet/util/user_attr.rb:File.readlines('/etc/user_attr').each do |line|
Add Comment
Jira (PUP-6949) generate() should optionally fail if program writes to stderr
Title: Message Title Josh Cooper commented on PUP-6949 Re: generate() should optionally fail if program writes to stderr This is a dup of PUP-4369 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.164201.1480496627000.53841.1623352500065%40Atlassian.JIRA.
Jira (PUP-6985) False test failures on Windows due to case-sensitive paths
Title: Message Title Josh Cooper commented on PUP-6985 Re: False test failures on Windows due to case-sensitive paths We don't have plans on fixing this in the near future, so I'm going to close this. Please reopen if you'd like to submit a pull request. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.165524.1481150338000.53840.1623352440241%40Atlassian.JIRA.
Jira (PUP-6978) Distinguish errors in ClassInformationService response for class located in improper manifest file
Title: Message Title
Josh Cooper commented on PUP-6978
Re: Distinguish errors in ClassInformationService response for class located in improper manifest file
Due to the validation ticket Henrik Lindberg mentioned the environment classes endpoint no longer returns class information:
# curl -sf -k --cert /etc/puppetlabs/puppet/ssl/certs/big-swarm.delivery.puppetlabs.net.pem --key /etc/puppetlabs/puppet/ssl/private_keys/big-swarm.delivery.puppetlabs.net.pem -X GET -H 'Accept: application/json' 'https://big-swarm.delivery.puppetlabs.net:8140/puppet/v3/environment_classes?environment=production'
{"files":[{"classes":[],"path":"/etc/puppetlabs/code/environments/production/manifests/site.pp"}],"name":"production"}
which is consistent with the agent run (since the class-to-be-included can't be found):
# puppet agent -t
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::mymodule::myclass for big-swarm.delivery.puppetlabs.net (file: /etc/puppetlabs/code/environments/production/manifests/site.pp, line: 1, column: 1) on node big-swarm.delivery.puppetlabs.net
...
Jira (PUP-6960) Resource reference errors during agent run (success during apply)
Title: Message Title Josh Cooper commented on PUP-6960 Re: Resource reference errors during agent run (success during apply) The issue was addressed upstream, so I'm going to close this. In general trying to validate a parameter in one resource against other resources in the catalog shouldn't be done in the parameter's validate block, because it depends on the order that those resources are added to the catalog (and the order of parameters within a single resource). You're better off defining a validate method for the entire type, like the file type does to validate interdependent parameters (source, content, etc). Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.164602.1480569484000.53818.162335138%40Atlassian.JIRA.
Jira (PUP-6863) Set max_nesting to prevent "Nesting Level Too Deep" errors in catalog
Title: Message Title Josh Cooper commented on PUP-6863 Re: Set max_nesting to prevent "Nesting Level Too Deep" errors in catalog We no longer use PSON by default and are in the process of dropping it entirely. JSON on the other hand sets a max_nesting limit to 100 (as of 2.7.3 https://github.com/ruby/ruby/blob/6847ee089d7655b2a0eea4fee3133aeacd4cc7cc/ext/json/parser/parser.c#L1728-L1730). So I'm going to close this as won't fix. Please reopen if this is an issue when using JSON serialization in puppet 6 or newer. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.159403.1478103021000.53803.1623350640096%40Atlassian.JIRA.
Jira (PUP-6832) hash/resource expression confusion
Title: Message Title Josh Cooper commented on PUP-6832 Re: hash/resource _expression_ confusion We don't have plans on fixing this in the near future, so I'm going to close this. Please reopen if it is still needed. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.157515.1476868362000.53785.1623350040481%40Atlassian.JIRA.
Jira (PUP-6785) Service start unit tests fail on Solaris
Title: Message Title Josh Cooper commented on PUP-6785 Re: Service start unit tests fail on Solaris We're unlikely to work on getting puppet rspec tests working on Solaris, so I'm going to close this. Please reopen if anyone has time to work on this and submit a pull request. Feel free to reach out in slack if you have questions. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.155112.1475681913000.53774.1623349860099%40Atlassian.JIRA.
Jira (PUP-6744) control warning for unrecognized escapes in dq strings with --strict
Title: Message Title Josh Cooper commented on PUP-6744 Re: control warning for unrecognized escapes in dq strings with --strict Given that future parser has been around for a long time and we document the behavior with respect to how double quoted string warn if there is unrecognized escape sequence, it seems like the right thing to me is to fix the offending puppet code, not "paper over" the issue by suppressing the warning. I'm going to close as won't fix. Please reopen if I'm missing something. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.153672.147498218.53767.1623349680040%40Atlassian.JIRA.
Jira (PUP-5944) Update the language specification for captures rest in args by name definitions
Title: Message Title Josh Cooper commented on PUP-5944 Re: Update the language specification for captures rest in args by name definitions The parent ticket was closed won't do, so I'm closing the subtask as well. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.117708.1456030789000.53738.1623348420160%40Atlassian.JIRA.
Jira (PUP-5504) `puppet resource service` as non-root on Mac OS X spews errors
Title: Message Title
Josh Cooper commented on PUP-5504
Re: `puppet resource service` as non-root on Mac OS X spews errors
I can't reproduce this using more recent puppet:
languid-rye:~ bob$ id
uid=1002(bob) gid=1000 groups=1000,12(everyone),61(localaccounts),100(_lpoperator)
languid-rye:~ bob$ puppet resource service
service { 'com.apple.AEServer':
ensure => 'stopped',
enable => 'false',
provider => 'launchd',
}
...
Add Comment
Jira (PUP-6001) Incomplete process table due to COLUMNS variable
Title: Message Title
Josh Cooper commented on PUP-6001
Re: Incomplete process table due to COLUMNS variable
The getpid method was rewritten to use Puppet::Util::Execution.execute so it would be fairly trivial to pass a custom environment that excludes the COLUMNS environment variable. You just have to make sure to "reenable" the default failonfail/combine options. Something like:
ps = getps
env = ENV.dup
env.delete('COLUMNS')
self.debug "Executing '#{ps}'"
table = Puppet::Util::Execution.execute(ps, failonfail: true, combine: true, custom_environment: env)
That said, we no longer support wheezy and most of our supported platforms don't use the ps command to detect services. So I'm going to close this as won't do. If someone wants to submit a pull request, please reopen the ticket and reach out on slack.
Add Comment
Jira (PUP-5942) Allow a Struct type to define keys using a pattern
Title: Message Title Josh Cooper commented on PUP-5942 Re: Allow a Struct type to define keys using a pattern Based on Henrik Lindberg comment in https://tickets.puppetlabs.com/browse/PUP-4669?focusedCommentId=632368=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-632368, I'm going to close this as well. It sounds like adding a Like data type would be a better way of handling this. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.117706.1456028309000.53658.1623345180275%40Atlassian.JIRA.
Jira (PUP-5943) Update Language Specification for (PUP-5942) Allow a Struct type to define keys using a pattern
Title: Message Title Josh Cooper commented on PUP-5943 Re: Update Language Specification for (PUP-5942) Allow a Struct type to define keys using a pattern Closing the subtask as won't do as well. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.117707.1456028366000.53659.1623345180326%40Atlassian.JIRA.
Jira (PUP-5714) Add a 'git' checksum type for file resource sources
Title: Message Title Josh Cooper commented on PUP-5714 Re: Add a 'git' checksum type for file resource sources If we improve/cache file metadata, then it'll likely be done as part of a code manager/r10k deployment (like we do for puppet generate types). So I'm going to close this as won't do. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.112551.1452820376000.53639.1623344880384%40Atlassian.JIRA.
Jira (PUP-11049) Ruby 3 changes default external encoding on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11049 Ruby 3 changes default external encoding on Windows Change By: Josh Cooper Fix Version/s: PUP 7.9.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.397714.1619738481000.53612.1623344340043%40Atlassian.JIRA.
Jira (PUP-11049) Ruby 3 changes default external encoding on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11049 Ruby 3 changes default external encoding on Windows Change By: Josh Cooper Fix Version/s: PUP 7.8.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.397714.1619738481000.53610.1623344280040%40Atlassian.JIRA.
Jira (PUP-11049) Ruby 3 changes default external encoding on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11049 Ruby 3 changes default external encoding on Windows Change By: Josh Cooper Epic Link: PUP-11071 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.397714.1619738481000.53611.1623344280084%40Atlassian.JIRA.
Jira (PUP-7635) Custom service provider is always selected as default
Title: Message Title
Josh Cooper commented on PUP-7635
Re: Custom service provider is always selected as default
Daniel Urist actually I'm not able to reproduce this. Puppet only selects a provider as a possible default if it (or one of its superclasses) specifies defaultfor and the platform you're running on satisfies that criteria. In your example, the test provider doesn't define defaultfor and neither do init, base, service, so I never see testdefaultservice selected as a default. It's possible this was fixed when notdefaultfor was added or in PUP-1766. Kienan I'm also not able to reproduce the runit issue:
root@reddish-endgame:~# puppet resource service cron ensure=running
service { 'cron':
ensure => 'running',
provider => 'systemd',
}
root@reddish-endgame:~# apt install runit
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
runit
0 upgraded, 1 newly installed, 0 to remove
Jira (PUP-6654) @property_hash not updated in OSX user directoryservice provider
Title: Message Title
Josh Cooper commented on PUP-6654
Re: @property_hash not updated in OSX user directoryservice provider
I can't repro with the most recent version:
languid-rye:~ root# facter os.macosx
{
build => "18C54",
product => "Mac OS X",
version => {
full => "10.14.2",
major => "10.14",
minor => "2"
}
}
languid-rye:~ root# puppet resource user bar ensure=present
Notice: /User[bar]/ensure: created
user { 'bar':
ensure => 'present',
Jira (FACT-3045) facter4 performance regression from facter3
Title: Message Title Alex Schultz updated an issue Facter / FACT-3045 facter4 performance regression from facter3 Change By: Alex Schultz Attachment: facter-t-root.log.gz Attachment: facter-t-nonroot.log.gz Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.400063.1621546219000.53335.1623331260105%40Atlassian.JIRA.
Jira (FACT-3045) facter4 performance regression from facter3
Title: Message Title Alex Schultz commented on FACT-3045 Re: facter4 performance regression from facter3 weird not certain how I got 2. Anyway I reran and in my tests it takes 17 seconds when run as non-root and 56 seconds when run as root. It's better but not great. See attached. On centos8: [root@standalone-0 ~]# gem install facter Fetching: hocon-1.3.1.gem (100%) Successfully installed hocon-1.3.1 Fetching: thor-1.1.0.gem (100%) Successfully installed thor-1.1.0 Fetching: facter-4.2.1.gem (100%) Successfully installed facter-4.2.1 3 gems installed [stack@standalone-0 ~]$ time /usr/local/bin/facter -t 2>&1 > facter-t-nonroot.log real 0m17.017s user 0m7.477s sys 0m9.664s [stack@standalone-0 ~]$ sudo -i [root@standalone-0 ~]# time /usr/local/bin/facter -t 2>&1 > facter-t-root.log real 0m56.623s user 0m11.093s sys 0m47.965s Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.400063.1621546219000.53334.1623331260046%40Atlassian.JIRA.
Jira (PUP-10892) Update Public-facing Puppet docs to include Fedora 34 x86_64
Title: Message Title Claire Cadman commented on PUP-10892 Re: Update Public-facing Puppet docs to include Fedora 34 x86_64 Sounds good! FYI Christine Yoon Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.386584.1612776588000.53314.1623325500101%40Atlassian.JIRA.
Jira (PUP-10893) Update Public-facing Puppet docs to include OSX 11 Big Sur
Title: Message Title Mihai Buzgau commented on PUP-10893 Re: Update Public-facing Puppet docs to include OSX 11 Big Sur Claire Cadman Christine Yoon macOS 11 Big Sur will also go out in the 6.23.0 release. Same as the 7 stream, we're only going to provide the 64-bit packages Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.386622.1612796673000.53312.1623325440149%40Atlassian.JIRA.
Jira (PUP-10967) Puppet always prints errors in debug when trying to resolve account to SID
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-10967 Puppet always prints errors in debug when trying to resolve account to SID Change By: Ciprian Badescu Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.391432.1615943783000.53287.1623323280036%40Atlassian.JIRA.
Jira (PUP-11106) superclass mismatch for class Uniquefile (TypeError)
Title: Message Title Philipp H commented on PUP-11106 Re: superclass mismatch for class Uniquefile (TypeError) Josh Cooper Thank you very much for your input! As I am using atomic updates ( fedora coreos ), the folders in /opt are mounted from /usr/lib/opt and puppet is actually installed in /usr/lib/opt. This was also the case in version 7.6.1. As you mentioned there seems to be a load path conflict with this setup in the new version. Is there any way to force the puppet ruby load path? (I guess I have to figure this out myself, as this version of fedora is not really supported.) Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402824.1623227757000.53231.1623314040026%40Atlassian.JIRA.
Jira (FACT-2848) Improve performance of cache manager
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2848 Improve performance of cache manager Change By: Ciprian Badescu all changes must keep backwards compatibility with existing API and configuration Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.376315.160389490.53228.1623312960046%40Atlassian.JIRA.
Jira (FACT-2848) Improve performance of cache manager
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2848 Improve performance of cache manager Change By: Ciprian Badescu Epic Link: FACT-3051 Issue Type: Task Improvement Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.376315.160389490.53216.1623312300034%40Atlassian.JIRA.
Jira (FACT-3017) Add OSX11 Big Sur support
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3017 Add OSX11 Big Sur support Change By: Mihai Buzgau Fix Version/s: FACT 3.14.18 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395609.1618486266000.53211.1623310620079%40Atlassian.JIRA.
Jira (PUP-11062) better handling of enable=delayed case for a systemd service
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11062 better handling of enable=delayed case for a systemd service Change By: Mihai Buzgau Fix Version/s: PUP 7.8.0 Fix Version/s: PUP 6.23.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399504.162100079.53187.1623310200233%40Atlassian.JIRA.
Jira (PUP-11025) Add OSX11 Big Sur support
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11025 Add OSX11 Big Sur support Change By: Mihai Buzgau Fix Version/s: PUP 6.23.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395611.1618488429000.53181.1623310140181%40Atlassian.JIRA.
Jira (PUP-11026) puppet cannot set/change password of a user resource on Big Sur
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11026 puppet cannot set/change password of a user resource on Big Sur Change By: Mihai Buzgau Fix Version/s: PUP 7.8.0 Fix Version/s: PUP 6.23.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.395612.1618492793000.53182.1623310140224%40Atlassian.JIRA.
Jira (PUP-11022) Running `bundle exec rake/rspec spec` has failures on main branch
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11022 Running `bundle exec rake/rspec spec` has failures on main branch Change By: Mihai Buzgau Fix Version/s: PUP 6.22.0 Fix Version/s: PUP 6.23.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394276.1617737537000.53180.1623310140135%40Atlassian.JIRA.
Jira (PUP-11071) Ruby 3 support - Phase 2
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11071 Ruby 3 support - Phase 2 Change By: Ciprian Badescu Summary: Ruby 3 support - Phase 2 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.400586.1621958026000.53177.1623310020357%40Atlassian.JIRA.
Jira (PUP-9328) puppet can't recognize Include syntax in yum.conf
Title: Message Title Ciprian Badescu commented on PUP-9328 Re: puppet can't recognize Include syntax in yum.conf Hi Fu Chen, thanks for raising this however a lot of time passed since this issue was raised and due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. If you are interested in submitting a patch to the repository for this project at https://github.com/puppetlabs, please open a pull request and re-open this ticket. Pending that, we are closing this as “Won’t Fix.” We may revisit it at a later time, and if so will re-open this ticket Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.285743.1542688799000.53135.1623306600036%40Atlassian.JIRA.
