Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows
Title: Message Title
William Hurt updated an issue
Puppet Task Runner / BOLT-1429
Inconsistent behavior in Boltspec::Run.run_command on Windows
Change By:
William Hurt
When the WinRM transport is used with the run_command method, Bolt leverages the WinRM gem and deliberately chooses to create a [PowerShell session on the remote host|https://github.com/puppetlabs/bolt/blob/master/lib/bolt/transport/winrm/connection.rb#L54].Using the local_windows transport to execute commands on the local host however is different. A simple [call to Open3.capture3|https://github.com/puppetlabs/bolt/blob/master/lib/bolt/transport/local_windows.rb#L71] is made.The effect on the end user is that the behavior of commands given to run_command is inconsistent.Litmus for instance exposes a method called ` run_shell ` that ends up leveraging ` run_command ` . Users that want to test their module using Litmus would be forced to detect within their test suite which scenario they are in at run time, local or remote, and if local, wrap their own commands in ` ' powershell.exe -noprofile -command #{ < blah }` >' boilerplate on their own.Instead, since the better default choice has already been made for WinRM transport commands, it seems like it could solve the issue closer to the source if the local transport were made to implement it's own wrapper, so that all consumers of the `run_command` method in Bolt spec, whether they be end users or frameworks, could enjoy consistency in the behavior of their commands.As an example of users already affected see [this PR comment|https://github.com/puppetlabs/puppetlabs-dsc/pull/414#discussion_r297455284] in which we are already faced with this difficulty while converting a module's test suite to Litmus.
Add Comment
Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows
Title: Message Title
William Hurt created an issue
Puppet Task Runner / BOLT-1429
Inconsistent behavior in Boltspec::Run.run_command on Windows
Issue Type:
Bug
Assignee:
Unassigned
Components:
bolt, Windows
Created:
2019/06/25 11:05 PM
Labels:
bolt windows
Priority:
Normal
Reporter:
William Hurt
When the WinRM transport is used with the run_command method, Bolt leverages the WinRM gem and deliberately chooses to create a PowerShell session on the remote host. Using the local_windows transport to execute commands on the local host however is different. A simple call to Open3.capture3 is made. The effect on the end user is that the behavior of commands given to run_command is inconsistent. Litmus for instance exposes a method called `run_shell` that ends up leveraging `run_command`. Users that want to test their module using Litmus would be forced to detect within their test suite which scenario they are in at run time, local or remote, and if local, wrap their own commands in `powershell.exe -noprofile -command # {blah} ` boilerplate on their own. Instead, since the better default choice has already been made for WinRM transport commands, it seems like it could solve the issue closer to the source if the local transport were made to implement it's own wrapper, so that all consumers of the `run_command` method in Bolt spec, whether they be end users or frameworks, could enjoy consistency in the behavior of their commands. As an example of users already affected see this PR comment in which we are already faced with this difficulty while converting a module's test suite to Litmus.
Jira (PDB-4422) initial migration at first start fails puppetdb hangs.
Title: Message Title Felipe Garcia commented on PDB-4422 Re: initial migration at first start fails puppetdb hangs. I pinned the version of postgres to .13 and it works fine. Note. when puppetdb failed to migrate systemctl was unable to stop the service and it had to be killed off. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313863.1561448596000.61241.1561513440588%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title
Tom Beech commented on BOLT-1318
Re: Modulepath unable to handle folder names in uppercase characters on Windows
Digging around a bit more it looks like all platforms are case-sensitive, not just windows. This holds wherever the user provides a path, whether at the command line when using --boltdir or --modulepath, in or in a bolt.yaml. Providing an error like this should be easy enough: $ bolt plan show --modulepath c:/data/workshop WARNING: Bolt is case sensitive when providing a module path. Did you mean:{{ }} C:/DATA/workshop Since paths are case-sensitive across platforms would it be preferable to have this type of warning, stress the case-sensitivity in the docs, or both?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.61153.1561507801239%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4443) PuppetDB master branch failing to promote into PE Lovejoy
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4443 PuppetDB master branch failing to promote into PE Lovejoy Issue Type: Bug Assignee: Unassigned Created: 2019/06/25 4:17 PM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https
Jira (PDB-4443) PuppetDB master branch failing to promote into PE Lovejoy
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4443 PuppetDB master branch failing to promote into PE Lovejoy Change By: Austin Blatt Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314108.1561504644000.60826.1561504681552%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4422) initial migration at first start fails puppetdb hangs.
Title: Message Title Austin Blatt commented on PDB-4422 Re: initial migration at first start fails puppetdb hangs. This fix has been merged and we are in the process of releasing versions of PuppetDB that avoid hitting the bug in PostgreSQL. You can follow the release Epic for your PuppetDB version stream if you'd like, but the packages will likely go live at the same time for all three. 5.2.9 - PDB-4425 6.0.4 - PDB-4431 6.3.4 - PDB-4437 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313863.1561448596000.60761.1561502880483%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4346) Update sync deduplication to account for configure-expiration commands
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4346 Update sync deduplication to account for configure-expiration commands Change By: Austin Blatt Fix Version/s: PDB 6.0.4 Fix Version/s: PDB 5.2.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305159.117556000.60740.1561501440793%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4367) Make sure jackson databind is not excluded in any relevant pdb or pdbext branches
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4367 Make sure jackson databind is not excluded in any relevant pdb or pdbext branches Change By: Austin Blatt Fix Version/s: PDB 6.0.4 Fix Version/s: PDB 5.2.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308133.1557439306000.60734.1561501440510%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4321) Typo in blacklist configuration docs
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4321 Typo in blacklist configuration docs Change By: Austin Blatt Fix Version/s: PDB 6.0.4 Fix Version/s: PDB 5.2.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302192.155380710.60730.1561501381120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4326) PuppetDB rejects catalogs with tags added automatically by Puppet
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4326 PuppetDB rejects catalogs with tags added automatically by Puppet Change By: Austin Blatt Fix Version/s: PDB 6.0.4 Fix Version/s: PDB 5.2.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302664.1554209608000.60726.1561501380932%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4345) Add name field to resource_events to avoid further duplication errors
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4345 Add name field to resource_events to avoid further duplication errors Change By: Austin Blatt Fix Version/s: PDB 6.0.4 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304800.1555358173000.60722.1561501380746%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4362) Fix upgrade_oldest
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4362 Fix upgrade_oldest Change By: Austin Blatt Fix Version/s: PDB 6.3.3 Fix Version/s: PDB n/a Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306703.1556573725000.60715.1561501320857%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4345) Add name field to resource_events to avoid further duplication errors
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4345 Add name field to resource_events to avoid further duplication errors Change By: Austin Blatt Fix Version/s: PDB 5.2.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304800.1555358173000.60718.1561501320998%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4347) Don't use a static temp table name for fact path gc
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4347 Don't use a static temp table name for fact path gc Change By: Austin Blatt Fix Version/s: PDB 6.0.4 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305777.1555967633000.60710.1561501320623%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4347) Don't use a static temp table name for fact path gc
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4347 Don't use a static temp table name for fact path gc Change By: Austin Blatt Fix Version/s: PDB 5.2.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305777.1555967633000.60707.1561501260335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1428) vRA: Support 7.5 and 7.6
Title: Message Title Lindsey Smith created an issue Puppet Task Runner / BOLT-1428 vRA: Support 7.5 and 7.6 Issue Type: Epic Assignee: Unassigned Created: 2019/06/25 3:15 PM Priority: Normal Reporter: Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.co
Jira (PDB-4438) Merge-up, branch, and create pipelines (PuppetDB 6.3.4)
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-4438
Merge-up, branch, and create pipelines (PuppetDB 6.3.4)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/06/25 2:48 PM
Due Date:
2019/06/18
Priority:
Normal
Reporter:
Austin Blatt
(Initial planned release date: 2019-06-25) 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
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
6.0.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
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:
Jira (PDB-4439) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.4)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4439 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.4) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:48 PM Due Date: 2019/06/18 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment
Jira (PDB-4442) Update winston (PuppetDB 6.3.4)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4442 Update winston (PuppetDB 6.3.4) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:49 PM Due Date: 2019/06/26 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4440) Bump versions, push directly, and tag (PuppetDB 6.3.4)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4440 Bump versions, push directly, and tag (PuppetDB 6.3.4) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:48 PM Due Date: 2019/06/21 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) (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 before pushing a non-snapshot version and tagging. Disable automatic promotions: Go to the CI pipeline for the version being released and select the Conditional Promotion Trigger job. Click the disable button (the job's circle indicator should be gray now). 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. Go into the 'release-new' hipchat room to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch you're releasing.
Jira (PDB-4437) PuppetDB 6.3.4 2019-06-25 Release
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4437 PuppetDB 6.3.4 2019-06-25 Release Issue Type: Epic Assignee: Austin Blatt Created: 2019/06/25 2:48 PM Priority: Normal Reporter: Austin Blatt PuppetDB 6.3.4 2019-06-25 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4441) Check builds, promote to PE (PuppetDB 6.3.4)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4441 Check builds, promote to PE (PuppetDB 6.3.4) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:48 PM Due Date: 2019/06/22 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) 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. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4434) Bump versions, push directly, and tag (PuppetDB 6.0.4)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4434 Bump versions, push directly, and tag (PuppetDB 6.0.4) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:47 PM Due Date: 2019/06/21 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) (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 before pushing a non-snapshot version and tagging. Disable automatic promotions: Go to the CI pipeline for the version being released and select the Conditional Promotion Trigger job. Click the disable button (the job's circle indicator should be gray now). 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. Go into the 'release-new' hipchat room to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch you're releasing.
Jira (PDB-4436) Update winston (PuppetDB 6.0.4)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4436 Update winston (PuppetDB 6.0.4) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:47 PM Due Date: 2019/06/26 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4433) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.0.4)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4433 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.0.4) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:47 PM Due Date: 2019/06/18 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment
Jira (PDB-4431) PuppetDB 6.0.4 2019-06-25 Release
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4431 PuppetDB 6.0.4 2019-06-25 Release Issue Type: Epic Assignee: Austin Blatt Created: 2019/06/25 2:47 PM Priority: Normal Reporter: Austin Blatt PuppetDB 6.0.4 2019-06-25 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4432) Merge-up, branch, and create pipelines (PuppetDB 6.0.4)
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-4432
Merge-up, branch, and create pipelines (PuppetDB 6.0.4)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/06/25 2:47 PM
Due Date:
2019/06/18
Priority:
Normal
Reporter:
Austin Blatt
(Initial planned release date: 2019-06-25) 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
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
6.0.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
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:
Jira (PDB-4435) Check builds, promote to PE (PuppetDB 6.0.4)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4435 Check builds, promote to PE (PuppetDB 6.0.4) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:47 PM Due Date: 2019/06/22 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) 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. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4425) PuppetDB 5.2.9 2019-06-25 Release
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4425 PuppetDB 5.2.9 2019-06-25 Release Issue Type: Epic Assignee: Austin Blatt Created: 2019/06/25 2:44 PM Priority: Normal Reporter: Austin Blatt PuppetDB 5.2.9 2019-06-25 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4428) Bump versions, push directly, and tag (PuppetDB 5.2.9)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4428 Bump versions, push directly, and tag (PuppetDB 5.2.9) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:44 PM Due Date: 2019/06/21 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) (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 before pushing a non-snapshot version and tagging. Disable automatic promotions: Go to the CI pipeline for the version being released and select the Conditional Promotion Trigger job. Click the disable button (the job's circle indicator should be gray now). 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. Go into the 'release-new' hipchat room to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch you're releasing.
Jira (PDB-4427) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.9)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4427 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.9) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:44 PM Due Date: 2019/06/18 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment
Jira (PDB-4430) Update winston (PuppetDB 5.2.9)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4430 Update winston (PuppetDB 5.2.9) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:44 PM Due Date: 2019/06/26 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4429) Check builds, promote to PE (PuppetDB 5.2.9)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4429 Check builds, promote to PE (PuppetDB 5.2.9) Issue Type: Task Assignee: Austin Blatt Created: 2019/06/25 2:44 PM Due Date: 2019/06/22 Priority: Normal Reporter: Austin Blatt (Initial planned release date: 2019-06-25) 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. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4426) Merge-up, branch, and create pipelines (PuppetDB 5.2.9)
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-4426
Merge-up, branch, and create pipelines (PuppetDB 5.2.9)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/06/25 2:44 PM
Due Date:
2019/06/18
Priority:
Normal
Reporter:
Austin Blatt
(Initial planned release date: 2019-06-25) 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
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
6.0.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
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:
Jira (PDB-4424) Database migration 65 doesn't work on PostgreSQL
Title: Message Title Stefan Seidel created an issue PuppetDB / PDB-4424 Database migration 65 doesn't work on PostgreSQL Issue Type: Bug Affects Versions: PDB 6.3.2, PDB 6.3.0, PDB 6.2.0, PDB 6.1.0 Assignee: Unassigned Components: PuppetDB Created: 2019/06/25 1:53 PM Environment: Debian Stretch, PuppetDB 6.1.0-6.3.3 (all tested) Priority: Normal Reporter: Stefan Seidel Cannot start PuppetDB on a newly created database: 2019-06-25T22:50:12.465+02:00 INFO [p.p.s.migrate] Applying database migration version 65 2019-06-25T22:50:12.505+02:00 ERROR [p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 1 alter table resource_events
Jira (BOLT-1427) Standardize specifying file paths in bolt config
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1427 Standardize specifying file paths in bolt config Issue Type: New Feature Assignee: Unassigned Created: 2019/06/25 1:14 PM Priority: Normal Reporter: Cas Donoghue Currently, most config settings are relative to the directory bolt is invoked from (inventoryfile, private-key, etc) while some paths such as modulepath or keys for the pkcs7 plugin are relative to the boltdir. When configuration settings point to a file path it should be assumed to be relative to the bolt project directory (boltdir) unless an absolute path is specified. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-282) No way to output markdown format to stdout
Title: Message Title Jesse Scott created an issue Puppet Strings / PDOC-282 No way to output markdown format to stdout Issue Type: Bug Assignee: Unassigned Created: 2019/06/25 12:33 PM Priority: Normal Reporter: Jesse Scott The documentation for `puppet strings generate` states: --out PATH - Write selected format to PATH. If no path is designated, strings prints to STDOUT. However when `–format markdown` is specified, the output is written to REFERENCE.md rather than STDOUT and there appears to be no way to override that behavior through the CLI. I think the offending code is https://github.com/puppetlabs/puppet-strings/blob/master/lib/puppet-strings.rb#L39
Jira (PUP-9809) Update Confluence and JIRA based on release (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9809 Update Confluence and JIRA based on release (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:42 AM Due Date: 2019/07/03 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description
Jira (PUP-9810) Communicate scope and timeline of next release (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9810 Communicate scope and timeline of next release (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:42 AM Due Date: 2019/07/03 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 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-9808) Send release announcement (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9808 Send release announcement (Puppet Platform 6.6.0) Issue Type: Task Assignee: Molly Waggett Created: 2019/06/25 11:42 AM Due Date: 2019/07/02 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 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.6.0 is now available".
Jira (PUP-9806) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9806 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:41 AM Due Date: 2019/07/01 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9807) Publish documentation and updates and release notes (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9807 Publish documentation and updates and release notes (Puppet Platform 6.6.0) Issue Type: Task Assignee: Jean Bond Created: 2019/06/25 11:41 AM Due Date: 2019/07/02 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 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-9803) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9803 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:41 AM Due Date: 2019/06/26 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-9804) Prepare documentation updates and release notes (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9804 Prepare documentation updates and release notes (Puppet Platform 6.6.0) Issue Type: Task Assignee: Jean Bond Created: 2019/06/25 11:41 AM Due Date: 2019/06/28 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 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-9805) Prepare release announcement (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9805 Prepare release announcement (Puppet Platform 6.6.0) Issue Type: Task Assignee: Bill Tang Created: 2019/06/25 11:41 AM Due Date: 2019/07/01 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond 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-9802) Prepare JIRA and Confluence for release (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9802 Prepare JIRA and Confluence for release (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:40 AM Due Date: 2019/06/26 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 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.6.0 and puppet-agent 6.6.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to reference
Jira (PUP-9801) Puppet Platform 6.6.0 Release - 2019-07-02
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9801 Puppet Platform 6.6.0 Release - 2019-07-02 Issue Type: Epic Assignee: Kenn Hussey Created: 2019/06/25 11:40 AM Due Date: 2019/07/02 Priority: Normal Reporter: Kenn Hussey Puppet Platform 6.6.0 Release - 2019-07-02 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9800) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9800 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:37 AM Due Date: 2019/07/01 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9798) Prepare documentation updates and release notes (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9798 Prepare documentation updates and release notes (Puppet Platform 6.6.0) Issue Type: Task Assignee: Jean Bond Created: 2019/06/25 11:37 AM Due Date: 2019/06/28 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 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-9796) Prepare JIRA and Confluence for release (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9796 Prepare JIRA and Confluence for release (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:37 AM Due Date: 2019/06/26 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 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.6.0 and puppet-agent 6.6.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to reference
Jira (PUP-9799) Prepare release announcement (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9799 Prepare release announcement (Puppet Platform 6.6.0) Issue Type: Task Assignee: Bill Tang Created: 2019/06/25 11:37 AM Due Date: 2019/07/01 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond 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-9797) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.6.0)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9797 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.6.0) Issue Type: Task Assignee: Kenn Hussey Created: 2019/06/25 11:37 AM Due Date: 2019/06/26 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-07-02) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-9795) Puppet Platform 6.6.0 Release - 2019-07-02
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9795 Puppet Platform 6.6.0 Release - 2019-07-02 Issue Type: Epic Assignee: Kenn Hussey Created: 2019/06/25 11:36 AM Due Date: 2019/07/02 Priority: Normal Reporter: Kenn Hussey Puppet Platform 6.6.0 Release - 2019-07-02 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9647) Pip package provider should use execute for Windows compatibility
Title: Message Title
Josh Cooper commented on PUP-9647
Re: Pip package provider should use execute for Windows compatibility
I think the issue occurs if pip --version returns output that doesn't match the expected regex. To repro, created pip executable shell script in current working directory:
#!/bin/sh
echo whoops
PATH=.:$PATH bundle exec puppet apply -e "package { 'foo': provider => pip }" --trace
Notice: Compiled catalog for neptune in environment production in 0.02 seconds
Error: Failed to apply catalog: undefined method `[]' for nil:NilClass
/Users/josh/work/puppet/lib/puppet/provider/package/pip.rb:73:in `block (2 levels) in pip_version'
/Users/josh/work/puppet/lib/puppet/provider/package/pip.rb:72:in `each'
/Users/josh/work/puppet/lib/puppet/provider/package/pip.rb:72:in `collect'
/Users/josh/work/puppet/lib/puppet/provider/package/pip.rb:72:in `block in pip_version'
/Users/josh/work/puppet/lib/puppet/util/execution.rb:81:in `block (2 levels) in execpipe'
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title
John O'Connor commented on PUP-9719
Re: Cannot run Puppet Agent as Administrator if first PA run is done as System
The following is a crude script that will Fix permissions - it can be run either in the puppetrun.ps1 script or prior to using puppet agent -t as Administrator
# Script to find and fix files under C:\ProgramData\PuppetLabs that don't have
# Administrator Rights.
$Folder = "C:\ProgramData\PuppetLabs"
$AccessAdminRule = New-Object System.Security.AccessControl.FileSystemAccessRule("BUILTIN\Administrators", "Full", "Allow")
Get-ChildItem -Path "$Folder" -Recurse |
where {$_.PSIsContainer -eq $False } |
ForEach-Object {get-acl -path $_.Fullname} |
where { $_.AccessToString -notMatch "Administrators"} | ForEach-Object {
Write-Output "Working on $($_.Path)"
Write-Output "Access to String $($_.AccesstoString)"
Jira (BOLT-1362) Support Plan Language Datatypes in tasks
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1362 Support Plan Language Datatypes in tasks Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311201.1559668479000.59824.1561481760345%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1398) I want to see what nodes are in an inventory group
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1398 I want to see what nodes are in an inventory group Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312528.1560553204000.59817.1561481700478%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1398) I want to see what nodes are in an inventory group
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1398
I want to see what nodes are in an inventory group
Change By:
Lucy Wyman
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.We should find what use cases current users have around displaying inventory.A workaround for now is to use a plan that returns the targets{noformat}plan resolve_targets( TargetSpec $nodes) { return(get_targets($nodes))}{noformat}Solution:This should be a new command {{bolt inventory show }} where some targetting option supports similar options to {{bolt * run}} (ie. {{--rerun}}, {{--targets}}, etc.). The output should be support both human output (printed list of names on newlines and maybe the total number of nodes), and a JSON array names for the json output.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
-
Jira (BOLT-1398) I want to see what nodes are in an inventory group
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1398
I want to see what nodes are in an inventory group
Change By:
Lucy Wyman
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.We should find what use cases current users have around displaying inventory.A workaround for now is to use a plan that returns the targets{noformat}plan resolve_targets( TargetSpec $nodes) { return(get_targets($nodes))}{noformat}Solution:This should be a new command {{bolt inventory show }} where some targetting option supports similar options to {{bolt * run}} (ie. {{--rerun}}, {{--targets}}, etc.). The output should be support both human output (printed list of names on newlines and maybe the total number of nodes), and a JSON array names for the json output.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
-
Jira (BOLT-1398) I want to see what nodes are in an inventory group
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1398
I want to see what nodes are in an inventory group
Change By:
Lucy Wyman
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.We should find what use cases current users have around displaying inventory.A workaround for now is to use a plan that returns the targets{noformat}plan resolve_targets( TargetSpec $nodes) { return(get_targets($nodes))}{noformat} Solution: This should be a new command {{bolt inventory show }} where some targetting option supports similar options to {{bolt * run}} (ie. {{--rerun}}, {{--targets}}, etc.). The output should be support both human output (printed list of names and maybe the total number of nodes), and a JSON array names for the json output.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You recei
Jira (BOLT-1398) I want to see what nodes are in an inventory group
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1398
I want to see what nodes are in an inventory group
Change By:
Lucy Wyman
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.We should find what use cases current users have around displaying inventory. A workaround for now is to use a plan that returns the targets{noformat}plan resolve_targets( TargetSpec $nodes) { return(get_targets($nodes))}{noformat} This should be a new command {{bolt inventory show }} where some targetting option supports similar options to {{bolt * run}} (ie. {{--rerun}}, {{--targets}}, etc.). The output should be support both human output (printed list of names and maybe the total number of nodes), and a JSON array names for the json output.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title Ethan Brown commented on PUP-9719 Re: Cannot run Puppet Agent as Administrator if first PA run is done as System Be careful when referring to Administrator We typically don't want Administrator (the user), we want to apply Administrators (the group). Administrators has a well known SID of S-1-5-32-544 and includes the users we typically wish to grant access to - Administrator, SYSTEM, domain admins, etc. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.59788.1561481160862%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1425) Document orchestrator client config options relevant to bolt
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1425 Document orchestrator client config options relevant to bolt Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313858.1561422568000.59761.1561480860565%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1425) Document orchestrator client config options relevant to bolt
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1425
Document orchestrator client config options relevant to bolt
Change By:
Lucy Wyman
Creating this ticket as a result of trying to debug why long running tasks are timing out. Root cause was the default {{job-poll-timeout}} in https://github.com/puppetlabs/orchestrator_client-ruby/blob/master/lib/orchestrator_client/config.rb#L40 . The issue was solved by configuring that option in {{/etc/puppetlabs/client-tools/orchestrator.conf}} on the bolt controller with something like{code}{ "options": {"job-poll-timeout": 2000 }}{code}It is difficult (impossible?) to figure that out without looking at the source code. Add this configuration option to documentation and possibly add it to common debugging in bolt depending on if tasks will typically take longer than ~16 minsUpdate:* Add orch-client config options the pcp transport config for Bolt - these should just get passed through
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1425) Document orchestrator client config options relevant to bolt
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1425
Document orchestrator client config options relevant to bolt
Change By:
Lucy Wyman
Creating this ticket as a result of trying to debug why long running tasks are timing out. Root cause was the default {{job-poll-timeout}} in https://github.com/puppetlabs/orchestrator_client-ruby/blob/master/lib/orchestrator_client/config.rb#L40 . The issue was solved by configuring that option in {{/etc/puppetlabs/client-tools/orchestrator.conf}} on the bolt controller with something like{code}{ "options": {"job-poll-timeout": 2000 }}{code}It is difficult (impossible?) to figure that out without looking at the source code. Add this configuration option to documentation and possibly add it to common debugging in bolt depending on if tasks will typically take longer than ~16 mins Update:* Add orch-client config options the pcp transport config for Bolt
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received
Jira (BOLT-1423) Bolt actions hang over ssh transport when ProxyCommand is set in openssh config
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1423 Bolt actions hang over ssh transport when ProxyCommand is set in openssh config Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313738.1561387259000.59743.1561480620296%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1315
Collect analytics about Boltdir usage
Change By:
Lucy Wyman
We should collect a data point about whether users are using a {{Boltdir}}, a local {{bolt.yaml}}, {{~/.puppetlabs/bolt}}, default Boltdir which isn't actually there, or an explicitly specified Boltdir. We should be able to include that as a custom dimension on the screen view that we send in the CLI.On the google analytics side, this can probably be tracked as a _session_-level metric, as a single user might have multiple projects potentially following different patterns, and we would like to know about that. Research if there's a way to tell if a user is using multiple Boltdirs
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.co
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1315 Collect analytics about Boltdir usage Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309059.1558038203000.59725.1561480440345%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1315
Collect analytics about Boltdir usage
Change By:
Lucy Wyman
We should collect a data point about whether users are using a {{Boltdir}}, a local {{bolt.yaml}}, or {{~/.puppetlabs/bolt}} , default Boltdir which isn't actually there, or an explicitly specified Boltdir . We should be able to include that as a custom dimension on the screen view that we send in the CLI.On the google analytics side, this can probably be tracked as a _session_-level metric, as a single user might have multiple projects potentially following different patterns, and we would like to know about that.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegrou
Jira (BOLT-1424) Vault plugin
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1424 Vault plugin Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313814.1561405465000.59705.1561480140423%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1424) Vault plugin
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1424 Vault plugin Change By: Lucy Wyman Users should be able to lookup passwords or other credential information for targets from Vault.* We should document loading ssh private keys from vault in addition to a password example. * This will require some research around how to authenticate with Vault* Alex will try to get feedback from Ops this afternoon* Lucy will ask in office hours* The Puppet function requires you to use the Puppet CA as the Vault CA (so configure Vault to share a CA with Puppet) - this won't work for us since Bolt doesn't have a CA. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at htt
Jira (BOLT-1410) Add plugin analytics
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1410 Add plugin analytics Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313047.1560895161000.59688.1561479900254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1410) Add plugin analytics
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1410 Add plugin analytics Change By: Lucy Wyman We Questions we want analytics to know how answer:1. How the builtin plugins are being used - how a. How frequently , which b. Which plugin did they use , and which c. Which hook did they use. 2. What version of the Inventory users are specifying (1, 2, or not specified)Analytics for user-added plugins will be a separate ticket. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313047.1560895161000.59687.156147984
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1318 Modulepath unable to handle folder names in uppercase characters on Windows Change By: Lucy Wyman Bolt won’t handle folder names with one or more uppercase characters in the name incorrectly, when they are part of the modulepath. I encountered this while doing a Bolt Workshop at KPN.If the modulepath has a capitalized foldername in it, not Tasks or Plans are found in that module. It is as if the module is not there.User has this Bolt project folder:`C:\DATA\workshop` with a bolt.yaml in itand subsequently the modulepath becomes c:/data/workshop/modulesHowever no tasks/plans are ever found there.If I manually force the modulepath (in bolt.yaml) to C:/DATA/workshop then it worksBolt needs to be completely case insensitive on Windows, otherwise this breaks everythingUpdate:- When on windows, we should check to see that all paths in the modulepath exist using Ruby's File tooling the canonicalized filename , and if they don't exist we should check for a case-insensitive version and warn if that exists. The warning should state that modulepaths are case-sensitive. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1318 Modulepath unable to handle folder names in uppercase characters on Windows Change By: Lucy Wyman Bolt won’t handle folder names with one or more uppercase characters in the name incorrectly, when they are part of the modulepath. I encountered this while doing a Bolt Workshop at KPN.If the modulepath has a capitalized foldername in it, not Tasks or Plans are found in that module. It is as if the module is not there.User has this Bolt project folder:`C:\DATA\workshop` with a bolt.yaml in itand subsequently the modulepath becomes c:/data/workshop/modulesHowever no tasks/plans are ever found there.If I manually force the modulepath (in bolt.yaml) to C:/DATA/workshop then it worksBolt needs to be completely case insensitive on Windows, otherwise this breaks everything Update:- When on windows, we should check to see that all paths in the modulepath exist using Ruby's File tooling, and if they don't exist we should check for a case-insensitive version and warn if that exists. The warning should state that modulepaths are case-sensitive. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1380) OSCON Demo
Title: Message Title Yasmin Rajabi commented on BOLT-1380 Re: OSCON Demo patching demo, developer focused demo (maybe an app deployment plan using yaml), terraform demo. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312023.1560269876000.59622.1561479240145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9794 Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) Change By: Kenn Hussey Fix Version/s: PUP 6.y Fix Version/s: PUP 6.6.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313648.1561146763000.59617.1561479180799%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9790 undefined method `pip_version' with pip3 provider Change By: Kenn Hussey Fix Version/s: PUP 6.y Fix Version/s: PUP 6.6.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.59610.1561479120692%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title
Thomas Kishel commented on PUP-9794
Re: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
This is an unsupported method of patching:
# a.pp
file_line { 'PUP-9794':
path => '/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package_targetable.rb',
line => "require 'puppet/provider/package' # PUP-9794",
after => "# Rather, .*",
}
root@ip-10-0-0-1:~# puppet apply a.pp
Error: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/package_provider.rb: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Notice: Compiled catalog for ip-10-0-0-1.us-west-2.compute.internal in environment production in 0.02 seconds
Jira (BOLT-612) Some docs only list unix paths, not Windows
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-612 Some docs only list unix paths, not Windows Change By: Lucy Wyman Labels: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.261706.1529474232000.59539.1561477440438%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1346) Bolt docs: Include example returns, link to docs about returned types
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1346 Bolt docs: Include example returns, link to docs about returned types Change By: Lucy Wyman Labels: DOCS bolt feedback-form-docs-site Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310238.1558737129000.59537.1561477440343%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1425) Document orchestrator client config options relevant to bolt
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1425 Document orchestrator client config options relevant to bolt Change By: Lucy Wyman Labels: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313858.1561422568000.59533.1561477380232%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1300 Update install docs to point to puppet-enterprise-tools repo Change By: Lucy Wyman Labels: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.59522.1561477320589%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1422) Update command reference docs
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1422 Update command reference docs Change By: Lucy Wyman Labels: DOCS docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313638.1561140371000.59517.1561477080272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1183) Improve documentation for using task metaparameters with powershell input method
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1183 Improve documentation for using task metaparameters with powershell input method Change By: Lucy Wyman Labels: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300387.1552608686000.59515.1561477020172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1056) Shell one liners with pipes and redirects don't work with bolt command and run_as
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1056 Shell one liners with pipes and redirects don't work with bolt command and run_as Change By: Lucy Wyman Team: Bolt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.289883.1545415759000.59513.1561476960181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1426) A variety of Bolt Docs related tickets
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1426 A variety of Bolt Docs related tickets Issue Type: Epic Assignee: Unassigned Created: 2019/06/25 8:34 AM Priority: Normal Reporter: Lucy Wyman We have a variety of Bolt Docs tickets that don't quite fit into 'First Steps'. Labelling these for when we have a dedicated Docs person will be helpful. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1056) Shell one liners with pipes and redirects don't work with bolt command and run_as
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1056
Shell one liners with pipes and redirects don't work with bolt command and run_as
Change By:
Lucy Wyman
For example:{ noformat code }bolt command run 'base64 -d /etc/puppetlabs/license.enc > /etc/puppetlabs/license.key' -n example.com --run-as root{ fornmat code }Fails because {{sudo base64 -d /etc/puppetlabs/license.enc}} is redirected as the original user to {{/etc/puppetlabs/license.key}}It's not clear how we can fix this without overriding the login shell. We should at least document how to call {{bash}} or another shell as the command.Question: How can we make sure users find this documentation?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email t
Jira (BOLT-1295) It's difficult for users to format plan/task show output
Title: Message Title Lucy Wyman commented on BOLT-1295 Re: It's difficult for users to format plan/task show output A user this morning wanted to have better configuration for formatting other Bolt output as well. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307488.1557180252000.59494.1561476660064%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1122) Support description metaparameter for run_plan
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1122 Support description metaparameter for run_plan Change By: Lucy Wyman Summary: Support description field metaparameter for run_plan Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295534.1549653717000.59493.1561476600247%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4422) initial migration at first start fails puppetdb hangs.
Title: Message Title Charlie Sharpsteen commented on PDB-4422 Re: initial migration at first start fails puppetdb hangs. Postgres versions released last Thursday June 20th, which includes 9.6.14, contain a regression in the behavior of the ALTER TABLE statement that is causing this issue by preventing PuppetDB from initializing its database schema. A concise summary of the issue can be found in this message to the Postgres mailing list: https://www.postgresql.org/message-id/20190621004554.GB1626%40paquier.xyz There is a preliminary patch up for PuppetDB to work around the issue: https://github.com/puppetlabs/puppetdb/pull/3010 Until PuppetDB or Postgres release a new version, the best workaround is to use an older version of Postgres such as 9.6.13. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313863.1561448596000.59476.1561476300322%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9789) Constants assigned twice emit warning during Litmus use on Windows.
Title: Message Title Josh Cooper commented on PUP-9789 Re: Constants assigned twice emit warning during Litmus use on Windows. The win32 gems from djberger have lots of issues, especially around Unicode, see PUP-5560, PUP-5735. Please don't use them in PDK or any new ruby code. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313352.1561054057000.59455.1561474920819%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Alex Dreyer commented on BOLT-1318 Re: Modulepath unable to handle folder names in uppercase characters on Windows Making modulepath case insensitive on windows would make project directories incompatible across platforms which seems worse. Also modules, tasks and the rest of the puppet objects won't be so it seems better for users to learn that puppet is case sensitive early. We may want to consider checking and warning when a path only exists in case sensitive form. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.59410.1561473300516%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1409) Remove 'lookups' from 'target_lookups'
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1409 Remove 'lookups' from 'target_lookups' Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313045.1560895034000.59364.1561472880436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1409) Remove 'lookups' from 'target_lookups'
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1409 Remove 'lookups' from 'target_lookups' Change By: Cas Donoghue Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313045.1560895034000.59367.1561472880579%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9789) Constants assigned twice emit warning during Litmus use on Windows.
Title: Message Title Thomas Honey commented on PUP-9789 Re: Constants assigned twice emit warning during Litmus use on Windows. here is the ticket for context https://tickets.puppetlabs.com/browse/PDK-1348 basically we are using FFI raw, when there are commity gems designed for this https://rubygems.org/gems/win32-api/ Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313352.1561054057000.59191.1561463760381%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4423) Cannot install PDB with puppetlabs-puppetdb module with newest version postgresql96-9.6.14-1PGDG.rhel7.x86_64
Title: Message Title Fredrik Larsson commented on PDB-4423 Re: Cannot install PDB with puppetlabs-puppetdb module with newest version postgresql96-9.6.14-1PGDG.rhel7.x86_64 Duplicate of PDB-4422 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313871.156145680.59170.1561459740408%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4422) initial migration at first start fails puppetdb hangs.
Title: Message Title Fredrik Larsson updated an issue PuppetDB / PDB-4422 initial migration at first start fails puppetdb hangs. Change By: Fredrik Larsson Affects Version/s: PDB 6.3.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313863.1561448596000.59161.1561458660382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4423) Cannot install PDB with puppetlabs-puppetdb module with newest version postgresql96-9.6.14-1PGDG.rhel7.x86_64
Title: Message Title Alexander Dubskiy created an issue PuppetDB / PDB-4423 Cannot install PDB with puppetlabs-puppetdb module with newest version postgresql96-9.6.14-1PGDG.rhel7.x86_64 Issue Type: Bug Affects Versions: PDB 6.3.2, PDB 5.2.8 Assignee: Unassigned Components: PuppetDB Created: 2019/06/25 3:00 AM Environment: Fresh install of CentOS 7.6.1810 x86_64 Added repos: epel, puppet5-release-el-7 Installed and started puppetserver Installed modules: /etc/puppetlabs/code/modules ├── puppetlabs-apt (v7.0.1) ├── puppetlabs-concat (v6.0.0) ├── puppetlabs-firewall (v2.0.0) ├── puppetlabs-inifile (v3.0.0) ├── puppetlabs-postgresql (v6.1.0) ├── puppetlabs-puppetdb (v7.3.0) ├── puppetlabs-stdlib (v6.0.0) └── puppetlabs-translate (v1.2.0) Priority: Blocker Reporter: Alexander Dubskiy When installing PuppetDB using the command: puppet apply -e "include puppetdb" installation hangs at starting puppetdb service. In /var/log/puppetlabs/puppetdb/puppetdb.log: 2019-06-25 12:53:03,248 INFO [p.p.s.migrate] Applying database migration version 65 2019-06-25 12:53:03,282 ERROR [p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 1 alter table resource_events alter column status type text, alter column property type text, alter column containing_class type text, alter column file type text was aborted. Call getNextException to see the cause. ... 2019-06-25 12:53:03,284 ERROR [p.p.s.migrate] Unravelled exception org.postgresql.util.PSQLException: ERROR: relation "resource_events_status_for_corrective_change_idx" already exists ... Thi
