Jira (PUP-1526) Package type should support environment variables
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1526 Package type should support environment variables Change By: Geoff Nichols Sprint: Platform OS Community PR 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-8686) Autoloader excessively stats files
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8686 Autoloader excessively stats files Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8686) Autoloader excessively stats files
Title: Message Title Josh Cooper created an issue Puppet / PUP-8686 Autoloader excessively stats files Issue Type: Bug Assignee: Unassigned Created: 2018/05/01 5:47 PM Priority: Normal Reporter: Josh Cooper For each puppet resource type, e.g. file, the autoloader will attempt to load all providers for that type. The autoloader's loadall method will glob each directory in its autoloader search pat looking for files of the form puppet/provider/. In a dev/bundler setup with no module there are about 100 directories to scan due to gems, etc. The files_to_load method will return a list of relative paths, e.g. puppet/provider/type/file/posix.rb. The autoloader will then call load_file to load the file using it's relative path. The autoloader then searches the entire search space again! So we've got an O^2 thing going on. The autoloader should preserve the absolute path of the provider it globbed, and try to load that file, instead of searching for it again. Making that change reduced the number of stat64 calls from 1515 to 1146, so 25% less. Add Comment
Jira (BOLT-507) Build and ship Bolt for SLES 15 x86_64
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-507 Build and ship Bolt for SLES 15 x86_64 Issue Type: Task Assignee: Unassigned Created: 2018/05/01 5:05 PM Priority: Normal Reporter: 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
Jira (BOLT-461) Rename bolt package to puppet-bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-461 Rename bolt package to puppet-bolt Change By: Michael Smith Ubuntu 18.04 has a package called 'bolt' as part of the core system:https://packages.ubuntu.com/bionic/boltWe will need to rename our packages to avoid a conflict. Fortunately they do not have a binary called 'bolt' so I think we can retain that, but we'll definitely need to rename the packages.Setup puppet-bolt to replace bolt < 0.20.0 and only on the platforms where we currently ship packages. Also add support for Ubuntu 18.04, and drop Debian 7 (EOL). 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-8685) Migrate gemspec info in project_data.yaml to the .gemspec file
Title: Message Title Enis Inan assigned an issue to Enis Inan Puppet / PUP-8685 Migrate gemspec info in project_data.yaml to the .gemspec file Change By: Enis Inan Assignee: Enis Inan 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-3918) (maint) Add dep-diff to allow checking :tree differences
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3918 (maint) Add dep-diff to allow checking :tree differences Issue Type: Bug Assignee: Unassigned Created: 2018/05/01 3:22 PM Priority: Normal Reporter: gepetto-bot 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 (FACT-1821) [facter] memory fact sometimes fails on AIX
Title: Message Title Branan Riley updated an issue Facter / FACT-1821 [facter] memory fact sometimes fails on AIX Change By: Branan Riley Sprint: Platform OS 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 (FACT-1821) [facter] memory fact sometimes fails on AIX
Title: Message Title Branan Riley assigned an issue to Unassigned Facter / FACT-1821 [facter] memory fact sometimes fails on AIX Change By: Branan Riley Assignee: Branan Riley 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-8590) puppet device --apply does not support symbol facts
Title: Message Title Rick Sherman updated an issue Puppet / PUP-8590 puppet device --apply does not support symbol facts Change By: Rick Sherman Summary: puppet device --apply does not support symbol facts 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-1843) Make prtdiag timeout configurable on Solaris
Title: Message Title Branan Riley updated an issue Facter / FACT-1843 Make prtdiag timeout configurable on Solaris Change By: Branan Riley Labels: maintenance triage sadness solaris triaged 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-1843) Make prtdiag timeout configurable on Solaris
Title: Message Title Branan Riley updated an issue Facter / FACT-1843 Make prtdiag timeout configurable on Solaris Change By: Branan Riley Labels: sadness solaris triaged 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-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage 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 (FACT-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform Change By: Geoff Nichols Fix Version/s: FACT 4.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 (FACT-1779) Windows 2016 container not detected as virtual=docker by facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1779 Windows 2016 container not detected as virtual=docker by facter Change By: Geoff Nichols Fix Version/s: whereami 1.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 (FACT-1779) Windows 2016 container not detected as virtual=docker by facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1779 Windows 2016 container not detected as virtual=docker by facter Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage 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 (FACT-1804) Need fact that returns "armhfp" on Raspberry Pi 3.
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1804 Need fact that returns "armhfp" on Raspberry Pi 3. Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage 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-1804) Need fact that returns "armhfp" on Raspberry Pi 3.
Title: Message Title Geoff Nichols assigned an issue to Branan Riley Facter / FACT-1804 Need fact that returns "armhfp" on Raspberry Pi 3. Change By: Geoff Nichols Assignee: Branan Riley 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Geoff Nichols Fix Version/s: PUP 6.y 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-8685) Migrate gemspec info in project_data.yaml to the .gemspec file
Title: Message Title Enis Inan created an issue Puppet / PUP-8685 Migrate gemspec info in project_data.yaml to the .gemspec file Issue Type: Task Assignee: Unassigned Created: 2018/05/01 2:36 PM Fix Versions: PUP 4.10.z Priority: Normal Reporter: Enis Inan We currently use packaging's "package:gem" task to build the Puppet 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
Jira (PUP-8396) Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called
Title: Message Title Branan Riley assigned an issue to Unassigned Puppet / PUP-8396 Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called Change By: Branan Riley 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-8396) Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called
Title: Message Title Branan Riley updated an issue Puppet / PUP-8396 Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called Change By: Branan Riley Sprint: Platform OS 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 (FACT-1843) Make prtdiag timeout configurable on Solaris
Title: Message Title Adam Bottchen commented on FACT-1843 Re: Make prtdiag timeout configurable on Solaris This issue can also cause side effects with MCO. If facter hangs on prtdiag (or anything else for that matter), it can cause the metadata refresh for MCO to backup and stack on top of each other. 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-8396) Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called
Title: Message Title Branan Riley updated an issue Puppet / PUP-8396 Puppet Resource Service fails on Debian/Ubuntu when non systemd service is called Change By: Branan Riley Labels: cs_pr_review cspapercuts linux sadness service type_and_provider ubuntu 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-1843) Make prtdiag timeout configurable on Solaris
Title: Message Title Adam Bottchen updated an issue Facter / FACT-1843 Make prtdiag timeout configurable on Solaris Change By: Adam Bottchen Labels: maintenance triage Sprint: Platform OS Grooming/Triage 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-506) Add boolean to parameter type docs
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-506 Add boolean to parameter type docs Issue Type: Task Assignee: Unassigned Created: 2018/05/01 2:24 PM Priority: Normal Reporter: Alex Dreyer Boolean should be listed in the parameter type docs for "writing_tasks" Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-506) Add boolean to parameter type docs
Title: Message Title Alex Dreyer assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-506 Add boolean to parameter type docs Change By: Alex Dreyer Assignee: Cas Donoghue 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-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage 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-1846) inconsistent results between facter and puppet facts
Title: Message Title Branan Riley updated an issue Facter / FACT-1846 inconsistent results between facter and puppet facts Change By: Branan Riley Labels: api triaged 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-1848) cmdline fact does not propperly resolve multiple parameters
Title: Message Title Scott McClellan updated an issue Facter / FACT-1848 cmdline fact does not propperly resolve multiple parameters Change By: Scott McClellan Labels: linux triaged 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-1848) cmdline fact does not propperly resolve multiple parameters
Title: Message Title Scott McClellan commented on FACT-1848 Re: cmdline fact does not propperly resolve multiple parameters We will need to create a list of which kernel parameters should be treated this way. 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-1850) Support XCP-ng operating system
Title: Message Title Branan Riley updated an issue Facter / FACT-1850 Support XCP-ng operating system Change By: Branan Riley Labels: help_wanted linux triaged 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-8684) Allow overriding Facter config (specifically external facts dir) when calling Puppet
Title: Message Title Scott McClellan moved an issue Puppet / PUP-8684 Allow overriding Facter config (specifically external facts dir) when calling Puppet Change By: Scott McClellan Key: FACT PUP - 1849 8684 Project: Facter 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 (FACT-1850) Support XCP-ng operating system
Title: Message Title Branan Riley commented on FACT-1850 Re: Support XCP-ng operating system We're unlikely to do this ourselves unless/until XCP-NG becomes a product priority. We're happy to accept a contribution on Github, though. 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-1850) Support XCP-ng operating system
Title: Message Title Branan Riley updated an issue Facter / FACT-1850 Support XCP-ng operating system Change By: Branan Riley Labels: help_wanted triaged 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-1850) Support XCP-ng operating system
Title: Message Title Branan Riley updated an issue Facter / FACT-1850 Support XCP-ng operating system Change By: Branan Riley Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8556) environment.conf modulepath should accept globs
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8556 environment.conf modulepath should accept globs Change By: Melissa Stone QA Risk Assessment: Needs Assessment No Action 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-8556) environment.conf modulepath should accept globs
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8556 environment.conf modulepath should accept globs Change By: Melissa Stone Release Notes Summary: The `modulepath` as defined in `environment.conf` can now accept globs in the path name. 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-8683) Change http_read_timeout and runtimeout defaults to be less than infinite
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8683
Change http_read_timeout and runtimeout defaults to be less than infinite
Change By:
Josh Cooper
Puppet's http_read_timeout currently defaults to 0 which means infinite. If the agent sends an HTTP request and is waiting for a response, but the response never arrives (eg hard server crash, cable disconnect, router crash, etc), then the agent will hang indefinitely unless {{runtimeout}} is set to a non-zero default , or TCP keepalive detects if the connection is still valid .In Puppet 6, we should change the {{http_read_timeout}} to something less. It also needs to be greater than the amount of time it takes the server to process catalog, report, etc requests.We should also change the {{runtimeout}} to be something less than infinite 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
Jira (BOLT-458) Document using facts plans and Target properties
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-458 Document using facts plans and Target properties Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-451) I would like to suppress notice level run_* logging in my plan
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-451 I would like to suppress notice level run_* logging in my plan Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-462) Function to query puppetdb from plans.
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-462 Function to query puppetdb from plans. Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8667) resource 'tidy' should be less chatty
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8667 resource 'tidy' should be less chatty Change By: Jacob Helwig QA Risk Assessment: Needs Assessment No Action Release Notes Summary: The Tidy resource type now uses the debug log level for its "File does not exist" message, instead of the info level. This means that resources of this type will no longer emit the message by default when the target of the resource has already been cleaned from disk. 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 (PUP-8558) Remove ability to enable non-strict mode in PMT
Title: Message Title Jayant Sane commented on PUP-8558 Re: Remove ability to enable non-strict mode in PMT Jorie Tappa Could you pl either add release notes or say not needed as may be the case? The QA tab says "Needs Assessment"; pl let know if it can be moved to Done since it has passed CI once you take care of the release notes? 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-7607) Windows Scheduled_Task doesn't accept password that comes from Hiera eyaml
Title: Message Title Erick Banks commented on PUP-7607 Re: Windows Scheduled_Task doesn't accept password that comes from Hiera eyaml Erick Banks attempt to repro 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Josh Cooper commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Coming back to this after awhile. Puppet may try to reuse a connection that was actively closed by the remote side (eg due to a load balancer sending FIN or RST) or the connection is in a half-open state (and the agent never received notification). Puppet could do an IO.select on the socket to detect an error condition in the first case, but that won't help the second. The only way to do that is to try to write something to the socket, rescue the exception, and retry. We could probably implement something similar to what httpclient does, to wrap requests in a protect_keep_alive_disconnected block, and force a new connection to be created if the request fails. However, I think that should only occur if there is an exception at the TCP layer, not the application layer, otherwise we might retry a non-idempotent REST method, e.g. PUT. A slightly different issue is that puppet uses an infinite read timeout by default. If puppet sends a request, e.g. for a catalog, and is waiting for a response, but ends up in a half-open state, then the agent will hang indefinitely (unless runtimeout is set to a non-zero value, see PUP-7517). In Puppet 6, we should change both of those default timeouts to something less than infinite (see PUP-8683). 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
Jira (PUP-8683) Change http_read_timeout and runtimeout defaults to be less than infinite
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8683 Change http_read_timeout and runtimeout defaults to be less than infinite Change By: Josh Cooper Team: Coremunity 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-8683) Change http_read_timeout and runtimeout defaults to be less than infinite
Title: Message Title Josh Cooper created an issue Puppet / PUP-8683 Change http_read_timeout and runtimeout defaults to be less than infinite Issue Type: Task Assignee: Unassigned Created: 2018/05/01 11:15 AM Fix Versions: PUP 6.0.0 Priority: Normal Reporter: Josh Cooper Puppet's http_read_timeout currently defaults to 0 which means infinite. If the agent sends an HTTP request and is waiting for a response, but the response never arrives (eg hard server crash, cable disconnect, router crash, etc), then the agent will hang indefinitely unless runtimeout is set to a non-zero default. In Puppet 6, we should change the http_read_timeout to something less. It also needs to be greater than the amount of time it takes the server to process catalog, report, etc requests. We should also change the runtimeout to be something less than infinite as well. Add Comment
Jira (PUP-6750) Windows scheduled_task v2
Title: Message Title Larissa Lane updated an issue Puppet / PUP-6750 Windows scheduled_task v2 Change By: Larissa Lane Epic Status: To Do Done 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-4433) Puppet doesn't process SIGCHLD
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4433
Puppet doesn't process SIGCHLD
Change By:
Josh Cooper
On some slow environments, there is a time between SIGCHLD and process termination. It leads to some issues as described at https://bugs.launchpad.net/fuel/+bug/1444989Puppet should verify SIGCHLD and make sure process actually ended and not zombiedLooking at util/execution.rb {code:ruby} if execution_stub = Puppet::Util::ExecutionStub.current_value return execution_stub.call(*exec_args)elsif Puppet.features.posix? child_pid = execute_posix(*exec_args) exit_status = Process.waitpid2(child_pid).last.exitstatus {code} Puppet code doesn't have any traps for sigchild to have any extra verifications if process zombied or stuck {code:ruby} trap(:CHLD) do beginwhile pid = Process.wait(-1, Process::WNOHANG) exit if pid == child_pidend rescue Errno::ECHILD endend {code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You
Jira (PUP-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection Change By: Josh Cooper Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (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 called {{Boltfile}}. 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}}.Add a new {{bolt boltfile 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 boltfile boltd install}} command that installs the {{Puppetfile}}Questions:Should we use {{Boltfile}} and bolt or {{Bolt.d}}? bolt.d Should we merge in any of the global config? No Should 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-465) Publish Bolt to Homebrew Cask
Title: Message Title Michael Smith commented on BOLT-465 Re: Publish Bolt to Homebrew Cask Hunter (Hunner) Haugen tp we were talking about how to automate this and whether we want to add another project to cask that updates every week. Did you consider creating a tap for pdk? We could have a shared one Puppet products. 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-8588) Support multiple implementations when loading tasks
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-8588 Support multiple implementations when loading tasks Change By: Alex Dreyer 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-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 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-486) Bolt plan help mentions using --query
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-486 Bolt plan help mentions using --query Change By: Alex Dreyer 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-486) Bolt plan help mentions using --query
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-486
Bolt plan help mentions using --query
Change By:
Alex Dreyer
{{bolt plan --help}} includes an example that uses {{-q}} to run against a PuppetDB query. That doesn't actually work.We should either remove that example from the plan help output, or update plans to accept {{--query => nodes}}.
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 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-461) Rename bolt package to puppet-bolt
Title: Message Title Michael Smith commented on BOLT-461 Re: Rename bolt package to puppet-bolt We should add Ubuntu 18.04 and drop Debian 7 packages at the same time. 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 Alex Dreyer commented on BOLT-461 Re: Rename bolt package to puppet-bolt we can deprecate debian 7 at the same time 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-505) PT_xyz env variables do not seem to be propagated when using "run-as"
Title: Message Title Alex Dreyer commented on BOLT-505 Re: PT_xyz env variables do not seem to be propagated when using "run-as" verify this fails cleanly. It may also break some task rely on the runas users environment. 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-6542) Group resource emits misleading change notification with auth_membership => false
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6542 Group resource emits misleading change notification with auth_membership => false Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: The output messages for this is pretty confusing. It appears as though it changes it to only the members specified, but it doesn't actually, which makes it behave like the user resource.It's unclear which behavior will be less confusing. Should the group resource manage the entire state of a group, or be additive in the way the user resource is?Windows is different in that groups can be members of other groups and having to respecify all members of a group may be frustrating. CS Severity: 3 - Serious CS Business Value: 5 - $$ CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-6542) Group resource emits misleading change notification with auth_membership => false
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6542 Group resource emits misleading change notification with auth_membership => false Change By: Owen Rodabaugh 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 (BOLT-451) I would like to suppress notice level run_* logging in my plan
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-451 I would like to suppress notice level run_* logging in my plan Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8634) Chown of ssldir Causing Failures
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8634 Chown of ssldir Causing Failures Change By: Owen Rodabaugh CS Priority: Needs Priority Minor CS Impact: Based on the comments in this ticket the behavior seems to be isolated to nodes upgrades from Puppet 3.x. Workarounds have been provided to either remove the puppet users and/or use the --manage_internal_file_permission=false setting in puppet.conf.While annoying this issue appears to have been resolved in puppet 4. CS Severity: 2 - Annoyance CS Business Value: 3 - CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-6936) unable to read last_run_summary.yaml from user
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Owen Rodabaugh CS Priority: Needs Priority Reviewed CS Impact: Customer wants to use this file to monitor their agent runs and not run monitoring as the root user which causes file to be inaccessible without other action to move it or change permissions. 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Adam Bottchen CS Priority: Normal 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-6387) Puppet agent hung waiting on read from puppetmaster
Title: Message Title
Tylar Murray commented on PUP-6387
Re: Puppet agent hung waiting on read from puppetmaster
Thanks Josh Cooper for the suggestion. In each of my cases it was a corrupted rpm database from a hard crash in the middle of puppet installing a package using yum. My fix was: [root@imars-airflow13 ~]# find /var/ -type f -name __db* -exec rm {} \; [root@imars-airflow13 ~]# find /var/lib/rpm -type f -name *lock -exec rm {} \;{{}} [root@imars-airflow13 ~]# yum update{{}}
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-8680) Puppet should supervise and kill its applying child if it gets stuck
Title: Message Title R.I.Pienaar commented on PUP-8680 Re: Puppet should supervise and kill its applying child if it gets stuck Ah that's handy, was not aware of this setting. Yeah setting it to something like a few hours by default in 6 would be great 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.
