Jira (PDB-3912) Fix pdbext dependency version mismatches with pdb 5.1.x
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3912 Fix pdbext dependency version mismatches with pdb 5.1.x Change By: Rob Browning Summary: Fix pdbext dependency version mismatches with pdb 5.1.x 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-3912) Fix 5.1.x dependency version mismatches between pdb and pdbext
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3912 Fix 5.1.x dependency version mismatches between pdb and pdbext Change By: Rob Browning Summary: Fix pdbext dependency version mismatches with pdb 5.1.x dependency version mismatches between pdb and pdbext 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-7238) Yum package provider should support reinstall
Title: Message Title Edwin Wiles commented on PUP-7238 Re: Yum package provider should support reinstall I'm curious, why is this not yet fixed? I looked at 6735 and 8157, and there doesn't appear to be any explanation as to why this issue has not been fixed; just a comment in 8157 that it was removed from the epic. What am I missing? Thanks! 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-507) Build and ship Bolt for SLES 15 x86_64
Title: Message Title Geoff Nichols updated an issue Puppet Task Runner / BOLT-507 Build and ship Bolt for SLES 15 x86_64 Change By: Geoff Nichols Team: Direct 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 (PDB-3314) Create an activemq queue extraction tool
Title: Message Title Rob Browning commented on PDB-3314 Re: Create an activemq queue extraction tool OK, thanks. I'll close it for now, and we can always reopen it later if 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 (FACT-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd
Title: Message Title Geoff Nichols commented on FACT-1851 Re: Linux networking resolver doesn't collect DHCP information under systemd-networkd Merged to facter#3.11.x at https://github.com/puppetlabs/facter/commit/b247279eb9fad100248268baccc68330dc23d6e5. 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-503) Use local config automatically to embed bolt in a project
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-503
Use local config automatically to embed bolt in a project
Change By:
Alex Dreyer
I want to use bolt as a tool to manage my applications including everything needed with the application repo itself.Currently this is possible by including {{bolt.yaml}} at the top level of your project, in {{bolt.yaml}} point to a modules an inventory inside the project repo. But then every command needs to be run with {{--config=$PROJECT_PATH/bolt.yaml}}.New features:When bolt runs it should search the {{cwd}} and its ancestors for a file directory called {{ Boltfile bolt }}. If one is found it should use that as the bolt config and default modules and inventory to be inside the directory bolt next to the {{ Boltfile Boltdir }}.Add a new {{bolt boltd init}} command that creates an empty Boltfile and a bolt directory with empty {{inventory}} and {{modules}} directory and an empty {{Puppetfile}}.Add a new {{bolt boltd install}} command that installs the {{Puppetfile}} . {{bolt install }} should accept the path to a puppetfile and install it. Questions:Should we use {{Boltfile}} and bolt or {{Bolt.d}}? bolt.d the directory should be called {{Boltdir}} Should we merge in any of the global config? NoShould we fall back to global inventory if there isn't local inventory?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-508) Clean up CLIErrors
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-508 Clean up CLIErrors 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-508) Clean up CLIErrors
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-508 Clean up CLIErrors Change By: Alex Dreyer We create CLIErrors a lot of places where it doesn't really make sense. We should convert those to Bolt::Error or a more appropriate subclass of it. - CLIError should only be thrown from the CLI class and only for things that can only happen at the CLI level not deep in a plan(for example plan/task not found)- We should have a special error class for unexpected puppet preformatted errors.- We should have a special error class for missing files.- In general we should have a class for anything it would make sense for an automated caller to handle specially. 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
Jira (BOLT-465) Publish Bolt to Homebrew Cask
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-465 Publish Bolt to Homebrew Cask 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-464) Publish Bolt to chocolatey.org
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-464 Publish Bolt to chocolatey.org 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-380) Support ed25519 out-of-the-box
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-380 Support ed25519 out-of-the-box 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-398) Lookup/Hiera spike
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-398 Lookup/Hiera spike Change By: David Kramer 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-461) Rename bolt package to puppet-bolt
Title: Message Title Lucy Wyman commented on BOLT-461 Re: Rename bolt package to puppet-bolt I was able to successfully install the bolt package on ubuntu 16.04 but not the puppet-bolt package. It looks like puppet-bolt got put into the bolt directory? 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-485) Bolt canary plan is a success even when it skips nodes
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-485 Bolt canary plan is a success even when it skips nodes Change By: Alex Dreyer Release Notes Summary: The canary plan will now fail if the action fails on any target node. 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 (BOLT-485) Bolt canary plan is a success even when it skips nodes
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-485 Bolt canary plan is a success even when it skips nodes Change By: Alex Dreyer 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-484) Default transport cannot be configured from bolt.yaml
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-484 Default transport cannot be configured from bolt.yaml Change By: Alex Dreyer 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-462) Function to query puppetdb from plans.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-462 Function to query puppetdb from plans. Change By: Alex Dreyer 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-8585) puppet device --resource should fail if non-existent target is given
Title: Message Title
Thomas Honey updated an issue
Puppet / PUP-8585
puppet device --resource should fail if non-existent target is given
Change By:
Thomas Honey
*Puppet Version:**Puppet Server Version:**OS Name/Version:*Describe your issue in as much detail as possible…Describe steps to reproduce…*Desired Behavior:**Actual Behavior:*Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.Examples:Run puppet agent with --test --trace --debugRelevant sections of {{/var/log/puppetlabs/puppetserver/puppetserver.log}} or any applicable logs from the same directory.For more detailed information turn up the server logs by upping the log level in the server's logback.xmlRelevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig)For memory issues with server heap dumps are also helpful.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message
Jira (PUP-8585) puppet device --resource should fail if non-existent target is given
Title: Message Title Thomas Honey updated an issue Puppet / PUP-8585 puppet device --resource should fail if non-existent target is given Change By: Thomas Honey The error message is not displayed unless --debug is passed. 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-8701) Update to Puppet help in PUP-8646 removed 'help easter egg'; please put it back!
Title: Message Title Thomas Kishel commented on PUP-8701 Re: Update to Puppet help in PUP-8646 removed 'help easter egg'; please put it back! https://forge.puppet.com/binford2k/easter_egg 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-4380) Split non-core puppet functionality into modules
Title: Message Title Kenn Hussey assigned an issue to Josh Cooper Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Kenn Hussey 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 (PUP-7877) Future Work for Intermediate CA Improvements
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7877 Future Work for Intermediate CA Improvements Change By: Kenn Hussey Due Date: 2018/06/ 20 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 (PUP-6893) Remove Ruby 1.9.3 support
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6893 Remove Ruby 1.9.3 support Change By: Kenn Hussey Due Date: 2018/06/ 20 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 (PUP-8503) Agent SSL CLI
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8503 Agent SSL CLI Change By: Kenn Hussey Due Date: 2018/06/ 20 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 (PUP-8703) Numeric('0') raises an error
Title: Message Title
Thomas Hallgren commented on PUP-8703
Re: Numeric('0') raises an error
Merged to 5.5.x at 3b737c4.
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-8703) Numeric('0') raises an error
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-8703
Numeric('0') raises an error
Issue Type:
Bug
Assignee:
Henrik Lindberg
Created:
2018/05/08 6:02 AM
Fix Versions:
PUP 5.5.z
Priority:
Normal
Reporter:
Henrik Lindberg
The Numeric data type when given the string "0" will fail because it attempts to look at the second char in the string - if it is a downcased 'b' or 'x' - and this fails since there is nothing to downcase.
Add Comment
This message was sent by Atlassian JIRA
Jira (PUP-8585) puppet device --resource should fail if non-existent target is given
Title: Message Title Thomas Honey assigned an issue to Thomas Honey Puppet / PUP-8585 puppet device --resource should fail if non-existent target is given Change By: Thomas Honey Assignee: Thomas Honey 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-8701) Update to Puppet help in PUP-8646 removed 'help easter egg'; please put it back!
Title: Message Title Adam Buxton updated an issue Puppet / PUP-8701 Update to Puppet help in PUP-8646 removed 'help easter egg'; please put it back! Change By: Adam Buxton Attachment: adam-buxton.pdf 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-602) Migrate gemspec info in project_data.yaml to the .gemspec file
Title: Message Title Enis Inan updated an issue Hiera / HI-602 Migrate gemspec info in project_data.yaml to the .gemspec file Change By: Enis Inan Sprint: Platform OS Kanban Ready for Eng. 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-602) Migrate gemspec info in project_data.yaml to the .gemspec file
Title: Message Title Enis Inan created an issue Hiera / HI-602 Migrate gemspec info in project_data.yaml to the .gemspec file Issue Type: Task Assignee: Unassigned Created: 2018/05/08 12:05 AM Priority: Normal Reporter: Enis Inan We currently use packaging's "package:gem" task to build the Hiera gem which adds a lot more complexity than we need (i.e. it builds a gemspec from data in project_data.yaml and then builds the corresponding default gem from it + any platform-specific gems [that might have platform-specific dependences]). We should have the info. in project_data.yaml in the .gemspec file so that a simple gem build should do the trick. Add Comment This message was sent by Atlassian JIRA
