Jira (PUP-9931) Make Context thread local
Title: Message Title Josh Cooper commented on PUP-9931 Re: Make Context thread local Passed puppet#master in https://github.com/puppetlabs/puppet/commit/c2ccdd4efe 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306716.1556578082000.93117.1568179680118%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Josh Cooper commented on PUP-10016 Re: Systemd provider is not correctly selected as the service provider if puppet is run as non root Passed master CI in https://github.com/puppetlabs/puppet/commit/c2ccdd4efe 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.93113.1568179620521%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is overridden by http_proxy environment variable
Title: Message Title Josh Cooper commented on PUP-9990 Re: no_proxy config setting is overridden by http_proxy environment variable CI passed in https://github.com/puppetlabs/puppet/commit/c2ccdd4efe 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322755.1567086003000.93107.1568179560529%40Atlassian.JIRA.
Jira (PUP-9109) File: source attribute broken for HTTP(s) URI's containing query parameters
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9109 File: source attribute broken for HTTP(s) URI's containing query parameters Change By: Josh Cooper Fix Version/s: PUP 6.4.4 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.274566.1536231724000.93095.1568178660483%40Atlassian.JIRA.
Jira (PUP-9109) File: source attribute broken for HTTP(s) URI's containing query parameters
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9109 File: source attribute broken for HTTP(s) URI's containing query parameters Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.274566.1536231724000.93099.1568178660511%40Atlassian.JIRA.
Jira (PUP-9109) File: source attribute broken for HTTP(s) URI's containing query parameters
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9109 File: source attribute broken for HTTP(s) URI's containing query parameters 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.274566.1536231724000.93097.1568178660501%40Atlassian.JIRA.
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10013 Update minitar version and call new fsync=false option Change By: Josh Cooper Fix Version/s: PUP 6.4.z 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323877.1567788493000.93093.1568175360225%40Atlassian.JIRA.
Jira (PUP-9813) Performance of unpacking modules is extremely slow
Title: Message Title Josh Cooper commented on PUP-9813 Re: Performance of unpacking modules is extremely slow Thanks for raising this issue Chris Suszynski. We submitted a patch to minitar, and it's been released. Now we need to update puppet's minitar usage, so we don't fsync every extracted file and directory. We're tracking that work in PUP-10013, so I'm going to close this ticket and related 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315304.156219440.93089.1568175060447%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows I realize this may be a matter of principle ... but I'm imagining trying to explain this to a user in documentation or a support ticket. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.93042.1568160300714%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Yes but it is counterintuitive that ... On Windows, the gem provider installs into Puppet On Linux, the gem provider installs into system Ruby On both Linux and Windows, the puppet_gem provider installs into 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.93024.1568160120533%40Atlassian.JIRA.
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Josh Cooper commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
I made a note in the PR, I think we can close this ticket as a dup of PUP-6488 and close the PR. Using the new targetable functionality it's possible to manage gems on windows (and other platforms) for ruby installations different than the vendored ruby in our puppet-agent package: I installed chocolatey using:
C:\Users\Administrator>choco install ruby
...
Ruby is going to be installed in 'C:\tools\ruby26'
Installing 64-bit ruby...
...
Then installed the gem into that ruby using:
package { 'puppet-lint':
ensure => present,
provider => 'gem',
command => 'C:\tools\ruby26\bin\gem.cmd',
}
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10016 Systemd provider is not correctly selected as the service provider if puppet is run as non root Change By: Josh Cooper Release Notes Summary: PUP-7312 (released in 6.8.0) introduced a regression that prevented puppet's systemd provider from working when running as non-root. For example, the command "puppet resource service" did not include systemd services. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.92774.1568153040226%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Josh Cooper commented on PUP-10016 Re: Systemd provider is not correctly selected as the service provider if puppet is run as non root Since PUP-7312 was never released in 5.5-6.4, then this "fix" only applies to 6.9.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.92754.1568152860218%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Josh Cooper commented on PUP-10016 Re: Systemd provider is not correctly selected as the service provider if puppet is run as non root Merged 5.5.x PR in https://github.com/puppetlabs/puppet/commit/7c01e08e03e54e6ea8f822c05ac117f500f9dcc4 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.92751.1568152800213%40Atlassian.JIRA.
Jira (PDB-4278) Add metric to track the number of commands "bashed in place"
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4278 Add metric to track the number of commands "bashed in place" Change By: Zachary Kent Assignee: Zachary Kent 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.297778.1551375448000.92742.1568152681114%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Josh Cooper commented on PUP-10016 Re: Systemd provider is not correctly selected as the service provider if puppet is run as non root Merged master PR in https://github.com/puppetlabs/puppet/commit/c2ccdd4efe8ffc4a721ab47c88a834158a37251e 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.92746.1568152681130%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Nirupama Mantha commented on PUP-10016 Re: Systemd provider is not correctly selected as the service provider if puppet is run as non root Please update release notes for this ticket accordingly 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.92679.1568151180179%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10016 Systemd provider is not correctly selected as the service provider if puppet is run as non root Change By: Josh Cooper Fix Version/s: PUP 6.9.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.92096.1568136780506%40Atlassian.JIRA.
Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title Jean Bond assigned an issue to Jean Bond Puppet / PUP-9993 lookup's knockout_prefix cannot be undef, contrary to the documentation Change By: Jean Bond Assignee: Jean Bond 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.92027.1568136000454%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is overridden by http_proxy environment variable
Title: Message Title Kris Bosland commented on PUP-9990 Re: no_proxy config setting is overridden by http_proxy environment variable Merged into master at a96169f. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322755.1567086003000.91993.1568135460455%40Atlassian.JIRA.
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-10013 Update minitar version and call new fsync=false option Change By: Jorie Tappa Assignee: 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323877.1567788493000.91871.1568134380240%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10016 Systemd provider is not correctly selected as the service provider if puppet is run as non root Change By: Gheorghe Popescu Story Points: 1 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.91564.1568122020146%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-10016 Systemd provider is not correctly selected as the service provider if puppet is run as non root Change By: Gheorghe Popescu Assignee: Gheorghe Popescu 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.91563.1568122020140%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Gheorghe Popescu commented on PUP-10016 Re: Systemd provider is not correctly selected as the service provider if puppet is run as non root https://github.com/puppetlabs/puppet/pull/7705 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.91560.1568121600138%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title
Gheorghe Popescu created an issue
Puppet / PUP-10016
Systemd provider is not correctly selected as the service provider if puppet is run as non root
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/09/10 6:16 AM
Priority:
Normal
Reporter:
Gheorghe Popescu
Puppet Version: 6.8.1 It seems that this change breaks a few things when Puppet is not being run as root, for example during spec tests (i.e. pdk test unit). At least under Ubuntu 16.04 and 18.04 the file /proc/1/exe is not accessible by regular users, so Puppet::FileSystem.exist?('/proc/1/exe') returns false and Puppet::FileSystem.readlink('/proc/1/exe').include?('systemd') fails with Errno::EACCES. ls also fails, obviously:
$ ls /proc/1/exe
ls: cannot read symbolic link '/proc/1/exe': Permission denied
lrwxrwxrwx 1 root root 0 Sep 7 00:13 /proc/1/exe
This has interesting implications in that now Puppet no longer recognizes that systemd is the correct service provider for recent Debian and Ubuntu releases. Thus spec tests for ser
