Jira (PUP-8747) Virtual Collector overrides fail with in 5.x
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-8747 Virtual Collector overrides fail with in 5.x Change By: Adam Bottchen CS Priority: Needs Priority Reviewed 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 Alex Dreyer commented on BOLT-523 Re: I want to install modules with bolt It's much more clear to me how it should work in Boltdir mode. Puppetfile should be loaded from Boltdir/Puppetfil modules installed into Boltdir/modules. I think a default relative to the Puppetfile probably makes the most sense even outside Boltdir mode. that will work well with task modules or other things that use the control repo format. 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-518) Facter task does not correctly detect Ubuntu OS family
Title: Message Title Cas Donoghue commented on BOLT-518 Re: Facter task does not correctly detect Ubuntu OS family General info about os-release: http://0pointer.de/blog/projects/os-release man page: https://www.freedesktop.org/software/systemd/man/os-release.html 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 commented on BOLT-503 Re: Use local config automatically to embed bolt in a project I broke the module installation features into their own ticket BOLT-523. I think a command to initialize an empty boltdir should be a separate ticket as well. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. 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 Solutions :When bolt runs it should search the {{cwd}} and its ancestors for a directory called {{ bolt Boltdir }}. If one is found it should use that as the bolt config and should run in Boltdir mode where default modules and inventory to be inside the directory bolt next to the location for {{ Boltdir}}.Add a new {{ bolt init .yaml }} command that creates an empty bolt directory with empty , {{inventory }} and {{modules}} directory and an empty {{Puppetfile}} . Add a new {{bolt install yaml }} command that installs the {{Puppetfile}}. {{bolt install }} should accept be at the path to a puppetfile top level of the Boltdir and install it.Questions:Should we use {{Boltfile}} and bolt or {{Bolt.d}}? the directory modulepath should be called default to {{Boltdir /modules/ }} Should we merge in any of the global config? No Should we fall back to The global config and inventory if there isn't local inventory? should not be loaded by default when running in Boltdir mode.
Add Comment
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 Sprint: Bolt Discover/Design 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-523) I want to install modules with bolt
Title: Message Title Michael Smith commented on BOLT-523 Re: I want to install modules with bolt bolt module install is similar to bundle install but reminiscent of puppet module install. Is bolt sync clear? Too simple? I think we should have a default place to install, and not require you to ask. Which then means we need to load modules from there as well. But I'm inclined to think a Puppetfile is a local thing, so maybe the default should be that it exists in a Boltdir. Otherwise you have to explicitly specify the Puppetfile and install location. 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 Nick Lewis commented on BOLT-380 Re: Support ed25519 out-of-the-box I'm not sure. 5.0.0beta2 was released two months ago, but there haven't really been any commits since then. I tried to build the ed25519 gem and failed on Windows, but I'm sure we can figure that out. 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 Alex Dreyer updated an issue Puppet Task Runner / BOLT-523 I want to install modules with bolt Change By: Alex Dreyer 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-380) Support ed25519 out-of-the-box
Title: Message Title Michael Smith commented on BOLT-380 Re: Support ed25519 out-of-the-box That sounds like a workable path. Any timeline for net-ssh 5.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 (BOLT-523) I want to install modules with bolt
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-523 I want to install modules with bolt Issue Type: Story Assignee: Unassigned Created: 2018/05/17 3:58 PM Priority: Normal Reporter: Alex Dreyer 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 for 2. 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 command Bolt 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? Should bolt become more opinionated on where code lives outside of the context of a boltdir? Add Comment
Jira (BOLT-380) Support ed25519 out-of-the-box
Title: Message Title Nick Lewis commented on BOLT-380 Re: Support ed25519 out-of-the-box It also looks like net-ssh 5.0 will change to using ed25519 and bcrypt_pbkdf for ed25519. Once that's released, we may be able to bump our dependency and bundle those gems. 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 Nick Lewis commented on BOLT-380 Re: Support ed25519 out-of-the-box The maintainer of rbnacl-libsodium is planning to deprecate it in favor of OS packages. That would leave us in a state of having to either depend on or bundle libsodium ourselves. Aside from that, the rbnacl-libsodium gem doesn't appear to be supported on Windows. So my question is: have we received enough signal on this issue that it's worth the effort of maintaining a build of libsodium ourselves? 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-7918) puppet fails to change user group membership if directory group names have spaces
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-7918 puppet fails to change user group membership if directory group names have spaces Change By: Adam Bottchen CS Priority: Needs Priority Normal 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-392) Application Deployment Plan
Title: Message Title Kate Lopresti commented on BOLT-392 Re: Application Deployment Plan Add app deployment lesson added to hands-on-lab. Needs Docs review. https://github.com/puppetlabs/tasks-hands-on-lab 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-8712) Add deprecation warning for puppet master --configprint
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8712 Add deprecation warning for puppet master --configprint Change By: Josh Cooper Sprint: Platform Core Hopper 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
Josh Cooper updated an issue
Puppet / PUP-8703
Numeric('0') raises an error
Change By:
Josh Cooper
Fix Version/s:
PUP 5.5.z
Fix Version/s:
PUP 5.5.2
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8637) freeze_main setting breaks when used with type aliases
Title: Message Title Josh Cooper commented on PUP-8637 Re: freeze_main setting breaks when used with type aliases Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/f3f37f401547c9a13a865ad035d76ce7e86a6588 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-8714) Puppet Agent doesn't recover from network failure
Title: Message Title Michael Smith commented on PUP-8714 Re: Puppet Agent doesn't recover from network failure Thanks for that breakdown, I caught some details there that I didn't get in the original description. 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-8714) Puppet Agent doesn't recover from network failure
Title: Message Title Joaquin Henriquez Alzola commented on PUP-8714 Re: Puppet Agent doesn't recover from network failure I run the "puppet agent -t" as the root user. puppet5 or puppet is just my nodename (dns) the systemd is run as root. I will try to explain it a bit simpler here: 400 server running puppet, normally Network Error happens Only 20% (80) of those nodes try to contact the puppet server while network is down The error is the generic specify above Network Recovers 320 servers keep working normally and systemctl log output shows it is working normally. 80 server are stuck with the Error specify above Running "puppet agent -t" on those 80 servers (as root) works fine If systemd runs on those 80 servers (every 30 minutes) it will fail again with the Error specify above the only solution is to perform a "systemctl restart puppet" Centos7 1804 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Jacob Helwig assigned an issue to Jacob Helwig Puppet / PUP-686 --detailed-exit-codes not honored when --noop is used Change By: Jacob Helwig Assignee: Jacob Helwig 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-522) More clear error message when trying to upload directories
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-522 More clear error message when trying to upload directories Issue Type: Improvement Assignee: Unassigned Created: 2018/05/17 2:06 PM Priority: Normal Reporter: Nick Lewis Currently, Bolt only supports uploading individual files. If you try to upload a directory (at least with SSH), the error message from the underlying library says can't upload directories unless :recursive. Since we don't support recursive uploads, that error message is extremely misleading. We should detect this case and inform the user we don't support directory uploads. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8714) Puppet Agent doesn't recover from network failure
Title: Message Title Michael Smith commented on PUP-8714 Re: Puppet Agent doesn't recover from network failure On re-reading, maybe there is a problem here. I'm trying to come up with theories of what it might be. Every scheduled run by the service should be started from scratch in a new child process of the service. When you run puppet agent -t, are you running as root or a user account? And presumably the service was working before the network issue. I'm at a bit of a loss where to start troubleshooting. Could this be a bug in systemd? 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-8714) Puppet Agent doesn't recover from network failure
Title: Message Title Michael Smith commented on PUP-8714 Re: Puppet Agent doesn't recover from network failure This is most likely an issue with how it's configured or how your network is setup. It's a little strange that it's trying to connect to puppet5:8140 rather than puppet:8140. I'd suggest asking this in our Slack or Q Site (linked from https://puppet.com/community). You should be able to get some more prompt help there. 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-8712) Add deprecation warning for puppet master --configprint
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-8712 Add deprecation warning for puppet master --configprint Change By: Jorie Tappa Assignee: Kris Bosland Jorie Tappa 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 Michael Smith updated an issue Puppet Task Runner / BOLT-507 Build and ship Bolt for SLES 15 x86_64 Change By: Michael Smith 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-507) Build and ship Bolt for SLES 15 x86_64
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-507 Build and ship Bolt for SLES 15 x86_64 Change By: Michael Smith Ensure bolt-runtime is produced for SLES 15, then add config to bolt-vanagon and update Bolt target platforms in ci-job-configs. 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 Michael Smith updated an issue Puppet Task Runner / BOLT-507 Build and ship Bolt for SLES 15 x86_64 Change By: Michael Smith 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 (PUP-8672) Memory leak in Puppet Server from loading translations
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8672 Memory leak in Puppet Server from loading translations Change By: Kenn Hussey Fix Version/s: PUP 5.5.2 Fix Version/s: PUP 5.5.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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8672) Memory leak in Puppet Server from loading translations
Title: Message Title Michael Smith updated an issue Puppet / PUP-8672 Memory leak in Puppet Server from loading translations Change By: Michael Smith Release Notes Summary: Addresses a small memory leak with temporary environments. When the environment cache was cleared, associated translation domains were not instead hanging onto them until they're replaced the next time the environment was used. Environments that were never used again would hang onto a small amount of memory (probably less than 100 bytes, plus whatever's used by actual translations). This has been resolved so translation domains will now be released when the related cached environment cache is purged. 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-8672) Memory leak in Puppet Server from loading translations
Title: Message Title Michael Smith updated an issue Puppet / PUP-8672 Memory leak in Puppet Server from loading translations Change By: Michael Smith Release Notes Summary: Addresses a small memory leak with temporary environments. When the environment cache was cleared, associated translation domains were not instead hanging onto them until they're replaced the next time the environment was used. Environments that were never used again would hang onto a small amount of memory (probably less than 100 bytes, plus whatever's used by actual translations). This has been resolved so translation domains will now be released when the related environment cache is purged. 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
Jira (FACT-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd
Title: Message Title Branan Riley updated an issue Facter / FACT-1851 Linux networking resolver doesn't collect DHCP information under systemd-networkd Change By: Branan Riley Fix Version/s: FACT 3.11.z Fix Version/s: FACT 3.11.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-392) Application Deployment Plan
Title: Message Title David Kramer assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-392 Application Deployment Plan Change By: David Kramer Assignee: Kate Lopresti 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-3925) Update rbac-client version in pdbext 5.1.x to match clj-parent
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3925 Update rbac-client version in pdbext 5.1.x to match clj-parent Issue Type: Improvement Assignee: Rob Browning Created: 2018/05/17 9:42 AM Priority: Normal Reporter: 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
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 Fix Version/s: PDB 5.1.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 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 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-8705) Add SRV record support to Puppet::Rest::Client
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8705 Add SRV record support to Puppet::Rest::Client Change By: Maggie Dreyer ***Update***In order to improve performance over the indirector's re-resolving SRV records on each request, we should implement something similar to [Puppet::Network::Resolver|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/resolver.rb] but that caches the results of the SRV lookup for each service. The cache of SRV records should be invalidated based on the shortest TTL among the cache entries. This resolver should be an object whose lifetime is tied to the HTTP client making requests with its results. A (Note that currently the HTTP clients are created where needed and their configuration is locked, but eventually we will probably use one client for all requests, at which point the DNS cache will therefore also be global). The client should then in turn cache the selected server and port, and that cache entry should only be invalidated if the cached server becomes unreachable for any reason, including a 500 error. The cache of SRV records At this point the server and port should be invalidated based on reselected from the shortest TTL among cached SRV record inside the cache entries Resolver .***Original text***Currently, Puppet::Rest::Client does not do any SRV lookups, unlike the other indirector-based HTTP client in Puppet. We need to implement this, once we fully understand the tradeoffs between performance and the need to restrict caching due to the nature of SRV lookups.A quick look at the current implementation ([https://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/request.rb#L187-L197] and [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/resolver.rb#L8-L41]) makes it look as though DNS::Resolv objects and SRV lookups are performed on every request. We need to evaluate whether this is necessary, or more could be done to cut down on work that must be done per-request. Add Comment
Jira (PUP-8705) Add SRV record support to Puppet::Rest::Client
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8705 Add SRV record support to Puppet::Rest::Client Change By: Maggie Dreyer Acceptance Criteria: * Puppet::Rest::Client respects SRV records when available . * The record list for a service is cached once it has been resolved . * The cached of records should be invalidated when the shortest TTL among cached records has expired. * The found server for each service is cached once it has been selected . * The cache entry for a selected server is invalidated if the server is unreachable, and a new server is selected from the cached record list for that service, falling back to configured value if none is available. 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-8705) Add SRV record support to Puppet::Rest::Client
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8705 Add SRV record support to Puppet::Rest::Client Change By: Maggie Dreyer ***Update***In order to improve performance over the indirector's re-resolving SRV records on each request, we should implement something similar to [Puppet::Network::Resolver|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/resolver.rb] but that caches the results of the SRV lookup for each service. This resolver should be an object whose lifetime is tied to the HTTP client making requests with its results. A cache entry should only be invalidated if the cached server becomes unreachable for any reason, including a 500 error. For the time being, The cache of SRV record TTLs can records should be ignored, since invalidated based on the client does not live long enough for it to be a problem shortest TTL among the cache entries .***Original text***Currently, Puppet::Rest::Client does not do any SRV lookups, unlike the other indirector-based HTTP client in Puppet. We need to implement this, once we fully understand the tradeoffs between performance and the need to restrict caching due to the nature of SRV lookups.A quick look at the current implementation ([https://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/request.rb#L187-L197] and [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/resolver.rb#L8-L41]) makes it look as though DNS::Resolv objects and SRV lookups are performed on every request. We need to evaluate whether this is necessary, or more could be done to cut down on work that must be done per-request. Add Comment
Jira (PUP-8747) Virtual Collector overrides fail with in 5.x
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-8747 Virtual Collector overrides fail with in 5.x Change By: Jarret Lavallee CS Priority: Needs Priority 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-8705) Add SRV record support to Puppet::Rest::Client
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8705 Add SRV record support to Puppet::Rest::Client Change By: Maggie Dreyer Acceptance Criteria: * Puppet::Rest::Client respects SRV records when available * The record list for a service is cached once it has been resolved * The found server for each service is cached once it has been resolved selected * The cache entry for a service selected server is invalidated if the selected server is unreachable, and a new server is selected from the cached record list for that service , falling back to configured value if none is resolved again from scratch available. 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-8747) Virtual Collector overrides fail with in 5.x
Title: Message Title Jarret Lavallee commented on PUP-8747 Re: Virtual Collector overrides fail with in 5.x Henrik Lindberg Thanks for taking a look into this. 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-8744) Using a variable in a Type on a parameter results in an error unless the variable was already loaded
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8744 Using a variable in a Type on a parameter results in an error unless the variable was already loaded Change By: Henrik Lindberg Sub-team: Language Team: Platform Core 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-8744) Using a variable in a Type on a parameter results in an error unless the variable was already loaded
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8744 Using a variable in a Type on a parameter results in an error unless the variable was already loaded Change By: Henrik Lindberg h1. The ProblemIf you use a variable from say your params class in a type of a parameter then whether or not you can parse that class depends on whether you included a class that loaded params before the class you use the variable in. Anyway here's an example: https://github.com/npwalker/regex_variable/blob/master/manifests/profile/test.pp#L8h1. Suggested solutionEither this should work every time or it should never work. I'd be fine with detection of this behavior and an outright failure. UPDATE-The data types for parameters must be literal expressions and should error when a variable or function call is used. 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
Jira (PUP-8744) Using a variable in a Type on a parameter results in an error unless the variable was already loaded
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8744 Using a variable in a Type on a parameter results in an error unless the variable was already loaded Change By: Henrik Lindberg 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-8744) Using a variable in a Type on a parameter results in an error unless the variable was already loaded
Title: Message Title
Thomas Hallgren commented on PUP-8744
Re: Using a variable in a Type on a parameter results in an error unless the variable was already loaded
If someone would want to do dynamic checking, that is possible, but it must be done in code (of course, since it's dynamic). A type can be parsed from a String. Example where $myvar is a regexp:
$the_type = Type("Pattern[$myvar]")
$value = $the_type.assert_type($value)
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-8744) Using a variable in a Type on a parameter results in an error unless the variable was already loaded
Title: Message Title Thomas Hallgren commented on PUP-8744 Re: Using a variable in a Type on a parameter results in an error unless the variable was already loaded Yes, I agree with that. The type declaration is a static construct so allowing non-literals is a bug. 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-8753) Agent Functions - Create Conjur deferred evaluation
Title: Message Title Craig Gomes created an issue Puppet / PUP-8753 Agent Functions - Create Conjur deferred evaluation Issue Type: Task Assignee: Unassigned Created: 2018/05/17 5:32 AM Priority: Normal Reporter: Craig Gomes Create deferred evaluation that calls into Conjur to retrieve secrets. What is the performance impact evaluation? Where's the performance impact? Is it in Conjur? Is it in Puppet What's the reference architecture for Conjur deployment with Puppet? Add Comment
Jira (PUP-8752) Agent Functions - Spike research Conjur integration
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8752 Agent Functions - Spike research Conjur integration Change By: Craig Gomes Acceptance Criteria: * Design proposal for Vault Conjur integration 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-8752) Agent Functions - Spike research Conjur integration
Title: Message Title Craig Gomes created an issue Puppet / PUP-8752 Agent Functions - Spike research Conjur integration Issue Type: Task Assignee: Unassigned Created: 2018/05/17 5:30 AM Priority: Normal Reporter: Craig Gomes Research ticket to understand and design Conjur integration for Agent Functions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8751) Agent Functions - Set up Conjur internally for testing
Title: Message Title Craig Gomes created an issue Puppet / PUP-8751 Agent Functions - Set up Conjur internally for testing Issue Type: Task Assignee: Unassigned Created: 2018/05/17 5:29 AM Priority: Normal Reporter: Craig Gomes Set up an internal server for testing. This just for initial implementation research. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8750) puppet resource user --to_yaml produces invalid yaml on solaris
Title: Message Title
Martin Alfke created an issue
Puppet / PUP-8750
puppet resource user --to_yaml produces invalid yaml on solaris
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/05/17 3:11 AM
Priority:
Normal
Reporter:
Martin Alfke
Puppet Version: 2016.4.7 Puppet Server Version: 2016.4.7 OS Name/Version: Solaris 11 puppet resource user --to_yaml produces invalid yaml when user keys are set:
users:
user:
ensure: 'present'
keys: {'lock_after_retries' => 'no'}
Desired Behavior: --to_yaml should produce valid yaml syntax Actual Behavior: yaml is invalid (according to yaml-lint and YAML.load
Jira (PUP-8744) Using a variable in a Type on a parameter results in an error unless the variable was already loaded
Title: Message Title Henrik Lindberg commented on PUP-8744 Re: Using a variable in a Type on a parameter results in an error unless the variable was already loaded Thomas Hallgren I think we need to make the type declarations for parameters only accept literal expressions - what do you think? 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-8747) Virtual Collector overrides fail with in 5.x
Title: Message Title Henrik Lindberg commented on PUP-8747 Re: Virtual Collector overrides fail with in 5.x The problem seems to be when an override is made with the same value as the one in the default. (I tested). If they differ, the override will override the given attribute value in the virtual resource. 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-8747) Virtual Collector overrides fail with in 5.x
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8747 Virtual Collector overrides fail with in 5.x Change By: Henrik Lindberg Fix Version/s: PUP 5.5.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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8749) acceptance test docs do not match reality
Title: Message Title David Schmitt created an issue Puppet / PUP-8749 acceptance test docs do not match reality Issue Type: Bug Assignee: Unassigned Created: 2018/05/17 1:25 AM Priority: Normal Reporter: David Schmitt The instructions in https://github.com/puppetlabs/puppet/blob/master/acceptance/README.md do not match up with reality. The "Preserving Hosts" section references a rake task (ci:test_against_preserved_hosts) that does not exist the configs in https://github.com/puppetlabs/puppet/tree/master/acceptance/config/nodes are half EOL systems, and are missing all the current systems (and should be replaced with beaker-hostgenerator, I assume, making all references to CONFIG= in the README obsolete The documentation for testing against the local changes (arguably the most common usecase for a developer) is buried under statements like "See notes on running acceptance with Vagrant for more details on using a local git daemon." This ticket is sponsored by the struggles in https://github.com/puppetlabs/puppet/pull/6831 Add Comment
Jira (PUP-8745) The match function does not accept a type alias
Title: Message Title Henrik Lindberg commented on PUP-8745 Re: The match function does not accept a type alias Marked this as "major" because there is no work around when you need the match function (expect to patch puppet) 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-8745) The match function does not accept a type alias
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8745 The match function does not accept a type alias Change By: Henrik Lindberg Fix Version/s: PUP 5.5.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8745) The match function does not accept a type alias
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8745 The match function does not accept a type alias Change By: Henrik Lindberg Priority: Normal Major 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.
