Jira (BOLT-547) Finish plans when using the pcp transport
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-547 Finish plans when using the pcp transport Change By: Michael Smith Assignee: Michael 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.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Erick Banks updated an issue Puppet / PUP-6729 NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators Change By: Erick Banks Sprint: Windows 2018-06-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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-547) Finish plans when using the pcp transport
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-547 Finish plans when using the pcp transport Change By: Michael Smith Assignee: Michael 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.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8771) Write integration/acceptance tests for NTFS permissions for PUP-6729
Title: Message Title Erick Banks updated an issue Puppet / PUP-8771 Write integration/acceptance tests for NTFS permissions for PUP-6729 Change By: Erick Banks Sprint: Windows 2018-05-30 Hopper , Windows 2018- 06 05 - 06 30 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6894) Remove Ruby 1.9.3 related pinning of addressable gem in Puppets Gemfile
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6894 Remove Ruby 1.9.3 related pinning of addressable gem in Puppets Gemfile Change By: Josh Cooper Sprint: Platform Core 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8483) Require ruby 2.3 or greater
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8483 Require ruby 2.3 or greater Change By: Josh Cooper Release Notes Summary: Puppet requires ruby 2.3 or greater. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6894) Remove Ruby 1.9.3 related pinning of addressable gem in Puppets Gemfile
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-6894
Remove Ruby 1.9.3 related pinning of addressable gem in Puppets Gemfile
Change By:
Josh Cooper
https://github.com/puppetlabs/puppet/pull/5362 was performed to fix issues running on Ruby 1.9.3 caused by the {{addressable}} gem. When 1.9.3 support is removed from Puppet, the {{addressable}} pin can be removed. Also ffi (PUP-8438) and win32-* (PUP-6445)
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8483) Require ruby 2.3 or greater
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8483 Require ruby 2.3 or greater Change By: Josh Cooper Summary: Update Require ruby and gem dependencies 2.3 or greater Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8483) Update ruby and gem dependencies
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8483 Update ruby and gem dependencies Change By: Josh Cooper Update Gemfile, .gemspec, ext/project_data.yaml so that we:1. Require puppet requires ruby 2. 0 3 or greater (or whatever minimum we decide on)2 . Update gem dependencies in cases where we are pinned to old versions for ruby 1.9.3 compatibility reasons, e.g. fast-gettext, addressable, ffi, etc Attempting to install puppet as a gem, running puppet via bundler, or running module tests using a local checkout of puppet should all fail when using ruby < 2. 3. 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.
Jira (PUP-8483) Update ruby and gem dependencies
Title: Message Title Josh Cooper commented on PUP-8483 Re: Update ruby and gem dependencies I'm going to mark this as resolved since Patrick Carlisle already bumped the minimum ruby version. Any gem dependency bumps can be handled in PUP-6894. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8484) Update ruby 1.9.3 code paths
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8484 Update ruby 1.9.3 code paths Change By: Josh Cooper Sprint: Platform Core 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8767) --config_version option to `puppet apply` leads to ruby-specific lastrun YAML
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8767 --config_version option to `puppet apply` leads to ruby-specific lastrun YAML Change By: Josh Cooper Release Notes Summary: When config_version refers to an external program, the last run summary no longer includes the puppet-specific class name in the YAML output, to ensure interoperability with other programs. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8767) --config_version option to `puppet apply` leads to ruby-specific lastrun YAML
Title: Message Title Josh Cooper commented on PUP-8767 Re: --config_version option to `puppet apply` leads to ruby-specific lastrun YAML Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/a5825b4050c71c3cdd10367c3c6a4473f0ad5e2d Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8571) Extract mailalias type/provider into a module
Title: Message Title Josh Cooper commented on PUP-8571 Re: Extract mailalias type/provider into a module Melissa Stone could you add release notes and resolve as all of the subtasks are complete? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8572) Extract maillist type/provider into a module
Title: Message Title Josh Cooper commented on PUP-8572 Re: Extract maillist type/provider into a module Melissa Stone could you add release notes and resolve as all of the subtasks are complete? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-258) Puppet Strings for puppetlabs-ibm_installation_manager
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-258 Puppet Strings for puppetlabs-ibm_installation_manager Issue Type: Task Assignee: Unassigned Created: 2018/06/05 3:21 PM Priority: Normal Reporter: Eric Putnam Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDOC-257) Puppet Strings for puppetlabs-websphere_application_server
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-257 Puppet Strings for puppetlabs-websphere_application_server Issue Type: Task Assignee: Unassigned Created: 2018/06/05 3:20 PM Priority: Normal Reporter: Eric Putnam 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
Jira (PUP-7761) New users with null passwords not created correctly
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7761 New users with null passwords not created correctly Change By: Josh Cooper Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8907) User Type/Provider Improvements
Title: Message Title Josh Cooper created an issue Puppet / PUP-8907 User Type/Provider Improvements Issue Type: Epic Assignee: Unassigned Created: 2018/06/05 2:59 PM Priority: Normal Reporter: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8897) check_manage_home useradd provider needs to add -M on Debian
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8897 check_manage_home useradd provider needs to add -M on Debian Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3931) (docs) Add 5.2.3 release notes
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3931 (docs) Add 5.2.3 release notes Issue Type: Bug Assignee: Unassigned Created: 2018/06/05 2:44 PM Priority: Normal Reporter: gepetto-bot No tickets in PDB 5.2.3 are marked as requiring release notes, so in lieu of notes I'm linking to the JIRA search for issues with that fixVersion. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8906) Improve CRL error messages/handling
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8906 Improve CRL error messages/handling Change By: Maggie Dreyer Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8906) Improve CRL error messages/handling
Title: Message Title Maggie Dreyer moved an issue Puppet / PUP-8906 Improve CRL error messages/handling Change By: Maggie Dreyer Key: SERVER PUP - 2207 8906 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-563) Improve parameter name consistency when specifying a "token" or "token-file" for bolt / puppetdb
Title: Message Title Yasmin Rajabi moved an issue Puppet Task Runner / BOLT-563 Improve parameter name consistency when specifying a "token" or "token-file" for bolt / puppetdb Change By: Yasmin Rajabi Key: PE BOLT - 24295 563 Project: Puppet Enterprise [Internal] Task Runner Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8905) New certificate download code breaks autosigning workflow
Title: Message Title Maggie Dreyer commented on PUP-8905 Re: New certificate download code breaks autosigning workflow This occurs because we actually create two SSL::Host objects during bootstrap, one at the start of the agent run to represent the agent in question, and a persistent localhost representing the same, that is lazily created and then used when validating HTTP connections, see https://github.com/puppetlabs/puppet/blob/master/lib/puppet/ssl/validator/default_validator.rb#L114. localhost is created the first time the indirector tries to make an HTTP request to check the CAs SSL record for this host, and as part of its creation sets up the hosts certs, which the host object from the agent run then sees and uses. Before the recent code changes, this first HTTP request occurred as part of this call to certificate: https://github.com/puppetlabs/puppet/blob/5.3.x/lib/puppet/ssl/host.rb#L329. But now that we have replaced the internals of the certificate method to avoid the indirector, the setup done by localhost occurs during the call to generate on the line below instead, here https://github.com/puppetlabs/puppet/blob/5.3.x/lib/puppet/ssl/host.rb#L231. However, apparently the submission of a CSR during an indirection.find for it does not actually return said CSR, so existing_request stays nil, and later on in the call to generate we issue another request, which the server rejects, issuing the error above. Note that in all of this, no actual inconsistent state occurs, and the autosigned cert was downloaded as part of the implicit initialization by localhost, so the agent actually ends fully initialized and further runs work correctly. The simplest fix is simply to re-check for a signing request, e.g. changing this line https://github.com/puppetlabs/puppet/blob/5.3.x/lib/puppet/ssl/host.rb#L252 to say "certificate_request" instead of "exising_request". However, that only really obfuscates the problem further, so I am going to look into not using the indirector to manage signing requests, similar to what we have done with certs and CRLs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-489) I want to know what OS bolt is being run from
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-489 I want to know what OS bolt is being run from Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-544) PuppetDB integration should work out-of-the-box with PE
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-544 PuppetDB integration should work out-of-the-box with PE Change By: Michael Smith 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-488) I would like to know how often subcommands in bolt are run
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-488 I would like to know how often subcommands in bolt are run Change By: Michael Smith 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7407 Add deprecation warning to Puppet::Util.absolute_path? Change By: Jorie Tappa Sprint: Agent 2017-04-19, Platform Core Hopper 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-534) Bolt hangs when no sudo password is provided
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-534 Bolt hangs when no sudo password is provided Change By: Michael Smith Assignee: Michael 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.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8484) Update ruby 1.9.3 code paths
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8484 Update ruby 1.9.3 code paths Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-547) Finish plans when using the pcp transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-547 Finish plans when using the pcp transport Change By: Alex Dreyer currently Currently bolt does not finish plans to avoid unnecessary error logging with ORCH-2224 This work is blocked on the PE 2018 . 1.1 release or Bolt should be feature flagged instead try to finish plans and log at debug level if that fails . This work should be tested by updating the orchestrator acceptance tests. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-548) Generate function reference docs for core plan language functions automatically
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-548 Generate function reference docs for core plan language functions automatically Change By: David Kramer Sub-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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-547) Finish plans when using the pcp transport
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-547 Finish plans when using the pcp transport Change By: David Kramer 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-523) I want to install modules with bolt
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-523 I want to install modules with bolt Change By: David Kramer Currently bolt does not ship with any tool to install modules. This means users need to install the puppet agent package or r10k into some ruby (we don't make it easy to install into bolts). This is especially a problem for users getting started with bolt who quickly have to find, install and use a completely different tool.Assumptions:1. pmt is too broken an unmaintained to add support for2. Puppetfile based installations are good enough for users getting started if we point them at a basic control repo (task-modules)3. Bolt users do not need the sort of global configuration of a remote control repo and syncing of multiple branches that makes sense on a puppet master.4. r10k is cryptic a cryptic command name and should be hidden from new users. Solution:Bolt should be packaged with the r10k gem but not expose the r10k commandBolt should expose a command to install modules from a puppetfile such that downloading a control repo and installing locally is easy.Bolt should use a puppetfile from the Boltdir and install into the Boltdir when in Boltdir mode. Questions:What should the command be? `bolt puppetfile install` `bolt puppetfile install --boltdir=.` Should bolt become more opinionated on where code lives outside of the context of a boltdir? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-131) Simplify tasks for repeatable code and importing code
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-131 Simplify tasks for repeatable code and importing code Change By: Lucy Wyman Epic Name: Sharable Shareable task 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-490) I want to know what transports are being used
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-490 I want to know what transports are being used Change By: David Kramer 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-489) I want to know what OS bolt is being run from
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-489 I want to know what OS bolt is being run from Change By: David Kramer 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-491) I want to know how many targets are present in bolt
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-491 I want to know how many targets are present in bolt Change By: David Kramer 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-562) I want to know how many targets are present in my inventory file
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-562 I want to know how many targets are present in my inventory file Change By: David Kramer 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-491) I want to know how many targets are present in bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-491 I want to know how many targets are present in bolt Change By: Alex Dreyer how many unique targets are they running on in a single bolt execution.When a bolt execution finishes bolt should send a summary of how many nodes were acted on. We should be able to gather that information from the inventory since everything targeted should have been initialized in the inventory(and untargeted nodes shouldn't?) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-562) I want to know how many targets are present in my inventory file
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-562 I want to know how many targets are present in my inventory file Change By: Yasmin Rajabi how many unique targets are they running on present in the inventory file Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-562) I want to know how many targets are present in my inventory file
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-562 I want to know how many targets are present in my inventory file Change By: Yasmin Rajabi 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-562) I want to know how many targets are present in my inventory file
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-562 I want to know how many targets are present in my inventory file Issue Type: Story Assignee: Unassigned Created: 2018/06/05 9:41 AM Priority: Normal Reporter: Yasmin Rajabi how many unique targets are they running on Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-490) I want to know what transports are being used
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-490 I want to know what transports are being used Change By: Alex Dreyer in scope: if user is using transportout of scope: how often per userWe want to track how commonly each should send an event the first time a given transport is used , so including the number of users using a particular transport tid. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-490) I want to know what transports are being used
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-490 I want to know what transports are being used Change By: Lucy Wyman in scope: if user is using transportout of scope: how often per user We want to track how commonly each transport is used, so the number of users using a particular transport Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-489) I want to know what OS bolt is being run from
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-489 I want to know what OS bolt is being run from Change By: Alex Dreyer operatingsystem > and operating system version I want to know if its paid redhat, free linux, windows, etc. and what version. - This should be discovered via ruby logic. Should we load facter or just copy paste facter logic? How slow is loading facter? We don't really care about unsupported operating systems probably- This should be a custom dimension assigned in the analytics class. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (BOLT-489) I want to know what OS bolt is being run from
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-489 I want to know what OS bolt is being run from Change By: Alex Dreyer operatingsystem > I want to know if its paid redhat, free linux, windows, etc. - This should be discovered via ruby logic. Should we load facter or just copy paste facter logic? How slow is loading facter? We don't really care about unsupported operating systems probably- This should be a custom dimension assigned in the analytics class. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-558) Add strings documentation to functions
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-558 Add strings documentation to functions Issue Type: Sub-task Assignee: Unassigned Created: 2018/06/05 9:22 AM Priority: Normal Reporter: Alex Dreyer All the functions in boltlib should have strings documenation following the strings style guide Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-561) Update 'writing plans' documentation to remove duplicated docs
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-561 Update 'writing plans' documentation to remove duplicated docs Issue Type: Sub-task Assignee: Unassigned Created: 2018/06/05 9:27 AM Priority: Normal Reporter: Lucy Wyman Creating reference docs will mean some info is duplicated from the writing plans docs. These should now link to reference docs instead and duplicated content should be removed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-560) (DOCS) Explore importing JSON documentation to DITA
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-560 (DOCS) Explore importing JSON documentation to DITA Issue Type: Sub-task Assignee: Unassigned Created: 2018/06/05 9:25 AM Priority: Normal Reporter: Lucy Wyman Explore how to import the Puppet Strings generated reference to DITA Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-559) Create rake task to generate reference documentation
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-559 Create rake task to generate reference documentation Issue Type: Sub-task Assignee: Unassigned Created: 2018/06/05 9:25 AM Priority: Normal Reporter: Lucy Wyman Create a rake task which will output both a JSON reference file as well as markdown documentation to be included in the in-repo documentation Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-489) I want to know what OS bolt is being run from
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-489 I want to know what OS bolt is being run from Change By: David Kramer osfamily operatingsystem > I want to know if its paid redhat, free linux, windows, etc. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-548) Generate function reference docs for core plan language functions automatically
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-548 Generate function reference docs for core plan language functions automatically Change By: Alex Dreyer Reference information about the plan language should be autogenerated with puppet strings.In scope: - Update plan language functions in boltlib to have strings based documentation - -Create a skeleton template(s) for documentation pages-(just output json) - Create rake task to generate docs - -Update templates to DITA (kate)- Explore import to DITA - Update writing plans page to include less reference info and linksOut of scope: - reference docs for datatypes - reference docs for modules other than boltlibQuestions: - How should output be structured into files?(kate will explore) start with one page of json dumped - What templating language should we use?(no templates) - Do we need links in generated content (no since we're just using json) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You
Jira (BOLT-548) Generate function reference docs for core plan language functions automatically
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-548 Generate function reference docs for core plan language functions automatically Change By: Lucy Wyman Reference information about the plan language should be autogenerated with puppet strings.In scope: - Update plan language functions in boltlib to have strings based documentation - Create a skeleton template(s) for documentation pages(just output json) - Create rake task to generate docs - Update templates to DITA (kate) - Update writing plans page to include less reference info and linksOut of scope: - reference docs for datatypes - reference docs for modules other than boltlibQuestions: - How should output be structured into files? (kate will explore) start with one page of json dumped Single JSON file - What templating language should we use? (no templates) None - Do we need links in generated content None Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because
Jira (BOLT-548) Generate function reference docs for core plan language functions automatically
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-548 Generate function reference docs for core plan language functions automatically Change By: David Kramer Reference information about the plan language should be autogenerated with puppet strings.In scope: - Update plan language functions in boltlib to have strings based documentation - - Create a skeleton template(s) for documentation pages-(just output json) - Create rake task to generate docs - - Update templates to DITA (kate) - Explore import to DITA - Update writing plans page to include less reference info and linksOut of scope: - reference docs for datatypes - reference docs for modules other than boltlibQuestions: - How should output be structured into files? Single JSON file (kate will explore) start with one page of json dumped - What templating language should we use? None (no templates) - Do we need links in generated content None Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-548) Generate function reference docs for core plan language functions automatically
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-548 Generate function reference docs for core plan language functions automatically Change By: David Kramer 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-548) Generate function reference docs for core plan language functions automatically
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-548 Generate function reference docs for core plan language functions automatically Change By: Alex Dreyer Reference information about the plan language should be autogenerated with puppet strings.In scope: - Update plan language functions in boltlib to have strings based documentation - Create a skeleton template(s) for documentation pages (just output json) - Create rake task to generate docs - Update templates to DITA (kate) - Update writing plans page to include less reference info and linksOut of scope: - reference docs for datatypes - reference docs for modules other than boltlibQuestions: - How should output be structured into files? (kate will explore) start with one page of json dumped - What templating language should we use? (no templates) - Do we need links in generated content 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
Jira (BOLT-557) Pass _task parameter to tasks
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-557 Pass _task parameter to tasks Change By: Nick Lewis 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-557) Pass _task parameter to tasks
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-557 Pass _task parameter to tasks Issue Type: Task Assignee: Unassigned Created: 2018/06/05 9:07 AM Priority: Normal Reporter: Nick Lewis In order to allow a single executable to be used for multiple tasks, we need to provide information to the executable about which task is being invoked. Per the tasks spec, we should pass a _task parameter with the name of the task being invoked. This will allow the executable to vary its behavior based on which task it's providing. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-556) Submit puppet-specifications PR for multi-file tasks
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-556 Submit puppet-specifications PR for multi-file tasks Issue Type: Task Assignee: Unassigned Created: 2018/06/05 9:05 AM Priority: Normal Reporter: Alex Dreyer Before we plan work for shareable task code we need to gather feedback on the spec update. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8733) File type redefined when required in code
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8733 File type redefined when required in code Change By: Josh Cooper Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8733) File type redefined when required in code
Title: Message Title Josh Cooper commented on PUP-8733 Re: File type redefined when required in code Merged to puppet#master in https://github.com/puppetlabs/puppet/commit/a7ef7088f8df7e1fd61443ff144758c3d917a039 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3926) Find/fix integration test failures with agent/server master (2018-05-22)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3926 Find/fix integration test failures with agent/server master (2018-05-22) Change By: Rob Browning Reporter: Rob Reynolds Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3926) Find/fix integration test failures with agent/server master (2018-05-22)
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-3926 Find/fix integration test failures with agent/server master (2018-05-22) Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3926) Find/fix integration test failures with agent/server master (2018-05-22)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3926 Find/fix integration test failures with agent/server master (2018-05-22) Change By: Rob Browning Sprint: Hopper/Triage, Data Platform 2018-05-23 , Data Platform 2018-06-06 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3926) Find/fix integration test failures with agent/server master (2018-05-22)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3926 Find/fix integration test failures with agent/server master (2018-05-22) Change By: Rob Browning Reporter: Rob Browning Reynolds Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8901) Puppet5 server does not work with Puppet4 termini
Title: Message Title Jake Yip commented on PUP-8901 Re: Puppet5 server does not work with Puppet4 termini We are following Puppet docs at https://puppet.com/docs/puppet/5.3/upgrade_minor.html > Upgrade PuppetDB nodes independently of masters and agents. > When you upgrade PuppetDB, you must also upgrade the puppetdb-termini package on all Puppet masters. That is the same sequence we used when we upgraded from 3 to 4. Puppet Server, then PuppetDB, then Puppet agent. This is a reasonable upgrade path because we could bring up new Puppet 4 servers first, and switchover a few agents at a time to make sure Puppet 4 server works similarly to Puppet 3 server. After all agents are hitting the Puppet 4 servers we then upgraded the Puppet DB and termini. We have 8 load balanced servers and over 1600 agents handled by multiple teams. We would appreciate a minimal disruption upgrade path, and I am wary of the risk with a big bang upgrade (8 puppetservers and puppetdb and puppetdb-termini all at once). Also, I am not sure how we can roll back from such an upgrade? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8905) New certificate download code breaks autosigning workflow
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8905 New certificate download code breaks autosigning workflow Change By: Maggie Dreyer Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8905) New certificate download code breaks autosigning workflow
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-8905 New certificate download code breaks autosigning workflow Issue Type: CI Blocker Assignee: Unassigned Created: 2018/06/05 8:32 AM Priority: Normal Reporter: Maggie Dreyer Autosigning appears to be broken with the new certificate download code (PUP-8652). When using an autosigning workflow, the first agent run fails with Error: Could not request certificate: Error 400 on SERVER: pto1to2xvyajwdw.delivery.puppetlabs.net already has a signed certificate; ignoring certificate request It seems that the agent is re-submitting a CSR even though it has successfully downloaded the signed host certificate. This could be related to some weird interaction between remaining indirector code and the code. This issue appears to be affecting both Puppetserver's beaker acceptance tests (whose pre-suites use autosigning to set up their environment) and PuppetDB's clojure integration tests.
Jira (PUP-8905) New certificate download code breaks autosigning workflow
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-8905 New certificate download code breaks autosigning workflow Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-577) Standalone `hiera` command errors with hiera v5 config file
Title: Message Title
Martin Ewings updated an issue
Hiera / HI-577
Standalone `hiera` command errors with hiera v5 config file
Change By:
Martin Ewings
*Overview*Sometimes you need to use the standalone {{hiera}} command to debug a hierarchy when working with tools such as {{onceover}} or when setting up a whole {{puppet lookup}} environment is impractical.If this is attempted using the {{hiera}} command shipped in puppet-agent-1.10.5-1.el7.x86_64.rpm user will always encounter a confusing error if {{version}} is set to {{> 3}} in the {{hiera.yaml}} file*Expected result*Expect to be able to lookup data item on the command line using {{hiera}} command and hiera v5 config file*Actual result*User receives the error:{noformat} Failed to start Hiera: RuntimeError: v4 hiera.yaml is only to be used inside an environment or a module and cannot be given to the global hiera{noformat} *Steps to reporoduce*1. Hiera.yaml{noformat} ---version: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Common data"path: "common.yaml"{noformat} 2. Lookup data as users:{noformat} hiera -c hiera.yaml ruh::rohFailed to start Hiera: RuntimeError: v4 hiera.yaml is only to be used inside an environment or a module and cannot be given to the global hiera{noformat} *Analysis*The error message seems to indicate that the hiera configuration file uses the old v4 format but it doesn't, its definitely version 5 and works fine with {{puppet lookup}} if dropped into the correct directory. Looking at the sourcecode, versions > 3 will allways encounter this error and Indeed the error can be cleared by declaring {{version: 3}} in the {{hiera.yaml}} file. I didn't check if this 'trick' still lets you work with hiera 5 functionality and wouldn't recommend it.*Workarounds*Setup the system to use {{puppet lookup}} \ (?)*Desired fix*I'm not sure what is supposed to happen here. I understand that hiera is now part of puppet but where does this leave the standalone hiera command? Is it intended to work at all? Is it deprecated in favour of {{puppet lookup}}? Is it only intended to work with {{hiera.yaml}} files v3 and earlier? Would be great to get some clarity around these issues as the error message about v4 configuration files is confusing when file is already in v5 format.
Jira (PUP-8893) external, executable facts via pluginsync get executable flag removed
Title: Message Title Martin Alfke commented on PUP-8893 Re: external, executable facts via pluginsync get executable flag removed Checked using PE 2018.1 and facts.d plugin sync is working as expected. I try to get back to customer and verify on their setup. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8893) external, executable facts via pluginsync get executable flag removed
Title: Message Title Martin Alfke commented on PUP-8893 Re: external, executable facts via pluginsync get executable flag removed Executable bit is set in GIT - I confirmed this prior opening the ticket. I have to verify whether executable bit after code manager deployment is set. Unluckily my contact at the potential PE customer seems to have left. I need to verify the issue at another installation. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
