Jira (PUP-9990) no_proxy config setting is overridden by http_proxy environment variable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9990 no_proxy config setting is overridden by http_proxy environment variable Change By: Josh Cooper Component/s: Docs 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.86338.1567641600336%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is overridden by http_proxy environment variable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9990 no_proxy config setting is overridden by http_proxy environment variable Change By: Josh Cooper Release Notes Summary: Fixes a bug where puppet would attempt to use a proxy specified in the HTTP_PROXY environment variable, even though Puppet[:no_proxy] said to bypass the proxy. 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.322755.1567086003000.86336.1567641600325%40Atlassian.JIRA.
Jira (PUP-9997) Puppet must not call Dir.chdir() except in a child process
Title: Message Title
James Ralston updated an issue
Puppet / PUP-9997
Puppet must not call Dir.chdir() except in a child process
Change By:
James Ralston
*Puppet Version:* 6.8.1*Puppet Server Version:* 6.5.0*OS Name/Version:* Red Hat Enterprise Linux 7In Ruby, Dir.chdir changes the current working directory (cwd) of the Ruby process. Under the hood, it calls the the chdir() system call.When Dir.chdir is passed a block, it notes the cwd, then calls chdir() and executes the block. When the block finishes, it calls chdir() again, supplying as the argument the previous cwd that it noted. (This is similar to the pushd/popd shell builtins.)However, in Unix, it is possible for the cwd to be a directory that is inaccessible to the current process. This means that once you chdir() out of the cwd, attempting to chdir() to the old cwd will fail.This is trivial to demonstrate for the non-root user:{noformat}$ cd /tmp$ mkdir foo$ chmod 0700 foo$ cd foo$ /usr/bin/pwd/tmp/foo$ cd /tmp/foo && echo noerrornoerror$ chmod .$ /usr/bin/pwd/tmp/foo$ cd /tmp/foo && echo noerror-bash: cd: /tmp/foo: Permission denied{noformat}In most cases, the root user will never receive permission denied errors when attempting to chdir to a directory. But there are exceptions. One exception is a network filesystem where the local root user has no special privileges, such as Kerberized NFS. On Linux systems, removal of the {{CAP_DAC_OVERRIDE}} and {{CAP_DAC_READ_SEARCH}} capabilities will also prevent root from calling chdir() to an inaccessible directory.So, putting this all together, we reach the following conclusion: the only time where it is safe to call Dir.chdir() is in a child process. Because:# Calling Dir.chdir() without a block has a side-effect of changing the cwd for the execution of all subsequent code. This is undesirable, and dangerous.# Calling Dir.chdir() with a block can fail to restore the cwd when the block exits (as per above), which then reduces to #1.Previously, the _cwd_ parameter of the _exec_ resource was implemented using Dir.chdir() with a block argument. This caused failures for users who ran {{sudo puppet agent --test}} when sitting in a Kerberized NFS home directory that root could not execute, as the very first exec resource encountered would throw an exception when Dir.chdir() received EACCES when attempting to restore the old cwd when the block finished. This spawned at least two tickets: PUP-5808 and PUP-5915. At some point in the recent past In PUP-6919 (specifically , {{Puppet [commit ebb57c3e|https : :Util::Execution //github . execute}} added the ability to specify the cwd of the command to be executed com/puppetlabs/puppet/commit/ebb57c3e60800bdc847cc1276b8a6d9d65c6208b]) , and the exec resource was rewritten to simply pass the cwd to {{Puppet::Util::Execution.execute}} instead of calling Dir.chdir() itself. Since {{Puppet::Util::Execution.execute}} doesn't call Dir.chdir() until after it forks the child process and before it calls exec(), and since calling chdir() in a child
Jira (PUP-5808) puppet via sudo from nfs home is not working
Title: Message Title James Ralston updated an issue Puppet / PUP-5808 puppet via sudo from nfs home is not working From digging, it was PUP-6919 (specifically, commit ebb57c3e) that rewrote the exec resource to have the child process call Dir.chdir(). Puppet 5.5.7 was the first version to contain the fix. Change By: James Ralston Fix Version/s: PUP 5.5.7 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.115050.1454515664000.86229.1567639260400%40Atlassian.JIRA.
Jira (PUP-5808) puppet via sudo from nfs home is not working
Title: Message Title James Ralston commented on PUP-5808 Re: puppet via sudo from nfs home is not working For posterity: the issue with the exec resource failing due to receiving EACCES when attempting to call chdir() to the cwd was resolved as a (perhaps intentional) side-effect of changes made to how the exec resource is implemented. (In essence, Puppet now calls chdir() in the child process it forks to perform the exec, not in the parent process.) But the root cause of this issue—that it is never safe to call chdir() except in a child process—is not completely resolved. See PUP-9997 for details. 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.115050.1454515664000.86204.1567638661238%40Atlassian.JIRA.
Jira (PUP-9997) Puppet must not call Dir.chdir() except in a child process
Title: Message Title James Ralston created an issue Puppet / PUP-9997 Puppet must not call Dir.chdir() except in a child process Issue Type: Bug Assignee: Unassigned Created: 2019/09/04 4:00 PM Priority: Minor Reporter: James Ralston Puppet Version: 6.8.1 Puppet Server Version: 6.5.0 OS Name/Version: Red Hat Enterprise Linux 7 In Ruby, Dir.chdir changes the current working directory (cwd) of the Ruby process. Under the hood, it calls the the chdir() system call. When Dir.chdir is passed a block, it notes the cwd, then calls chdir() and executes the block. When the block finishes, it calls chdir() again, supplying as the argument the previous cwd that it noted. (This is similar to the pushd/popd shell builtins.) However, in Unix, it is possible for the cwd to be a directory that is inaccessible to the current process. This means that once you chdir() out of the cwd, attempting to chdir() to the old cwd will fail. This is trivial to demonstrate for the non-root user: $ cd /tmp $ mkdir foo $ chmod 0700 foo $ cd foo
Jira (PUP-9465) group resource type misunderstands/misuses libuser
Title: Message Title James Ralston commented on PUP-9465 Re: group resource type misunderstands/misuses libuser Gabriel Nagy, I agree that using binaries from 2 different packages in the same provider seems wrong. That's the primary reason why I think there should be two separate providers, even though there is a lot of overlap between the functionality of the providers. Upon reflection, I will walk back my "If both the libuser provider and the groupadd provider are available, prefer the libuser provider" assertion. But I'm not sure that the minor differences in functionality are appropriate selection criteria to prefer one provider over the other, either. As you noted, libuser doesn't support NIS (which shadow supports). But shadow doesn't support LDAP (which libuser supports). How about this: for any system where groupadd is currently the default provider, it should remain the default provider, even if the libuser provider is available. This will make the libuser provider available for those who specifically want it (most likely for the manages_members feature), but it will avoid potential disruption by exposing Puppet users to subtle differences between the groupadd and libuser providers. But I still think that once the libuser provider is available, the forcelocal parameter should be deprecated, and should emit a warning that 1) the forcelocal parameter will be removed in a future Puppet release, and 2) to use the libuser provider instead if the goal is have the manages_members feature. Finally, I wouldn't put much stock in the 2013 comment 2 in Red Hat BZ#1028544 about libuser going away. A lot of what libuser was planned to do was subsumed by the sssd project, which is why development on libuser has slowed. But both the shadow project and the libuser project are active. As another metric, Red Hat Enterprise Linux 8 shipped with libuser. Since libuser was created by Red Hat developers and is maintained by Red Hat developers, that means libuser isn't going anywhere for the lifetime of RHEL8, which doesn't end until May 2029. And libuser is still in Fedora, which is (essentially) the upstream for RHEL. Add Comment This message was sent by
Jira (PUP-9991) `puppet module uninstall` does not work on FIPS
Title: Message Title Josh Cooper commented on PUP-9991 Re: `puppet module uninstall` does not work on FIPS Merged to master in https://github.com/puppetlabs/puppet/commit/2e8956b37522da3e7f37d4022df48623c1df34fa 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.323058.1567203304000.85894.1567630320553%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is overridden by http_proxy environment variable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9990 no_proxy config setting is overridden by http_proxy environment variable Change By: Josh Cooper Summary: no_proxy config setting is ignored overridden by puppet agent http_proxy environment variable 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.85351.1567620240421%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9990 no_proxy config setting is ignored by puppet agent 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.322755.1567086003000.85347.1567620240406%40Atlassian.JIRA.
Jira (PUP-9991) `puppet module uninstall` does not work on FIPS
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9991 `puppet module uninstall` does not work on FIPS Change By: Josh Cooper Release Notes Summary: The `puppet module uninstall` command now works in FIPS mode provided the `--ignore_changes` or `--force` arguments are specified. If the arguments are not specified, then uninstall will fail, so that local changes to the module are not lost. 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.323058.1567203304000.85342.1567620180208%40Atlassian.JIRA.
Jira (PUP-9991) `puppet module uninstall` does not work on FIPS
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9991 `puppet module uninstall` does not work on FIPS 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.323058.1567203304000.85344.1567620180217%40Atlassian.JIRA.
Jira (PUP-9991) `puppet module uninstall` does not work on FIPS
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9991 `puppet module uninstall` does not work on FIPS Change By: Josh Cooper Sprint: Coremunity Hopper 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.323058.1567203304000.85331.1567619940944%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper commented on PUP-9990 Re: no_proxy config setting is ignored by puppet agent I wasn't able to reproduce earlier because puppet.delivery.puppetlabs.net resolves to 127.0.0.1 (I'm running puppetserver as a docker container), and Ruby has logic to ignore the proxy env variables when connecting to the loopback: https://github.com/ruby/ruby/blob/f6da4a544760e00d932fea9a586bd869e82ad339/lib/uri/generic.rb#L1533 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.85107.1567616411940%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9990 no_proxy config setting is ignored by puppet agent 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.322755.1567086003000.85075.1567615740227%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9990 no_proxy config setting is ignored by puppet agent 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.322755.1567086003000.85073.1567615740220%40Atlassian.JIRA.
Jira (PDOC-234) remove deprecated cli options
Title: Message Title Eric Putnam assigned an issue to Unassigned Puppet Strings / PDOC-234 remove deprecated cli options Change By: Eric Putnam Assignee: Eric Putnam 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.244919.1523367125000.85021.1567614420247%40Atlassian.JIRA.
Jira (PDOC-193) Evaluate using `yard i18n` to extract doc string content into POT files
Title: Message Title Eric Putnam assigned an issue to Unassigned Puppet Strings / PDOC-193 Evaluate using `yard i18n` to extract doc string content into POT files Change By: Eric Putnam Assignee: Eric Putnam 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.226417.1513173836000.84971.1567613460170%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper commented on PUP-9990 Re: no_proxy config setting is ignored by puppet agent In ruby < 2.5, the Net::HTTP.start method did not automagically read proxy environment variables, but Net::HTTP.new did. This was changed in https://github.com/ruby/ruby/commit/67723c1e4673253b2f4a2c7204ccab9d0daaaeb9#diff-8c2ab8e0fb4f052e1d95ab6334e192c1 so that both start and new observe the env variables by default. When combined with https://github.com/puppetlabs/puppet/commit/64ec44b6331c978ca3bde47f5ae4bc672949ada8#diff-be7012428c14ff64a2e7e58a45ebecd3 for PUP-4470, ruby will try to use proxy settings from the environment even when puppet doesn't want to use a proxy. 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.84957.1567613100719%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper commented on PUP-9990 Re: no_proxy config setting is ignored by puppet agent root@ps5omle63p3320c:~# puppet --version 6.8.0 root@ps5omle63p3320c:~# /opt/puppetlabs/puppet/bin/ruby --version ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux] root@ps5omle63p3320c:~# printenv | grep -i proxy root@ps5omle63p3320c:~# grep proxy /etc/puppetlabs/puppet/puppet.conf http_proxy_host = webproxy.example.com http_proxy_port = 3128 no_proxy = *.delivery.puppetlabs.net root@ps5omle63p3320c:~# env http_proxy=http://webproxy.example.com:3128 puppet agent --test --server_list k83emhbfl9imev6.delivery.puppetlabs.net Error: Could not run Puppet configuration client: Could not select a functional puppet master from server_list: 'k83emhbfl9imev6.delivery.puppetlabs.net' root@ps5omle63p3320c:~# puppet agent --test --server_list k83emhbfl9imev6.delivery.puppetlabs.net
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper commented on PUP-9990 Re: no_proxy config setting is ignored by puppet agent Thanks Ben Roberts. I can reproduce using puppet-agent 6.8.0 on debian stretch. I'll continue looking. 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.84875.1567610760320%40Atlassian.JIRA.
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title Patrick Grant commented on PUP-9996 Re: Stdlib : ensure_resources function does not throw an error if dependent resource type is missing Tested on PE 2019.1.0, (Puppet 6.4.2) Following my documented replication steps I was able to recreate. Following similar steps to TP's puppet apply replication, I could not. Both attempts are attached in 201910agenttest.txt 201910applytest.txt Seems to be more of an issue with puppet apply vs puppet agent from these replications and having spoken to Thomas Honey i've cloned this to the puppet project 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.323404.1567607979000.84803.1567608360078%40Atlassian.JIRA.
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-9996
Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
201910agenttest.txt, 201910applytest.txt, ensure_resources.txt
Created:
2019/09/04 7:39 AM
Priority:
Normal
Reporter:
Patrick Grant
Basic Info Module Version: puppetlabs-stdlib (v6.0.0) Puppet Version: PE 2018, (5.5.14) OS Name/Version: RHEL 7 agent Replication... Install the inifile module (puppetlabs-inifile (v3.1.0)) on a Master and use the following test code to apply a file to my test agent:
class ensurerestest{
ensure_resources ('ini_setting', {'sample' => {'ensure' => 'present', 'path' => '/tmp/foo.ini', 'section' => 'bar', 'setting' => 'baz', 'value' => 'quux'}})
}
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Ben Roberts commented on PUP-9990 Re: no_proxy config setting is ignored by puppet agent When set only in puppet.conf, and nothing in the environment, it connect fine. [root ~]# printenv | grep -i proxy [root ~]# grep proxy /etc/puppetlabs/puppet/puppet.conf http_proxy_host = webproxy.example.com http_proxy_port = 3128 no_proxy = 10.0.0.0/8,local,*.local,127.0.0.1,localhost,*.example.com,example.com,master1,master2 [root ~]# puppet agent --test --server_list master1 --noop --verbose --http_debug opening connection to master1:8140... opened starting SSL for master1:8140... SSL established <- "GET /status/v1/simple/master HTTP/1.1\r\nAccept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3\r\nAccept: */*\r\nUser-Agent: Puppet/6.8.0 Ruby/2.5.3-p105 (x86_64-linux)\r\nHost: master1:8140\r\n\r\n" -> "HTTP/1.1 200 OK\r\n" -> "Date: Wed, 04 Sep 2019 14:11:21 GMT\r\n"
Jira (PUP-9992) FAIL COMMAND "PUPPET AGENT --TEST" for puppet agent versión 6 on node client Error: Could not run: 403 "Forbidden"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9992 FAIL COMMAND "PUPPET AGENT --TEST" for puppet agent versión 6 on node client Error: Could not run: 403 "Forbidden" Change By: Josh Cooper Fix Version/s: PUP 6.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323109.1567411706000.84762.1567606380398%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper commented on PUP-9990 Re: no_proxy config setting is ignored by puppet agent The no_proxy setting should be added to the configuration reference. /cc Jean Bond But I can't reproduce the issue as described: $ cat ~/.puppetlabs/etc/puppet/puppet.conf [main] server = puppet.delivery.puppetlabs.net http_proxy_host = doesntexist.example.com http_proxy_port= no_proxy=*.delivery.puppetlabs.net $ env http_proxy=doesntexist.example.com bundle exec puppet agent -t --server_list puppet.delivery.puppetlabs.net Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Caching catalog for XXX Info: Applying configuration version '1567605099'
Jira (FACT-2011) Kernel and memory facts for Windows
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2011 Kernel and memory facts for Windows Issue Type: Task Assignee: Oana Tanasoiu Created: 2019/09/04 4:43 AM Priority: Normal Reporter: Oana Tanasoiu 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
Jira (PUP-9934) AIX user resource fails
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9934 AIX user resource fails Change By: Mihai Buzgau Story Points: 5 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.319111.1564634229000.84683.1567597140353%40Atlassian.JIRA.
Jira (FACT-1992) autofs mountpoints being mounted by facter
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1992 autofs mountpoints being mounted by facter Change By: Mihai Buzgau Story Points: 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321294.156596424.84680.1567597080235%40Atlassian.JIRA.
Jira (PUP-9465) group resource type misunderstands/misuses libuser
Title: Message Title Gabriel Nagy commented on PUP-9465 Re: group resource type misunderstands/misuses libuser This makes me think we won't ever want to default this provider: https://bugzilla.redhat.com/show_bug.cgi?id=1028544#c2 with libuser itself probably being obsoleted within the next few years I believe it's right to implement it since the way this is being handled right now is wrong (using binaries from 2 different packages - shadow and libuser - in the same provider). We shouldn't prefer libuser if both groupadd and libuser are present since libuser doesn't have 1:1 parity with groupadd regarding its functionalities. For example, libuser doesn't support NIS accounts. 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.293306.1548368109000.84660.1567595880265%40Atlassian.JIRA.
Jira (PUP-9963) The 'value' field of 'selboolean' should accept Booleans
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9963 The 'value' field of 'selboolean' should accept Booleans Change By: Mihai Buzgau Sprint: NW PR - 2019-09-18 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320668.1565704234000.84632.1567590960243%40Atlassian.JIRA.
Jira (PUP-9934) AIX user resource fails
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9934 AIX user resource fails Change By: Mihai Buzgau Sprint: PR NW - Triage 2019-09-18 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.319111.1564634229000.84628.1567590900169%40Atlassian.JIRA.
Jira (PUP-9963) The 'value' field of 'selboolean' should accept Booleans
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9963 The 'value' field of 'selboolean' should accept Booleans Change By: Mihai Buzgau Sprint: PR NW - Triage 2019-09-18 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.320668.1565704234000.84626.1567590840496%40Atlassian.JIRA.
Jira (FACT-1992) autofs mountpoints being mounted by facter
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1992 autofs mountpoints being mounted by facter Change By: Mihai Buzgau Sprint: PR NW - Triage 2019-09-18 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.321294.156596424.84621.1567590840470%40Atlassian.JIRA.
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Ben Roberts commented on PUP-9990 Re: no_proxy config setting is ignored by puppet agent I have re-tested this. The circumstance under which it is using the proxy unexpectedly is when: puppet.conf contains http_proxy_host, http_proxy_port and no_proxy variables env var http_proxy is set env var no_proxy is not set The configuration reference docs state that env var http_proxy or HTTP_PROXY overrides the http_proxy_host and http_proxy_port config setting, but makes no note that these env vars also affect the no_proxy setting, which is counter-intuitive. no_proxy is not currently mentioned at all in https://puppet.com/docs/puppet/latest/configuration.html, the only place it's documented is https://puppet.com/docs/puppet/latest/release_notes_puppet.html#puppet-release-notes-x.8.0 which also does not indicate any relation to the http_proxy env var overriding it. This is perhaps a somewhat contrived example, we would normally have both http_proxy and no_proxy env vars set together, or not at all. The reason I found myself in the state of having one and not the other was while investigating the behaviour where the puppet config and env var for no_proxy had different values, so I unset the environment variable to try and debug, only to find the config file value was then not being used at all. Can you re-create this, and if so do you agree it's confusion and should be fixed (either via a behaviour change, or a documentation change)? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9465) group resource type misunderstands/misuses libuser
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9465 group resource type misunderstands/misuses libuser Change By: Mihai Buzgau Sprint: NW - 2019-08-21, NW - 2019-09-03 , NW - 2019-09-18 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.293306.1548368109000.84573.1567588623782%40Atlassian.JIRA.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Mihai Buzgau Sprint: NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03 , NW - 2019-09-18 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.267945.153332494.84544.1567588623503%40Atlassian.JIRA.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System Change By: Mihai Buzgau Sprint: PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03 , NW - 2019-09-18 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.310162.1558726819000.84528.1567588623310%40Atlassian.JIRA.
Jira (FACT-1919) blank/negative facter cache due to timed out EC2 metadata
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1919 blank/negative facter cache due to timed out EC2 metadata Change By: Mihai Buzgau Sprint: PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03 , NW - 2019-09-18 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.307267.1556898834000.84531.1567588623323%40Atlassian.JIRA.
Jira (PUP-9754) Log resident configuration upon daemon launch
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9754 Log resident configuration upon daemon launch Change By: Mihai Buzgau Sprint: PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03 , NW - 2019-09-18 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.312512.1560543853000.84536.1567588623401%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 Mihai Buzgau updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Mihai Buzgau Sprint: NW - 2019-08-21, NW - 2019-09-03 , NW - 2019-09-18 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.84568.1567588623761%40Atlassian.JIRA.
Jira (FACT-2003) Create fact formatter that supports multiple formats
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2003 Create fact formatter that supports multiple formats Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.322748.1567078267000.84496.1567587600165%40Atlassian.JIRA.
Jira (FACT-2002) Fix display of fact value
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2002 Fix display of fact value Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.322739.1567071049000.84495.1567587420088%40Atlassian.JIRA.
Jira (PUP-9992) FAIL COMMAND "PUPPET AGENT --TEST" for puppet agent versión 6 on node client Error: Could not run: 403 "Forbidden"
Title: Message Title Francisco José Fernández Cabezón commented on PUP-9992 Re: FAIL COMMAND "PUPPET AGENT --TEST" for puppet agent versión 6 on node client Error: Could not run: 403 "Forbidden" Goog morning Josh, thanks to your answer I could find the problem. The problem was in the environment variable for the proxy (http_proxy, https_proxy) The system interprets the request to the proxy and does not redirect to the internal server; however, I am surprised that this problem does not happen in puppet 5. Thanks for the attention. I close the 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.323109.1567411706000.84446.1567576980156%40Atlassian.JIRA.
