Jira (PUP-5908) Implement a PCore MsgPack Serializer
Title: Message Title Josh Cooper commented on PUP-5908 Re: Implement a PCore MsgPack Serializer Closing this, please reopen if it is still a concern. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.116992.145567328.5372.1583395020025%40Atlassian.JIRA.
Jira (PUP-6092) Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive)
Title: Message Title Josh Cooper commented on PUP-6092 Re: Identify Windows-specific file/folder flags in Windows (e.g. hidden, archive) It's unlikely that we'll address this issue anytime soon, so closing Please reopen if this is still a concern. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.123408.1458839379000.5371.1583394840030%40Atlassian.JIRA.
Jira (PUP-6212) Puppet Accepts an Empty Array for the "returns" Attribute of the "exec" Type
Title: Message Title Josh Cooper commented on PUP-6212 Re: Puppet Accepts an Empty Array for the "returns" Attribute of the "exec" Type Agree validation could be better but is unlikely to be fixed. Please reopen if this is still a concern. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.47839.1408036982000.5368.1583394720087%40Atlassian.JIRA.
Jira (PUP-6213) Puppet Accepts Strings for the "returns" Attribute of the "exec" Type
Title: Message Title Josh Cooper commented on PUP-6213 Re: Puppet Accepts Strings for the "returns" Attribute of the "exec" Type Agree validation could be better but is unlikely to be fixed. Please reopen if this is still a concern. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.47838.1408036355000.5367.1583394720033%40Atlassian.JIRA.
Jira (PUP-6516) support the same service name in resources with multiple providers
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6516 support the same service name in resources with multiple providers Change By: Josh Cooper Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.142012.1468838106000.5366.1583394600092%40Atlassian.JIRA.
Jira (PUP-6516) support the same service name in resources with multiple providers
Title: Message Title Josh Cooper commented on PUP-6516 Re: support the same service name in resources with multiple providers Trying to manage services across different providers seems like asking for trouble. I'm going to close this, please reopen if it's still a concern. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.142012.1468838106000.5365.1583394600037%40Atlassian.JIRA.
Jira (PUP-6648) Puppet 4.6.x breaks catalog.apply in unit tests
Title: Message Title Josh Cooper commented on PUP-6648 Re: Puppet 4.6.x breaks catalog.apply in unit tests Given Puppet 4 is EOL, I'm going to close this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.148877.1472042867000.5364.1583394420021%40Atlassian.JIRA.
Jira (PUP-7505) *nix forcelocal group management cannot handle varying encodings
Title: Message Title Josh Cooper commented on PUP-7505 Re: *nix forcelocal group management cannot handle varying encodings This may have been overtaken by recent events? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.189845.1494287651000.5363.1583393880091%40Atlassian.JIRA.
Jira (PUP-7505) *nix forcelocal group management cannot handle varying encodings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7505 *nix forcelocal group management cannot handle varying encodings Change By: Josh Cooper Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.189845.1494287651000.5362.1583393880036%40Atlassian.JIRA.
Jira (PUP-8515) Automate and record runs of puppet benchmarks
Title: Message Title Josh Cooper commented on PUP-8515 Re: Automate and record runs of puppet benchmarks That would be cool, but unlikely to happen, closing. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.239978.1520381823000.5346.1583392560028%40Atlassian.JIRA.
Jira (PUP-9196) Host type raises error for use of whitespace in host_aliases attribute while array delimiter is a whitespace
Title: Message Title Josh Cooper commented on PUP-9196 Re: Host type raises error for use of whitespace in host_aliases attribute while array delimiter is a whitespace The host type was moved to a module in puppet 6. So any changes would need to be applied to the module and possibility backported to puppet 5.5.x (or not). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.278670.1538573698000.5343.1583392080320%40Atlassian.JIRA.
Jira (PUP-9196) Host type raises error for use of whitespace in host_aliases attribute while array delimiter is a whitespace
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9196 Host type raises error for use of whitespace in host_aliases attribute while array delimiter is a whitespace Change By: Josh Cooper Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.278670.1538573698000.5342.1583392080277%40Atlassian.JIRA.
Jira (PUP-9196) Host type raises error for use of whitespace in host_aliases attribute while array delimiter is a whitespace
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9196 Host type raises error for use of whitespace in host_aliases attribute while array delimiter is a whitespace Change By: Josh Cooper Component/s: Language Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.278670.1538573698000.5336.1583392020113%40Atlassian.JIRA.
Jira (PUP-9256) Remove future_features setting and any code that depends on it
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9256 Remove future_features setting and any code that depends on it Change By: Josh Cooper Issue Type: New Feature Task Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.281581.1539984459000.5335.1583392020108%40Atlassian.JIRA.
Jira (PUP-9256) Remove future_features setting and any code that depends on it
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9256 Remove future_features setting and any code that depends on it Change By: Josh Cooper Summary: Review Remove future_features setting and any code blocks that depends on it Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.281581.1539984459000.5334.1583392020054%40Atlassian.JIRA.
Jira (PUP-9274) Documentation that clearly states the forward and backward compatibility statements between the Server and the Agent.
Title: Message Title Josh Cooper commented on PUP-9274 Re: Documentation that clearly states the forward and backward compatibility statements between the Server and the Agent. agents and servers within the same 6.x series are compatible agents < 6 are compatible with server 6.x agents 6.x are not necessarily compatible with servers < 6 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.281152.153982198.5333.1583391840024%40Atlassian.JIRA.
Jira (PUP-9297) Audit and fix locations where set_mode is called with inappropriate permissions on Windows
Title: Message Title
Josh Cooper commented on PUP-9297
Re: Audit and fix locations where set_mode is called with inappropriate permissions on Windows
There are only a few remaining places:
lib/puppet/configurer.rb:Puppet::Util.replace_file(Puppet[:lastrunfile], mode) do |fh|
lib/puppet/provider/service/rcng.rb: Puppet::Util.replace_file(rcfile, 0644) do |f|
lib/puppet/provider/service/rcng.rb: Puppet::Util.replace_file(rcfile, 0644) do |f|
lib/puppet/provider/service/upstart.rb:Puppet::Util.replace_file(file, 0644) do |f|
lib/puppet/provider/user/user_role_add.rb: Puppet::Util.replace_file(target_file_path, 0640) do |fh|
lib/puppet/ssl/host.rb:Puppet::Util.replace_file(file_path, 0644) do |f|
lib/puppet/ssl/host.rb:Puppet::Util.replace_file(certificate_request_location(name), 0644) do |file|
lib/puppet/ssl/host.rb: Puppet::Util.replace_file(crl_path, 0644) do |file|
lib/puppet/type/file.rb: Puppet::Util.replace_file(self[:path], mode_int, staging_location: self[:staging_location], validate_callback: validate_callback) do |file|
lib/puppet/util/reference.rb:Puppet::Util.replace_file("/tmp/puppetdoc.txt") {|f| f.puts text }
Jira (PUP-9297) Audit and fix locations where set_mode is called with inappropriate permissions on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9297 Audit and fix locations where set_mode is called with inappropriate permissions on Windows Change By: Josh Cooper Labels: beginner Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.283329.1541059084000.5326.1583391660116%40Atlassian.JIRA.
Jira (PUP-9297) Audit and fix locations where set_mode is called with inappropriate permissions on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9297 Audit and fix locations where set_mode is called with inappropriate permissions on Windows Change By: Josh Cooper Team: Windows Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.283329.1541059084000.5327.1583391660159%40Atlassian.JIRA.
Jira (PUP-6728) Active Directory Integration Improvements
Title: Message Title Josh Cooper commented on PUP-6728 Re: Active Directory Integration Improvements Closing this epic, please reopen if needed. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.153175.1474567879000.5318.1583391180561%40Atlassian.JIRA.
Jira (PUP-5450) Windows integration with local certificate store
Title: Message Title Josh Cooper commented on PUP-5450 Re: Windows integration with local certificate store It would not be too difficult to write a CertProvider that retrieved keys and certs from the local Windows store, but given that this ticket hasn't been updated in more than 2 years, I'm closing it. Please reopen if this is still a concern. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.103392.1446075931000.5306.1583391120022%40Atlassian.JIRA.
Jira (PUP-5971) Define evaluation should be evaluated depth-first, not breadth-first
Title: Message Title Josh Cooper commented on PUP-5971 Re: Define evaluation should be evaluated depth-first, not breadth-first We're not going to change this, closing. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.118495.1456356457000.5300.1583390700052%40Atlassian.JIRA.
Jira (PUP-7694) metadata.json created with `puppet module generate --skip-interview` fails validation
Title: Message Title Josh Cooper commented on PUP-7694 Re: metadata.json created with `puppet module generate --skip-interview` fails validation puppet module generate was removed in puppet 6. Please reopen and move to the pdk project if this is still an issue. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.197615.1498247562000.5282.1583390520023%40Atlassian.JIRA.
Jira (PUP-8059) rake validate fails on modules with plans
Title: Message Title Josh Cooper commented on PUP-8059 Re: rake validate fails on modules with plans Module validation has been moved to the pdk, so I'm going to close this. Please reopen or move to the pdk project if this is still an issue. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.216337.1508172924000.5281.1583390460032%40Atlassian.JIRA.
Jira (PUP-6237) PMT should gracefully fall back to older, compatible versions of modules
Title: Message Title Josh Cooper commented on PUP-6237 Re: PMT should gracefully fall back to older, compatible versions of modules This makes sense, but hasn't been worked on in many years and is unlikely to be worked on anytime soon. Please reopen if this is still a concern. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.128471.146171335.5278.1583390220028%40Atlassian.JIRA.
Jira (PUP-5626) Missing the dependencies key in metadata.json breaks puppet module tool
Title: Message Title Josh Cooper commented on PUP-5626 Re: Missing the dependencies key in metadata.json breaks puppet module tool This is still an issue, but is unlikely to be fixed anytime soon. Please reopen if this is still a concern. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.110015.1450388931000.5277.1583390100027%40Atlassian.JIRA.
Jira (PUP-6813) module face: `install` should report back on which dependencies were not satisfiable
Title: Message Title Josh Cooper commented on PUP-6813 Re: module face: `install` should report back on which dependencies were not satisfiable PUP-9176 has steps to reproduce, so I'm closing this as a dup. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.156307.1476292924000.5276.1583389980076%40Atlassian.JIRA.
Jira (PUP-9176) puppet module install should list unsatisfiable dependencies if installation fails
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9176
puppet module install should list unsatisfiable dependencies if installation fails
Change By:
Josh Cooper
When {{puppet module}} install fails to find a module version for which dependencies can be satisfied, the operation fails with an error message. The message does not include any information about which dependency could not be satisfied which leaves no starting point for debugging and resolving the issue.h2. Reproduction Case - Install Puppet 6 on CentOS 7:{code:bash}rpm -Uvh http://yum.puppetlabs.com/puppet6/puppet6-release-el-7.noarch.rpmyum install -y puppet-agentsource /etc/profile.d/puppet-agent.sh{code} - Install the latest version of puppetlabs-stdlib:{code:bash}puppet module install puppetlabs-stdlib{code} - Attempt to install v0.4.0 of puppetlabs-puppet_authorization, which depends on stdlib "< 5.0.0":{code:bash}puppet module install puppetlabs-puppet_authorization -- verson version 0.4.0{code}h3. OutcomeInstallation fails with an error about unsatisfiable dependencies, but no information on which dependency could not be satisfied:{noformat}# puppet module install puppetlabs-stdlibNotice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppet.com ...Notice: Installing -- do not interrupt .../etc/puppetlabs/code/environments/production/modules└── puppetlabs-stdlib (v5.0.0)# puppet module install puppetlabs-puppet_authorization --version 0.4.0Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppet.com ...Error: Could not install module 'puppetlabs-puppet_authorization' (???) No version of 'puppetlabs-puppet_authorization' can satisfy all dependencies Use `puppet module install --ignore-dependencies` to install only this module{noformat}h3. Expected OutcomeThe error message lists {{puppetlabs-stdlib}}, its version, and the unsatisfiable dependency "< 5.0.0" that caused installation to fail. The module where the unsatisfiable dependency occurred should also be listed as this error can arise from transitive dependencies. E.g. a dependency of a dependency of the module being installed cannot have its constraints satisfied.
Jira (PUP-5196) puppet module tool validates the wrong directory when used w/ --environment
Title: Message Title Josh Cooper commented on PUP-5196 Re: puppet module tool validates the wrong directory when used w/ --environment This was fixed awhile ago, I think when we started explicitly passing the current environment: [root@resonant-try ~]# puppet module install puppetlabs/motd --version 1.0.0 Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from https://forgeapi.puppet.com ... Notice: Installing -- do not interrupt ... /etc/puppetlabs/code/environments/production/modules └── puppetlabs-motd (v1.0.0) [root@resonant-try ~]# mkdir /etc/puppetlabs/code/environments/dev [root@resonant-try ~]# puppet module install puppetlabs/motd --environment dev Notice: Preparing to install into /etc/puppetlabs/code/environments/dev/modules ... Notice: Created target directory /etc/puppetlabs/code/environments/dev/modules Notice: Downloading from https://forgeapi.puppet.com ... Notice: Installing -- do not interrupt ...
Jira (PUP-3439) PMT can't accept deflate (zlib) compressed content from the forge
Title: Message Title Josh Cooper commented on PUP-3439 Re: PMT can't accept deflate (zlib) compressed content from the forge Puppet's new HTTP client relies on ruby to compress/decompress, so there's nothing for us to do here. Closing. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.54229.1412963725000.5265.1583389500023%40Atlassian.JIRA.
Jira (PUP-6846) Obscure error messages caused by error in metadata.json of a module.
Title: Message Title Josh Cooper commented on PUP-6846 Re: Obscure error messages caused by error in metadata.json of a module. puppet module build was removed in puppet 6 and has been replaced by the pdk. As this hasn't seen any activity in 2+ years, I'm going to close it. Please reopen a new ticket against the pdk if it is still an issue. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.158515.1477577592000.5256.1583389320096%40Atlassian.JIRA.
Jira (PUP-6587) `puppet module search --render-as json` returns non-JSON first line on stdout
Title: Message Title Josh Cooper commented on PUP-6587 Re: `puppet module search --render-as json` returns non-JSON first line on stdout Agree this is a problem, but unlikely to be fixed. Please reopen if need be. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.145353.1470377055000.5255.1583388840024%40Atlassian.JIRA.
Jira (PUP-6658) Support puppet-REST integration
Title: Message Title Josh Cooper commented on PUP-6658 Re: Support puppet-REST integration This hasn't been updated in years, and we introduced the resource-api as a way to simplify custom providers, so I'm going to close this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.149299.1472242906000.5254.1583388780084%40Atlassian.JIRA.
Jira (PUP-7873) Windows Custom event log - Research puppetres.dll dependencies
Title: Message Title Josh Cooper commented on PUP-7873 Re: Windows Custom event log - Research puppetres.dll dependencies We now use %SystemRoot%\System32\EventCreate.exe instead of puppptres.dll which avoids issues when upgrading the dll, but it's locked because the eventviewer has loaded it. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.207117.1503523534000.5252.1583388540026%40Atlassian.JIRA.
Jira (PUP-5633) gem provider doesn't remove old gem version
Title: Message Title Josh Cooper commented on PUP-5633 Re: gem provider doesn't remove old gem version The gem version isn't part of the "name" so when a new version is specified, puppet interprets that to mean install the 2nd version, not uninstall the old version and install the new version. To do that we'd need a parameter that indicates only the specified version(s) should be installed, and any version not listed should be uninstalled. It's similar to how the auth_membrership property controls members of a group. That said we're unlikely to fix this anytime soon. Please reopen if it's still a concern. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.110407.1450811254000.5245.1583388000121%40Atlassian.JIRA.
Jira (PUP-6680) Descendant providers do not inherit features from ancestors
Title: Message Title Josh Cooper commented on PUP-6680 Re: Descendant providers do not inherit features from ancestors The gem provider was recently modified to accept a targetable command so that subclassing the gem provider is not necessary. Closing this as we're unlikely to fix the issue of features not being inherited by provider subclasses. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.150528.1473126282000.5243.1583387580093%40Atlassian.JIRA.
Jira (PUP-6939) New users are confused by package's ensure=>$version
Title: Message Title Josh Cooper commented on PUP-6939 Re: New users are confused by package's ensure=>$version We're unlikely to deprecate specifying version strings in the package ensure property as this would literally cause issues for every puppet user. Closing this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.163586.1479985607000.5242.1583387400021%40Atlassian.JIRA.
Jira (PUP-7750) puppet resource service fails on FreeBSD 11
Title: Message Title Josh Cooper commented on PUP-7750 Re: puppet resource service fails on FreeBSD 11 I'm going to close this due to inactivity and based on Geoff's comments above. Please reopen if/when you have a PR. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.198902.1499190688000.5231.1583387160032%40Atlassian.JIRA.
Jira (PUP-10356) Empty YAML files cause warnings in yaml_data and eyaml_lookup_key functions
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-10356 Empty YAML files cause warnings in yaml_data and eyaml_lookup_key functions Change By: Glenn Sarti *Puppet Version: 6.x* *Puppet Server Version: N/A* *OS Name/Version:* When using a valid but empty YAML file in the hiera hierarchy the logs spew out a lot of warnings about expecting a hash.While I can understand the warnings when there's a type mismatch (e.g. Got a String instead of a Hash), and but an empty file is deliberate act with no data (e . g. commenting everything out). Therefore Puppet should not raise a warning for empty YAML files. *Desired Behavior:*Empty YAML files do not raise warnings*Actual Behavior:* Warnings can be seen in puppet apply or puppet agent command Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 (PDB-4673) Provide a PQL operator that uses LIKE rather than a regex match
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-4673 Provide a PQL operator that uses LIKE rather than a regex match Change By: Austin Boyd Labels: jira_escalated Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348763.1583374635000.5224.1583374980335%40Atlassian.JIRA.
Jira (PDB-4673) Provide a PQL operator that uses LIKE rather than a regex match
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-4673 Provide a PQL operator that uses LIKE rather than a regex match Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 38273 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348763.1583374635000.5223.1583374980290%40Atlassian.JIRA.
Jira (PDB-4673) Provide a PQL operator that uses LIKE rather than a regex match
Title: Message Title Adam Bottchen created an issue PuppetDB / PDB-4673 Provide a PQL operator that uses LIKE rather than a regex match Issue Type: Improvement Assignee: Unassigned Created: 2020/03/04 6:17 PM Priority: Normal Reporter: Adam Bottchen Problem Right now, PQL only provides access to the regex pattern match operator. As seen in multiple customer cases, and highlighted in CDPE-2927, this operator can lead to significantly slower queries to postgres when compared to the LIKE operator. In an example dataset from a customer system, a query using the regex operator took 7 minutes to complete, but only 2.5 seconds when replaced with LIKE, as the query planner was able to prioritize the correct index. Recommendation Provide a PQL operator that translates into LIKE when building the resulting SQL to provide users the choice. Add Comment
Jira (PUP-10356) Empty YAML files cause warnings in yaml_data and eyaml_lookup_key functions
Title: Message Title Glenn Sarti created an issue Puppet / PUP-10356 Empty YAML files cause warnings in yaml_data and eyaml_lookup_key functions Issue Type: Bug Assignee: Unassigned Created: 2020/03/04 6:17 PM Environment: N/A Priority: Normal Reporter: Glenn Sarti Puppet Version: 6.x Puppet Server Version: N/A OS Name/Version: When using a valid but empty YAML file in the hiera hierarchy the logs spew out a lot of warnings about expecting a hash. While I can understand the warnings when there's a type mismatch (e.g. Got a String instead of a Hash), and empty file is deliberate act with no data. Therefore Puppet should not raise a warning for empty YAML files. Desired Behavior: Empty YAML files do not raise warnings Actual Behavior: Warnings can be seen in puppet apply or puppet agent command Add Comment
Jira (PUP-10353) Change http client API to generic options hash
Title: Message Title Josh Cooper assigned an issue to Melissa Stone Puppet / PUP-10353 Change http client API to generic options hash Change By: Josh Cooper Assignee: Melissa Stone Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348571.1583350288000.5127.1583367420032%40Atlassian.JIRA.
Jira (PUP-10355) Can't disable Puppet::SSL::Host deprecation warning when using puppetdb terminus
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10355 Can't disable Puppet::SSL::Host deprecation warning when using puppetdb terminus Change By: Josh Cooper Summary: PuppetDB module uses deprecated http_instance method Can't disable Puppet::SSL::Host deprecation warning when using puppetdb terminus Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.321972.1566497006000.5080.1583363400032%40Atlassian.JIRA.
Jira (PUP-10355) PuppetDB module uses deprecated http_instance method
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-10355 PuppetDB module uses deprecated http_instance method Change By: Josh Cooper Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.321972.1566497006000.5007.1583362380771%40Atlassian.JIRA.
Jira (PUP-10355) PuppetDB module uses deprecated http_instance method
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10355 PuppetDB module uses deprecated http_instance method Change By: Josh Cooper Sprint: Coremunity Hopper Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.321972.1566497006000.5008.1583362380819%40Atlassian.JIRA.
Jira (PUP-10355) PuppetDB module uses deprecated http_instance method
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10355 PuppetDB module uses deprecated http_instance method Change By: Josh Cooper Epic Link: PUP-8550 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.321972.1566497006000.5006.1583362380727%40Atlassian.JIRA.
Jira (PUP-10355) PuppetDB module uses deprecated http_instance method
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10355 PuppetDB module uses deprecated http_instance method Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.321972.1566497006000.4991.1583362320243%40Atlassian.JIRA.
Jira (PUP-10355) PuppetDB module uses deprecated http_instance method
Title: Message Title Josh Cooper moved an issue Puppet / PUP-10355 PuppetDB module uses deprecated http_instance method Change By: Josh Cooper Key: PDB PUP - 4488 10355 Project: PuppetDB Puppet Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.321972.1566497006000.4990.1583362320199%40Atlassian.JIRA.
Jira (PDB-4488) PuppetDB module uses deprecated http_instance method
Title: Message Title Josh Cooper commented on PDB-4488 Re: PuppetDB module uses deprecated http_instance method Coming back to this. The intention was to deprecate Puppet::Network::HttpPool.http_instance in documentation only, while adding a hard deprecation warning to Puppet::SSL::Host. The trouble is that the former relies on the latter, which is why you see Puppet::SSL::Host is deprecated. It should be possible to fix puppet's HttpPool.http_instance method to not trigger the deprecation warning. I'll move this back to the PUP project. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.321972.1566497006000.4989.1583362320146%40Atlassian.JIRA.
Jira (PUP-10353) Change http client API to generic options hash
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10353
Change http client API to generic options hash
Change By:
Josh Cooper
Acceptance Criteria:
Keep url, params, headers, options for get, post, etcValidate options that we currently recognize like user, password, ssl_context, include_system_storeSome methods may need extra validation like passing content_type and body to the {{put}} method.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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.348571.1583350288000.4920.1583359860203%40Atlassian.JIRA.
Jira (PUP-10353) Change http client API to generic options hash
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10353 Change http client API to generic options hash Change By: Melissa Stone Sprint: Coremunity Grooming Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348571.1583350288000.4863.1583358840028%40Atlassian.JIRA.
Jira (PUP-10324) Forward http client requests to puppetserver
Title: Message Title Melissa Stone assigned an issue to Unassigned Puppet / PUP-10324 Forward http client requests to puppetserver Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348081.1583171843000.4861.1583358780422%40Atlassian.JIRA.
Jira (PUP-10324) Forward http client requests to puppetserver
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10324 Forward http client requests to puppetserver Change By: Melissa Stone Sprint: Platform Core KANBAN Coremunity Grooming Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348081.1583171843000.4862.1583358780464%40Atlassian.JIRA.
Jira (PUP-7737) Add HTTP report processor setting for including system truststore
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7737
Add HTTP report processor setting for including system truststore
Change By:
Josh Cooper
Acceptance Criteria:
Add a puppet setting to include the system CA store when posting the report to an HTTPS URL.If enabled, pass {{include_system_store: true}} in the call to {{Client#post}}.For this ticket, it will only affect when the {{http}} report processor is used in puppet apply. A separate SERVER ticket will be needed to update puppetserver's HTTP client implementation.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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.198103.1498609351000.4852.1583358660049%40Atlassian.JIRA.
Jira (PUP-10316) Update http report processor to use http client
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10316
Update http report processor to use http client
Change By:
Josh Cooper
Acceptance Criteria:
When the http report processor receives a report, it should post the report to {{Puppet[:reporturl]}} using the new Puppet::HTTP::Client API. When using puppetserver, it should use the ExternalClient implementation created when puppetserver registered its http_client_class. When using {{puppet apply}} it should use the default Client implementation.The post request should include {{metric_id}} and if specified, user/password credentials for basic authentication.The post request should only trust the puppet PKI.The processor should receive a Puppet::HTTP::Response and may need to rescue Puppet::HTTP::HTTPError or subclasses.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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.347625.1582698076000.4844.1583358180091%40Atlassian.JIRA.
Jira (PUP-10324) Forward http client requests to puppetserver
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10324 Forward http client requests to puppetserver Change By: Melissa Stone Sprint: Coremunity Grooming Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348081.1583171843000.4733.1583356740048%40Atlassian.JIRA.
Jira (PUP-10324) Forward http client requests to puppetserver
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-10324 Forward http client requests to puppetserver Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348081.1583171843000.4734.1583356740092%40Atlassian.JIRA.
Jira (PUP-10320) Secondary group handling causing issues in 6.13.0
Title: Message Title Robert Brooks commented on PUP-10320 Re: Secondary group handling causing issues in 6.13.0 Ciprian Badescu I can confirm 6.13.0 with your patch applied no longer exhibits the issue shown above. Many thanks! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347941.1582919251000.4642.1583353860028%40Atlassian.JIRA.
Jira (PUP-10154) Detect connection errors when using TLS 1.3 and using post-handshake authentication
Title: Message Title Josh Cooper commented on PUP-10154 Re: Detect connection errors when using TLS 1.3 and using post-handshake authentication Puppetserver doesn't support TLSv1.3: $ openssl s_client -connect red-overhead.delivery.puppetlabs.net:8140 -tls1_3 CONNECTED(0005) 4754687424:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:ssl/record/rec_layer_s3.c:1544:SSL alert number 40 --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 7 bytes and written 260 bytes Verification: OK --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported
Jira (PUP-10353) Change http client API to generic options hash
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10353 Change http client API to generic options hash Change By: Josh Cooper Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348571.1583350288000.4562.1583351700117%40Atlassian.JIRA.
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 Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.51011.1410505537000.4561.1583351700111%40Atlassian.JIRA.
Jira (PUP-10354) Add HTTP client yardocs and mark as private
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10354 Add HTTP client yardocs and mark as private Change By: Josh Cooper Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348573.1583350439000.4563.1583351700123%40Atlassian.JIRA.
Jira (PUP-10354) Add HTTP client yardocs and mark as private
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10354 Add HTTP client yardocs and mark as private Change By: Josh Cooper Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348573.1583350439000.4538.1583351340092%40Atlassian.JIRA.
Jira (PUP-10353) Change http client API to generic options hash
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10353 Change http client API to generic options hash Change By: Josh Cooper Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348571.1583350288000.4537.1583351340046%40Atlassian.JIRA.
Jira (PUP-10314) Puppet tries to print ssl information for non-ssl connections in debug mode
Title: Message Title Josh Cooper commented on PUP-10314 Re: Puppet tries to print ssl information for non-ssl connections in debug mode Passed CI in e0ec65484c Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347571.1582668582000.4521.1583351100056%40Atlassian.JIRA.
Jira (PUP-10347) Client does not reconnect when the server closes a persistent connection
Title: Message Title Josh Cooper commented on PUP-10347 Re: Client does not reconnect when the server closes a persistent connection Passed CI in e0ec65484cf84f51db5e7d7a4901e624b082c810 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348479.158328511.4520.1583351040022%40Atlassian.JIRA.
Jira (PUP-10354) Add HTTP client yardocs and mark as private
Title: Message Title Josh Cooper created an issue Puppet / PUP-10354 Add HTTP client yardocs and mark as private Issue Type: Task Assignee: Unassigned Created: 2020/03/04 11:33 AM Priority: Normal Reporter: Josh Cooper 1. Add yardoc for Puppet::HTTP::* classes, Puppet::Runtime 2. Tag each class as @api private Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10353) Change http client API to generic options hash
Title: Message Title Josh Cooper created an issue Puppet / PUP-10353 Change http client API to generic options hash Issue Type: Bug Assignee: Unassigned Created: 2020/03/04 11:31 AM Priority: Normal Reporter: Josh Cooper The HTTP client API needs to use a generic options hash instead of keyword arguments for two reasons: 1. The API currently uses keyword arguments, but we need to add a puppetserver implementation. If we add a new argument to puppet's implementation, then it will break puppetserver, unless it collects "extra" options using **options. But then we'll end up with some arguments expressed as keyword arguments and some "leftovers". 2. Callers of the API sometimes pass options that the client implementation doesn't know about, such as compress. The API needs a way to pass options which may only be understood by one implementation. Each implementation should parse and validate options it recognizes and pass through options it doesn't. Add Comment
Jira (PUP-10324) Forward http client requests to puppetserver
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10324
Forward http client requests to puppetserver
Change By:
Josh Cooper
Acceptance Criteria:
It should be possible to write a custom function or report processor that makes POST and GET requests using the HTTP client when running in puppetserver. Add the following report processor to {{lib/puppet/reports/myreport.rb}}.{code:ruby}Puppet::Reports.register_report(:myreport) do def processclient = Puppet.runtime['http'] client.get(URI("https://.delivery.puppetlabs.net:8140/status/v1/simple"))client.post(URI("https://.delivery.puppetlabs.net:8140/puppet/v3/catalog/#{Puppet[:certname]}?environment=production"), content_type: 'text/plain', body: '')endend{code}Register the processor in {{puppet.conf}}:{code:ini}[main]reports = myreport{code}Run {{puppet agent -t}} and verify puppetserver successfully gets & posts.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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-10324) Forward http client requests to puppetserver
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10324
Forward http client requests to puppetserver
Change By:
Josh Cooper
Acceptance Criteria:
It should be possible to write a custom function or report processor that makes POST and GET requests using the HTTP client when running in puppetserver. Add the following report processor to {{lib/puppet/reports/myreport.rb}}. {code:ruby} Puppet::Reports.register_report(:myreport) do def processclient = Puppet.runtime['http'] client.get(URI("https://.delivery.puppetlabs.net:8140/status/v1/simple"))client.post(URI("https://.delivery.puppetlabs.net:8140/puppet/v3/catalog/#{Puppet[:certname]}?environment=production"), content_type: 'text/plain', body: '')endend{code} Register the processor in {{puppet.conf}}: {code:ini} [main]reports = myreport{code} Run {{puppet agent -t}} and verify puppetserver successfully gets & posts.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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-10320) Secondary group handling causing issues in 6.13.0
Title: Message Title Ciprian Badescu commented on PUP-10320 Re: Secondary group handling causing issues in 6.13.0 Robert Brooks, is this helpfull: https://github.com/puppetlabs/puppet/commit/8feb8baca243a76b8d9ed283497d71a0622c24e9.patch I think correction will also be available in the next nightly at http://nightlies.puppet.com/index_by_name.html Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347941.1582919251000.4363.1583349720083%40Atlassian.JIRA.
Jira (PUP-10316) Update http report processor to use http client
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10316
Update http report processor to use http client
Change By:
Josh Cooper
The {{http}} report processor calls {{Puppet::Network::HttpPool}} to post the report to {{Puppet[:reporturl]}}. Modify the processor to use {{Puppet::HTTP::Client#post}} instead. It should continue to send the same query parameters, eg ( {{metric_id}}, {{content-type}}, basic authentication, etc as it currently does. It should continue to only trust the puppet PKI.This is blocked on puppetserver integration PUP-10324
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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.347625.1582698076000.4303.158334929%40Atlassian.JIRA.
Jira (PUP-10325) Custom file mode for lastrunreport as defined in puppet.conf is ignored
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10325 Custom file mode for lastrunreport as defined in puppet.conf is ignored Change By: Josh Cooper Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348140.1583195074000.4288.1583348760104%40Atlassian.JIRA.
Jira (PUP-10325) Custom file mode for lastrunreport as defined in puppet.conf is ignored
Title: Message Title Josh Cooper commented on PUP-10325 Re: Custom file mode for lastrunreport as defined in puppet.conf is ignored # git bisect start 6.13.0 6.8.1 Bisecting: a merge base must be tested [c956ad95fcdd9aabb28e196b55d1f112b5944777] (packaging) Updating manpage file for master # git bisect run ./gitcheck.rb running ./gitcheck.rb world readable Bisecting: 464 revisions left to test after this (roughly 9 steps) [0e948b8072b5aadbd04a54069f665f544d6373ff] (PUP-10033) Thread ssl_context from service to client running ./gitcheck.rb world readable Bisecting: 230 revisions left to test after this (roughly 8 steps) [a17761d60b2e5d42cc01a36e1d6ba3d790c9dcf8] Merge remote-tracking branch 'upstream/6.4.x' running ./gitcheck.rb
Jira (PUP-10325) Custom file mode for lastrunreport as defined in puppet.conf is ignored
Title: Message Title
Josh Cooper commented on PUP-10325
Re: Custom file mode for lastrunreport as defined in puppet.conf is ignored
I can reproduce also:
# puppet agent -t --debug | grep last_run
Debug: Using settings: adding file resource 'lastrunfile': 'File[/var/tmp/puppet/last_run_summary.yaml]{:path=>"/var/tmp/puppet/last_run_summary.yaml", :mode=>"664", :ensure=>:file, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'lastrunreport': 'File[/var/tmp/puppet/last_run_report.yaml]{:path=>"/var/tmp/puppet/last_run_report.yaml", :mode=>"664", :ensure=>:file, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: /File[/var/tmp/puppet/last_run_report.yaml]/mode: mode changed '0660' to '0664'
# ls -la /var/tmp/puppet/last_run_report.yaml
-rw-rw 1 root root 173233 Mar 4 18:28 /var/tmp/puppet/last_run_report.yaml
Add Comment
Jira (PUP-5069) Puppet's HTTP API does not allow callers to trust system cacerts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5069 Puppet's HTTP API does not allow callers to trust system cacerts Change By: Josh Cooper Release Notes: Enhancement Release Notes Summary: The HTTP client now accepts a parameter to trust the system certificate store when making HTTPS connections. By default, it only trusts the puppet PKI. The API is private and may change in a future release. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.94774.1440440148000.4221.1583347560211%40Atlassian.JIRA.
Jira (PUP-10320) Secondary group handling causing issues in 6.13.0
Title: Message Title Robert Brooks commented on PUP-10320 Re: Secondary group handling causing issues in 6.13.0 Ciprian Badescu is a patched package available? Github doesn't seem to want to give me a diff/patch. I can provide the manifest privately, but it does a lot of things and I would need to anonymize users etc. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347941.1582919251000.4219.1583347560163%40Atlassian.JIRA.
Jira (PUP-10350) Abort puppet run if empty values retrieved
Title: Message Title Henrik Lindberg commented on PUP-10350 Re: Abort puppet run if empty values retrieved In hiera 5 there is a difference between nil and empty string - both are valid as values in yaml - if that is what you are asking. As long as the backend signals "not found" as it should I think it should be possible to return both "undef" and empty string. This because you may want to be able to override some other bound value with "nothing". A user can do a type cast to String[1] to ensure they do not get undef or empty string. (but may be difficult in practice - not sure if it returns Sensitive or not). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348512.1583314551000.4220.1583347560168%40Atlassian.JIRA.
Jira (PUP-10315) Replace find_functional_server call with http client
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10315 Replace find_functional_server call with http client Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Puppet agents use the new HTTP client to resolve the first available server in the server_list setting. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347624.1582687503000.4216.1583347500059%40Atlassian.JIRA.
Jira (PUP-10347) Client does not reconnect when the server closes a persistent connection
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10347 Client does not reconnect when the server closes a persistent connection Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: It was possible for the new HTTP client to try to use a cached HTTP connection, but fail if the server had previously said the connection should be kept alive, but decided to close it later, such as if the server restarted. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348479.158328511.4215.1583347380298%40Atlassian.JIRA.
Jira (PUP-9932) [SPIKE] Can we make 3x functions loaders thread-safe?
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9932 [SPIKE] Can we make 3x functions loaders thread-safe? Change By: Maggie Dreyer Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.306743.1556579117000.4208.1583347080441%40Atlassian.JIRA.
Jira (PUP-9932) [SPIKE] Can we make 3x functions loaders thread-safe?
Title: Message Title Josh Cooper commented on PUP-9932 Re: [SPIKE] Can we make 3x functions loaders thread-safe? Merged to master in https://github.com/puppetlabs/puppet/commit/2e9661f8359ca09387cafd8f783b14f23ec8a5fb. Is there anything else needed for this ticket? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.306743.1556579117000.4209.1583347080484%40Atlassian.JIRA.
Jira (PUP-10315) Replace find_functional_server call with http client
Title: Message Title Melissa Stone commented on PUP-10315 Re: Replace find_functional_server call with http client merged into master with https://github.com/puppetlabs/puppet/commit/38edbcd2f7904ca4ab4207ede46eebdd022c328a Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347624.1582687503000.4181.1583346540022%40Atlassian.JIRA.
Jira (PUP-10350) Abort puppet run if empty values retrieved
Title: Message Title Josh Cooper commented on PUP-10350 Re: Abort puppet run if empty values retrieved I imagine someone is relying on lookup being able to return an empty string, which is different than nil. I think we'd need to pass an argument to the lookup call to reject empty strings. Thoughts Henrik Lindberg? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348512.1583314551000.4164.1583346360118%40Atlassian.JIRA.
Jira (PUP-5069) Puppet's HTTP API does not allow callers to trust system cacerts
Title: Message Title Melissa Stone commented on PUP-5069 Re: Puppet's HTTP API does not allow callers to trust system cacerts Merged into master with https://github.com/puppetlabs/puppet/commit/001a141fc18db46e3274256784614ed8a8e2b79a Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.94774.1440440148000.4096.1583344980467%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10351 Puppet Agent fails to self-restart on config change or update Change By: Josh Cooper Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348520.1583329295000.4040.1583344500199%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title
Josh Cooper commented on PUP-10351
Re: Puppet Agent fails to self-restart on config change or update
I cannot reproduce this using nightly puppet-agent in cases where I send it HUP, USR1 or edit puppet.conf. This may have been fixed by the state pidfile detection correctly handling LWP on Linux. See PUP-10218.
root@worse-mandate:~# puppet resource package puppet-agent
package { 'puppet-agent':
ensure => '6.13.0.111.g401fef03-1xenial',
provider => 'apt',
}
# systemctl status puppet
● puppet.service - Puppet agent
Loaded: loaded (/lib/systemd/system/puppet.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-03-04 17:46:55 UTC; 4min 54s ago
Main PID: 2165 (puppet)
CGroup: /system.slice/puppet.service
└─2165 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent --no-daemonize
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10351 Puppet Agent fails to self-restart on config change or update Change By: Josh Cooper Epic Link: PUP-7532 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348520.1583329295000.4039.1583344500155%40Atlassian.JIRA.
Jira (PUP-10285) Puppet upgrade should prevent a Puppet run from occurring
Title: Message Title Josh Cooper commented on PUP-10285 Re: Puppet upgrade should prevent a Puppet run from occurring It's not possible to stage the upgrade and then atomically switch over given that we rely on Windows Installer (MSI) to perform the upgrade. Another complicating issue is Windows does not allow a program to be overwritten while it is running, unlike *nix. In particular we can't overwrite ruby.exe or any of its loaded dlls while it's running. I think the next best thing would be to have the pupet_agent module drop a lock file in place prior to running and cleaning it up when it's done. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.345634.1581107584000.4013.1583343900053%40Atlassian.JIRA.
Jira (PDB-4672) Add at-at periodic monitor to check for migration mismatch
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4672 Add at-at periodic monitor to check for migration mismatch Change By: Zachary Kent Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.348442.1583265198000.3968.1583343420042%40Atlassian.JIRA.
Jira (PUP-9820) managing a File user or group or mode breaks require on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9820 managing a File user or group or mode breaks require on Windows Change By: Josh Cooper Team: Night's Watch Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.316149.1562868793000.3946.1583342760087%40Atlassian.JIRA.
Jira (PUP-9820) managing a File user or group or mode breaks require on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9820 managing a File user or group or mode breaks require on Windows Change By: Josh Cooper Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.316149.1562868793000.3945.1583342760045%40Atlassian.JIRA.
Jira (PUP-8956) puppet agent doesn't run properly when avast anti-virus running
Title: Message Title Josh Cooper commented on PUP-8956 Re: puppet agent doesn't run properly when avast anti-virus running There haven't been any updates to this ticket in nearly 2 years. Going to close as there doesn't seem to be anything actionable here. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.262540.1529833586000.3944.1583342700155%40Atlassian.JIRA.
Jira (PDB-4635) puppetdb_avg_mem larger than baseline values
Title: Message Title John Duarte commented on PDB-4635 Re: puppetdb_avg_mem larger than baseline values For the performance comparison run of week 2020-03-02, this tolerance failed when testing recent PE master build (2019.5.0-rc0-399-g3d3203b) to the LTS baseline (but not STS). 2019.5.0-rc0-399-g3d3203b 2018.1.12 comparison: Result 'process_puppetdb_avg_mem' is outside tolerances: baseline: 715959; result: 889080; variance: 24.18% Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.343321.1579814655000.3898.1583340720029%40Atlassian.JIRA.
Jira (PUP-9074) Windows scheduled_task name cannot use a path
Title: Message Title Josh Cooper commented on PUP-9074 Re: Windows scheduled_task name cannot use a path The scheduled task provider in puppet only supports the v1 scheduled task API. In order to manage tasks containing a folder name, you must install the puppetlabs-scheduled_task module from the forge and specify a compatibility level that supports folder names. Marking this as closed. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.271714.1534514997000.3852.1583336580028%40Atlassian.JIRA.
Jira (PUP-9074) Windows scheduled_task name cannot use a path
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9074 Windows scheduled_task name cannot use a path Change By: Josh Cooper Summary: Windows scheduled_task name cannot us use a path Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.271714.1534514997000.3851.1583336460026%40Atlassian.JIRA.
Jira (PUP-9074) Windows scheduled_task name cannot us a path
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9074
Windows scheduled_task name cannot us a path
Change By:
Josh Cooper
*Puppet Version: 4.10.4* *Puppet Server Version: 5.3.4* *OS Name/Version: Windows 2016 10.0.14393*When trying to execute the follow resource on a Windows 2016 server an error is returned: {code:puppet} scheduled_task { '\Puppet\PuppetKickoff': ensure => present, enabled => true, command => 'powershell.exe', arguments => ' E:\\Program Files\\PuppetLabs\\bin\\run_puppet_shell.bat -Verb runas', trigger => { schedule => daily, every => 1, # Specifies every other day. Defaults to 1 (every day). start_time => '08:${puppet_agent::params::cronminute}', # Must be specified minutes_interval => '60', # Repeat this task every 60 minutes minutes_duration => '300', # The task will run for a total of five hours } {code} Error: {noformat} Error: Failed to call #::NewWorkItem with HRESULT: -2147024893.: The system cannot find the path specified.Error: /Stage[main]/Puppet_agent::Init_windows/Scheduled_task[\Puppet\PuppetKickoff]/ensure: change from absent to present failed: Failed to call #::NewWorkItem with HRESULT: -2147024893.: The system cannot find the path specified. {noformat} When I only use PuppetKickoff in the name, it sucessfully creates a scheduled task but not in the path I desire.*Desired Behavior:*Allow a path structure in the scheduled_task name in order to place a task away from the main path*Actual Behavior:*See above
Add Comment
Jira (PUP-9074) Windows scheduled_task name cannot us a path
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9074
Windows scheduled_task name cannot us a path
Change By:
Josh Cooper
*Puppet Version: 4.10.4* *Puppet Server Version: 5.3.4* *OS Name/Version: Windows 2016 10.0.14393*When trying to execute the follow resource on a Windows 2016 server an error is returned:{code:puppet}scheduled_task { '\Puppet\PuppetKickoff': ensure => present, enabled => true, command => 'powershell.exe', arguments => ' E:\\Program Files\\PuppetLabs\\bin\\run_puppet_shell.bat -Verb runas', trigger => { schedule => daily, every => 1, # Specifies every other day. Defaults to 1 (every day). start_time => '08:${puppet_agent::params::cronminute}', # Must be specified minutes_interval => '60', # Repeat this task every 60 minutes minutes_duration => '300', # The task will run for a total of five hours } } {code}Error:{noformat}Error: Failed to call #::NewWorkItem with HRESULT: -2147024893.: The system cannot find the path specified.Error: /Stage[main]/Puppet_agent::Init_windows/Scheduled_task[\Puppet\PuppetKickoff]/ensure: change from absent to present failed: Failed to call #::NewWorkItem with HRESULT: -2147024893.: The system cannot find the path specified.{noformat}When I only use PuppetKickoff in the name, it sucessfully creates a scheduled task but not in the path I desire.*Desired Behavior:*Allow a path structure in the scheduled_task name in order to place a task away from the main path*Actual Behavior:*See above
Add Comment
