Jira (BOLT-656) Bypass batching and threading for bolt-server
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-656 Bypass batching and threading for bolt-server Change By: Michael Smith Summary: [SPIKE] Can we bypass Bypass batching and threading in the for bolt executor? -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-656) Bypass batching and threading for bolt-server
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-656 Bypass batching and threading for bolt-server 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-9028) Create a `puppet ssl` subcommand that can perform SSL client actions on the agent
Title: Message Title Melissa Stone commented on PUP-9028 Re: Create a `puppet ssl` subcommand that can perform SSL client actions on the agent This has passed ci as a part of puppet-agent 5.99.2.314.g3ae6d1e Jacob Helwig what's happening with the sub-tasks on this ticket? It looks like the ssl application has all the utilities outlined in the sub-tasks, so it looks like those can be closed when this main ticket gets closed 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-656) [SPIKE] Can we bypass batching and threading in the bolt executor?
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-656 [SPIKE] Can we bypass batching and threading in the bolt executor? Change By: Michael Smith 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-656) [SPIKE] Can we bypass batching and threading in the bolt executor?
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-656 [SPIKE] Can we bypass batching and threading in the bolt executor? 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-9141) Ability to destroy multiple CSRs at once
Title: Message Title Daniel Parks updated an issue Puppet / PUP-9141 Ability to destroy multiple CSRs at once Change By: Daniel Parks Labels: customer0 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-9141) Ability to destroy multiple CSRs at once
Title: Message Title
Daniel Parks created an issue
Puppet / PUP-9141
Ability to destroy multiple CSRs at once
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/09/14 2:50 PM
Priority:
Normal
Reporter:
Daniel Parks
It would be super helpful to be able to destroy multiple pending certs at once, for example:
sudo puppet ca destroy bad-host.example.net other-bad-host.example.net
We end up getting a lot of bad CSRs, and it would be very expensive to fix on the other end. We currently have 450+. I end up dong things like:
sudo puppet ca list | awk '/bad-host/ {print$1}' | xargs -n 1 sudo puppet ca destroy
Jira (BOLT-643) Add apply functionality to bolt_shim
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-643 Add apply functionality to bolt_shim 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 (PUP-8601) agent should support rich data content negotiation
Title: Message Title Patrick Carlisle updated an issue Puppet / PUP-8601 agent should support rich data content negotiation Change By: Patrick Carlisle Release Notes Summary: The `rich_data` setting is now enabled by default. Catalog requests have two new content-types, `application/vnd.puppet.rich+json` and `application/vnd.puppet.rich+msgpack`, that are used when both master and agent have this enabled (and depending on whether `preferred_serialization_format` is `json` or `msgpack`). Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-834) Support Puppet 6 Windows locations for ruby.exe and puppet/facter libs
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-834
Support Puppet 6 Windows locations for ruby.exe and puppet/facter libs
Change By:
Michael Smith
Puppet 6 rearranged file locations on Windows: https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md#puppet-agent-6-windows. We need to update https://github.com/puppetlabs/bolt/blob/0.22.0/lib/bolt/transport/winrm/connection.rb#L101-L106 so that* {{PATH}} includes {{C:\Program Files\Puppet Labs\Puppet\puppet\bin}}* {{RUBYLIB}} may need to be updated, or may be automatically setup by ruby. We need to add tests against Puppet 6.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-9053) Enable localizations for extracted modules
Title: Message Title Melissa Stone commented on PUP-9053 Re: Enable localizations for extracted modules This doesn't need ci, but I do want to check up on the module pipelines (especially if there are any module changes that go in), to check on if the i18n jobs are actually working 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-9094) Switch rest client back to using Puppet::Network::HttpPool
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9094 Switch rest client back to using Puppet::Network::HttpPool Change By: Melissa Stone Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9053) Enable localizations for extracted modules
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9053 Enable localizations for extracted modules Change By: Melissa Stone Release Notes Summary: We are now doing translations for extracted modules Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8836) Remove type/provider code from puppet
Title: Message Title Melissa Stone commented on PUP-8836 Re: Remove type/provider code from puppet This passed ci as of puppet-agent 5.99.2.314.g3ae6d1e, though probably earlier 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-5985) Features are not being re-evaluated when a block is used
Title: Message Title Melissa Stone commented on PUP-5985 Re: Features are not being re-evaluated when a block is used This passed ci as of puppet-agent 5.99.2.314.g3ae6d1e, though probably earlier 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-828) Fix race condition in Logging.logger
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-828 Fix race condition in Logging.logger Change By: Kate Lopresti Labels: feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-828) Fix race condition in Logging.logger
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-828 Fix race condition in Logging.logger Change By: Kate Lopresti Labels: feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3470) Add pdb sandboxing infrastructure, and use it in travis
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3470 Add pdb sandboxing infrastructure, and use it in travis Change By: Zachary Kent Fix Version/s: PDB 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 (PDB-3490) Get rbac-client version from clj-parent in pdbext
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3490 Get rbac-client version from clj-parent in pdbext Change By: Zachary Kent Fix Version/s: PDB 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 (PDB-4008) Use jruby-gem-list for all version
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4008 Use jruby-gem-list for all version Change By: Zachary Kent Fix Version/s: PDB 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 (PDB-3934) Determine deprecations, if any for pdb 6
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3934 Determine deprecations, if any for pdb 6 Change By: Zachary Kent Fix Version/s: PDB 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 (PDB-3940) Investigate clojure 1.9 support
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3940 Investigate clojure 1.9 support Change By: Zachary Kent Fix Version/s: PDB 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 (PDB-4089) Investigate voom/ezbake jobs needing hard coded project versions
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4089 Investigate voom/ezbake jobs needing hard coded project versions Issue Type: Task Assignee: Unassigned Created: 2018/09/14 11:03 AM Priority: Normal Reporter: Zachary Kent It looks like voom/ezbake expect there to be hardcoded project versions in project.clj. See if it is possible to change this so that we can use a file instead. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9053) Enable localizations for extracted modules
Title: Message Title Melissa Stone commented on PUP-9053 Re: Enable localizations for extracted modules PR ready for merge: https://github.com/puppetlabs/ci-job-configs/pull/4966 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-9110) Accept and produce ASCII_8BIT as Binary value
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9110 Accept and produce ASCII_8BIT as Binary value Change By: Henrik Lindberg Release Notes Summary: We did not quite finish the support for the Binary data type in time for 6.0.0. Before you start to use Binary in your manifests for anything except File content, you should be aware of the ticket PUP-9110 as it could introduce changes that may affect you. 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-9110) Accept and produce ASCII_8BIT as Binary value
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9110 Accept and produce ASCII_8BIT as Binary value We did not quite finish the support for the Binary data type in time for 6.0.0. Before you start to use Binary in your manifests for anything except File content, you should be aware of the ticket PUP-9110 as it could introduce changes that may affect you. Change By: Henrik Lindberg Release Notes: Known Issue 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-9125) Prepare release announcement (Puppet Platform 6.0.0)
Title: Message Title Michelle Fredette commented on PUP-9125 Re: Prepare release announcement (Puppet Platform 6.0.0) Henrik Lindberg can you please add the release note to that 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-646) Migrate bolt_catalog to use PAL
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-646 Migrate bolt_catalog to use PAL Change By: Lucy Wyman Assignee: Lucy Wyman 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-658) Validate JSON data in bolt-transport-api requests
Title: Message Title Lucy Wyman assigned an issue to Nick Lewis Puppet Task Runner / BOLT-658 Validate JSON data in bolt-transport-api requests Change By: Lucy Wyman Assignee: Lucy Wyman 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 (PUP-9140) File resource checksum => mtime fails with empty mtime
Title: Message Title
Francois Isabelle created an issue
Puppet / PUP-9140
File resource checksum => mtime fails with empty mtime
Issue Type:
Bug
Affects Versions:
PUP 5.3.7
Assignee:
Unassigned
Components:
Puppet Server
Created:
2018/09/14 5:41 AM
Environment:
This server is a CentOS 7.4.1708 machine running Puppet Server 5.3.7 with Ruby 2.4.4. The client is Puppet 5.5.2.
Priority:
Normal
Reporter:
Francois Isabelle
In order to improve performance for large binary files I have been using File resources with the checksum type set to 'mtime' for a while and I was satisfied with it . But apparently, this does not always work. On a different system, I keep getting : Error: File written to disk did not match checksum; discarding changes ({mtime} vs {mtime}Thu Sep 13 16:19:24 -0400 2018) As if the mtime on the server could not be compute. This seemed like a bug.
Jira (PUP-9139) Package provider apt fails when installing from local file
Title: Message Title Dirk Heinrichs updated an issue Puppet / PUP-9139 Package provider apt fails when installing from local file Change By: Dirk Heinrichs *Puppet Version: 4.10* *Puppet Server Version: 2.8.1* *OS Name/Version: Ubuntu 16.04*apt-get is able to install packages from locally stored .deb files (apt-get install /path/to/package), resolving dependencies as usual. However, the apt package provider doesn't seem to support this, which enforces the use of the dpkg provider. Unfortunately, this provider doesn't do depenedency dependency resolution (since dpkg itself can't do that).*Desired Behavior:*Installing a from a local package file with the apt provider should just work.*Actual Behavior:*apt provider fails when trying to install from a local 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
Jira (PUP-9139) Package provider apt fails when installing from local file
Title: Message Title Dirk Heinrichs created an issue Puppet / PUP-9139 Package provider apt fails when installing from local file Issue Type: New Feature Assignee: Unassigned Created: 2018/09/14 3:54 AM Priority: Normal Reporter: Dirk Heinrichs Puppet Version: 4.10 Puppet Server Version: 2.8.1 OS Name/Version: Ubuntu 16.04 apt-get is able to install packages from locally stored .deb files (apt-get install /path/to/package), resolving dependencies as usual. However, the apt package provider doesn't seem to support this, which enforces the use of the dpkg provider. Unfortunately, this provider doesn't do depenedency resolution (since dpkg itself can't do that). Desired Behavior: Installing a from a local package file with the apt provider should just work. Actual Behavior: apt provider fails when trying to install from a local file. Add Comment
Jira (PUP-9121) puppet apply --catalog cat.json does not trigger resolution of Deferred values
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-9121 puppet apply --catalog cat.json does not trigger resolution of Deferred values Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9121) puppet apply --catalog cat.json does not trigger resolution of Deferred values
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9121 puppet apply --catalog cat.json does not trigger resolution of Deferred values Change By: Henrik Lindberg 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-9125) Prepare release announcement (Puppet Platform 6.0.0)
Title: Message Title Henrik Lindberg commented on PUP-9125 Re: Prepare release announcement (Puppet Platform 6.0.0) Since PUP-9110 did not go in, it should be listed as a known issue. That to allow us to treat that as a bug and fix in 6.0.1 - it could otherwise be seen as a breaking change. 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-838) Bolt debug output is not helpful
Title: Message Title
Dylan Ratcliffe updated an issue
Puppet Task Runner / BOLT-838
Bolt debug output is not helpful
Change By:
Dylan Ratcliffe
The debug output for bolt is very noisy but doesn't say much about what bolt is actually doing, for example once a task completes bolt hangs for 2-3 seconds before exiting, what is it doing? There is no debug output at all, when using PCP we get a message when the orchestration client is created, but nothing about what request was submitted, what the response was, what follow-up requests are being submitted. Here is some example debug output with timestamps to show what could be improved:{code}[root@pe-201813-master ~]# bolt task run service --nodes pe-201813-master.puppetdebug.vlan --params @params.json --transport pcp --debug --configfile .puppetlabs/bolt.yaml 2>&1 | gawk '{ print strftime("[%H:%M:%S]"), $0 }'[06:08:36] Could not read inventory file: /root/.puppetlabs/inventory.yaml[06:08:36] Did not find config for pe-201813-master.puppetdebug.vlan in inventory[06:08:36] Submitting analytics: {[06:08:36] "v": 1,[06:08:36] "cid": "b8322956-1f52-4830-9a87-bb3367c4b213",[06:08:36] "tid": "UA-120367942-1",[06:08:36] "an": "bolt",[06:08:36] "av": "0.21.8",[06:08:36] "aip": true,[06:08:36] "ul": "en-AU",[06:08:36] "cd1": "CentOS 7",[06:08:36] "t": "screenview",[06:08:36] "cd": "task_run",[06:08:36] "cd5": "human",[06:08:36] "cd4": 1,[06:08:36] "cd2": 0,[06:08:36] "cd3": 1[06:08:36] }## What was it doing for these 5 seconds?[06:08:41] Completed analytics submission## And these 56 seconds?[06:09:37] ModuleLoader: module 'aggregate' has unknown dependencies - it will have all other modules visible[06:09:37] ModuleLoader: module 'canary' has unknown dependencies - it will have all other modules visible[06:09:37] ModuleLoader: module 'facts' has unknown dependencies - it will have all other modules visible[06:09:37] ModuleLoader: module 'puppetdb_fact' has unknown dependencies - it will have all other modules visible[06:09:37] Started with 10 max thread(s)[06:09:37] ModuleLoader: module 'boltlib' has unknown dependencies - it will have all other modules visible[06:09:37] Did not find config for pe-201813-master.puppetdebug.vlan in inventory[06:09:37] Starting: task service on pe-201813-master.puppetdebug.vlan[06:09:37] Submitting analytics: {[06:09:37] "v": 1,[06:09:37] "cid": "b8322956-1f52-4830-9a87-bb3367c4b213",[06:09:37] "tid": "UA-120367942-1",[06:09:37] "an": "bolt",[06:09:37] "av": "0.21.8",[06:09:37] "aip": true,[06:09:37] "ul": "en-AU",[06:09:37] "cd1": "CentOS 7",[06:09:37] "t": "event",[06:09:37] "ec": "Bundled Content",[06:09:37] "ea": "Task",[06:09:37] "el": "service"[06:09:37] }## Why do we need to submit analytics so often? And why do we need to print the whole hash?[06:09:37] Running task service with '{"action"=>"status", "name"=>"puppet", "_task"=>"service"}' via on ["pe-201813-master.puppetdebug.vlan"][06:09:37] Creating orchestrator client for
