Jira (PUP-10014) Unvendor deep_merge
Title: Message Title Josh Cooper commented on PUP-10014 Re: Unvendor deep_merge For this particular ticket, it turns out we're already including deep_merge in all the places. So it may be as simple as removing the vendored code from puppet, the deep_merge load hook, and updating puppet's gem dependencies. 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.324072.156805500.2075.1571181900249%40Atlassian.JIRA.
Jira (PDB-4550) Restore post-migration "vacuum analyze" machinery
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4550 Restore post-migration "vacuum analyze" machinery Change By: Rob Browning It looks like this was lost some good while back. See the PR commit for further 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.329601.1571174302000.1761.1571174820319%40Atlassian.JIRA.
Jira (PDB-4550) Restore post-migration "vacuum analyze" machinery
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4550 Restore post-migration "vacuum analyze" machinery Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.329601.1571174302000.1738.1571174340509%40Atlassian.JIRA.
Jira (PDB-4550) Restore post-migration "vacuum analyze" machinery
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4550 Restore post-migration "vacuum analyze" machinery Issue Type: Improvement Assignee: Unassigned Created: 2019/10/15 2:18 PM Priority: Normal Reporter: Rob Browning It looks like this was lost some good while back. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10014) Unvendor deep_merge
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10014
Unvendor deep_merge
Change By:
Josh Cooper
Puppet vendors the deep_merge gem version 1.0.1. Puppet also implements deep_merge logic ([https://github.com/puppetlabs/puppet/blob/34b208f04f7415f9a99bf6eafd6d101b303b920d/lib/puppet/vendor/load_deep_merge.rb#L1]). And there are other places where we should deeply merging objects.This ticket is to update calls sites to use the deep_merge gem, and unvendor the gem. It will need to be added as a runtime dependency to .gemspec and ext/project_data.yaml. To avoid breaking CI, we need to work backwards from the consumers of the puppet gem to puppet itself: 1. add deep_merge gem to artifactory with kermintor in release-new-new 2. add deep_merge gem component to puppet-runtime - at this point you need to know if it's client-side only, or both client and server, and whether the gem is pure ruby or contains native extensions:if you're adding a pure-ruby gem that must be available everywhere see ([https://github.com/puppetlabs/puppet-runtime/blob/6d8fb954c44f3d6c79c3756b2372b0dcc2136aca/configs/components/rubygem-semantic_puppet.rb#L17]). This prefers {{settings[:puppet_gem_vendor_dir]}} if set ( , for example {{/opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems}} ) , otherwise falls back to {{settings[:gem_home]}} ( , for example {{/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/}} ) .If you're adding client-side gem (eg for a provider) or a gem with native extensions, see https://github.com/puppetlabs/puppet-runtime/blob/master/configs/components/rubygem-CFPropertyList.rb 3. add component to the different projects in puppet-runtime repo, see https://github.com/puppetlabs/puppet-runtime/blob/master/configs/projects/_shared-agent-components.rb, https://github.com/puppetlabs/puppet-runtime/blob/master/configs/projects/bolt-runtime.rb, https://github.com/puppetlabs/puppet-runtime/blob/master/configs/projects/pdk-runtime.rb, etc 4. dockerfile in puppet-agent installs the gem when building the puppet-agent docker image (https://github.com/puppetlabs/puppet-agent/blob/master/docker/puppet-agent-alpine/windows-build/Dockerfile.build#L41) 5. add your gem to test to make sure it gets installed correctly: [https://github.com/puppetlabs/puppet-agent/blob/master/acceptance/tests/validate_vendored_ruby.rb#L154] 6. If the gem isn't client-only, add it to: jruby: [https://github.com/puppetlabs/puppetserver/blob/e87fbaf09112aa7ffa9f31c192d879d12c9562ff/resources/ext/build-scripts/jruby-gem-list.txt]7. Once it has been added everywhere it needs to be, actually remove vendored code from Puppet
Jira (PUP-10014) Unvendor deep_merge
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10014
Unvendor deep_merge
Change By:
Josh Cooper
Puppet vendors the deep_merge gem version 1.0.1. Puppet also implements deep_merge logic ([https://github.com/puppetlabs/puppet/blob/34b208f04f7415f9a99bf6eafd6d101b303b920d/lib/puppet/vendor/load_deep_merge.rb#L1]). And there are other places where we should deeply merging objects.This ticket is to update calls sites to use the deep_merge gem, and unvendor the gem. It will need to be added as a runtime dependency to .gemspec and ext/project_data.yaml. Also add To avoid breaking CI, we need to work backwards from the consumers of the puppet -runtime as a shared gem (so it's useable by to puppet -agent and puppetserver). itself: Need to work backwards - 1. add deep_merge gem to artifactory with kermintor in release-new-new 2. add deep_merge gem component to puppet-runtime - at this point you need to know if it's client-side only , or both client and server -side , and whether the gem is pure ruby or both contains native extensions: if you're using something adding a pure-ruby gem that might must be used on the server, available everywhere see ([https://github.com/puppetlabs/puppet-runtime/blob/6d8fb954c44f3d6c79c3756b2372b0dcc2136aca/configs/components/rubygem-semantic_puppet.rb#L17]) - this . This prefers the {{settings[:puppet_gem_vendor_dir]}} if set (for example {{/opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems}}) , otherwise falls back to {{settings[:gem_home]}} (for example {{/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/gems/}}). if only If you're adding client - side gem (eg for a provider) or a gem with native extensions , refer to something such as see https://github.com/puppetlabs/puppet-runtime/blob/master/configs/components/rubygem- httpclient CFPropertyList .rb 3. add component to the different projects in puppet-runtime repo (semantic , see https://github.com/puppetlabs/puppet - runtime/blob/master/configs/projects/_shared-agent-components.rb, https://github.com/puppetlabs/ puppet is a good example) -runtime/blob/master/configs/projects/bolt-runtime.rb, https://github.com/puppetlabs/puppet-runtime/blob/master/configs/projects/pdk-runtime.rb, etc 4. dockerfile in puppet-agent installs the gem when building the puppet-agent docker image (https://github.com/puppetlabs/puppet-agent/blob/master/docker/puppet-agent-alpine/windows-build/Dockerfile.build#L41) 5. add your gem to test to make sure it gets installed correctly: [https://github.com/puppetlabs/puppet-agent/blob/master/acceptance/tests/validate_vendored_ruby.rb#L154] 6. setting in puppet-runtime for destination directories that controls which directory it gets installed into. ([https://github.com/puppetlabs/puppet-runtime/blob/d5d4ee5835251beef3decfbf4ace790d3da139f0/configs/projects/agent-runtime-6.4.x.rb#L18]) where we want gems to go if shared with server: /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems _*Caveat: can If the gem isn 't contain native code*_7. if
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Molly Waggett commented on PUP-10085 Re: Prepare release announcement (Puppet Platform 6.10.1) thank you! all sent! 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.328054.1570145509000.1720.1571173620143%40Atlassian.JIRA.
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha commented on PUP-10085 Re: Prepare release announcement (Puppet Platform 6.10.1) Email subject: Puppet Platform 5.5.17, 6.4.4, and 6.10.1 are now available! The latest point releases in the Puppet 5.5, 6.4 and 6.10 series - Puppet 5.5.17, 6.4.4 and 6.10.1 are now available! 5.5.17 The release contains bug fixes and minor improvements, including: The exec type’s onlyif and unless checks now return redacted output if it is marked sensitive. You can now specify no_proxy as a Puppet setting, consistent with other http_proxy_* Puppet settings. Installation time on larger modules has been improved. Puppet can now set Windows service startup type to Auto-Start (Delayed). This version includes security updates to Ruby 2.4.9, OpenSSL 1.0.2t, and curl 7.66.0. For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/5.5/release_notes.html 6.4.4 The release contains bug fixes and minor improvements, including: New no_proxy setting available in the puppet.conf file. serverip6 fact added. puppet plugin information is now included in help. Module installation performance with minitar improved. Automatic (delayed start) is now an option for Windows services. Agents now connect directly if target host is set to NO_PROXY. Query parameters for HTTP and HTTPS file resources are preserved. This version includes security updates to Ruby 2.5.7, OpenSSL 1.1.1d, and curl 7.66.0. For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/6.4/release_notes_puppet.html 6.10.1 The release contains bug fixes and minor improvements, including: Module installation performance with minitar improved. Automatic (delayed start) is now an option for Windows services. Module repository credentials redacted during installation. Sensitive values redacted in notify resource messages. This version include security updates to Ruby 2.5.7, OpenSSL 1.1.1d, and curl 7.66.0. For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha commented on PUP-10085 Re: Prepare release announcement (Puppet Platform 6.10.1) Jean Bond Molly Waggett added a consolidated version here 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.328054.1570145509000.1563.1571171280234%40Atlassian.JIRA.
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Jean Bond commented on PUP-10085 Re: Prepare release announcement (Puppet Platform 6.10.1) lgtm; I condensed the security updates into one bullet point and added periods to the ends of sentences. 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.328054.1570145509000.1537.1571170260202%40Atlassian.JIRA.
Jira (PUP-10064) Prepare release announcement (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha commented on PUP-10064 Re: Prepare release announcement (Puppet Platform 5.5.17) thanks Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327718.1570050334000.1528.1571170080113%40Atlassian.JIRA.
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha commented on PUP-10085 Re: Prepare release announcement (Puppet Platform 6.10.1) The next point release in the Puppet 6 series, Puppet 6.10.1 is now available! The release contains bug fixes and minor improvements, including: Module installation performance with minitar improved Automatic (delayed start) is now an option for Windows services Module repository credentials redacted during installation Sensitive values redacted in notify resource messages This version upgrades the Ruby version to 2.5.7 This version upgrades OpenSSL to 1.1.1d This version includes a security update to curl 7.66.0 For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html cc/Jean Bond to review, once Jean is good, Molly Waggett we should be good to send it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-10074) Prepare release announcement (Puppet Platform 6.4.4)
Title: Message Title Jean Bond commented on PUP-10074 Re: Prepare release announcement (Puppet Platform 6.4.4) lgtm; I condensed all the security updates into one bullet point 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.327758.1570050677000.1517.1571169840112%40Atlassian.JIRA.
Jira (PUP-10064) Prepare release announcement (Puppet Platform 5.5.17)
Title: Message Title Jean Bond commented on PUP-10064 Re: Prepare release announcement (Puppet Platform 5.5.17) lgtm; I did condense all the security updates into one bullet 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.327718.1570050334000.1514.1571169780116%40Atlassian.JIRA.
Jira (PUP-10074) Prepare release announcement (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha commented on PUP-10074 Re: Prepare release announcement (Puppet Platform 6.4.4) The next point release in the Puppet 6.4 series, Puppet 6.4.4 is now available! The release contains bug fixes and minor improvements, including: New no_proxy setting available in puppet.conf serverip6 fact added puppet plugin information is now included in help Module installation performance with minitar improved Automatic (delayed start) is now an option for Windows services Agents now connect directly if target host is set to NO_PROXY Query parameters for HTTP and HTTPS file resources are preserved This version upgrades the Ruby version to 2.5.7 This version upgrades OpenSSL to 1.1.1d This version includes a security update to curl 7.66.0 For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/6.4/release_notes_puppet.html cc/Jean Bond to review, once Jean is good, Molly Waggett we should be good to send it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10064) Prepare release announcement (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha commented on PUP-10064 Re: Prepare release announcement (Puppet Platform 5.5.17) The next point release in the Puppet 5.5 series, Puppet 5.5.17 is now available! The release contains bug fixes and minor improvements, including: The exec type’s onlyif and unless checks now return redacted output if it is marked sensitive You can now specify no_proxy as a Puppet setting, consistent with other http_proxy_* Puppet settings. Installation time on larger modules has been improved. Puppet can now set Windows service startup type to Auto-Start (Delayed). This version upgrades the Ruby version to 2.5.7 This version upgrades OpenSSL to 1.0.2t This version includes a security update to curl 7.66.0 For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/5.5/release_notes.html cc/Jean Bond to review, once Jean is good, @molly we should be good to send it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha assigned an issue to Nirupama Mantha Puppet / PUP-10085 Prepare release announcement (Puppet Platform 6.10.1) Change By: Nirupama Mantha Assignee: Bill Tang Nirupama Mantha 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.328054.1570145509000.1466.1571168160218%40Atlassian.JIRA.
Jira (PUP-10074) Prepare release announcement (Puppet Platform 6.4.4)
Title: Message Title Nirupama Mantha assigned an issue to Nirupama Mantha Puppet / PUP-10074 Prepare release announcement (Puppet Platform 6.4.4) Change By: Nirupama Mantha Assignee: Bill Tang Nirupama Mantha 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.327758.1570050677000.1462.1571168040213%40Atlassian.JIRA.
Jira (PUP-10064) Prepare release announcement (Puppet Platform 5.5.17)
Title: Message Title Nirupama Mantha assigned an issue to Nirupama Mantha Puppet / PUP-10064 Prepare release announcement (Puppet Platform 5.5.17) Change By: Nirupama Mantha Assignee: Bill Tang Nirupama Mantha 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.327718.1570050334000.1434.1571167080101%40Atlassian.JIRA.
Jira (PUP-10014) Unvendor deep_merge
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10014 Unvendor deep_merge Change By: Jorie Tappa 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.324072.156805500.1407.1571166240207%40Atlassian.JIRA.
Jira (PUP-10014) Unvendor deep_merge
Title: Message Title
Jorie Tappa updated an issue
Puppet / PUP-10014
Unvendor deep_merge
Change By:
Jorie Tappa
Puppet vendors the deep_merge gem version 1.0.1. Puppet also implements deep_merge logic ( [ https://github.com/puppetlabs/puppet/blob/34b208f04f7415f9a99bf6eafd6d101b303b920d/lib/puppet/vendor/load_deep_merge.rb#L1 ] ). And there are other places where we should deeply merging objects.This ticket is to update calls sites to use the deep_merge gem, and unvendor the gem. It will need to be added as a runtime dependency to .gemspec and ext/project_data.yaml. Also add to puppet-runtime as a shared gem (so it's useable by puppet-agent and puppetserver). Need to work backwards - 1. add deep_merge gem to artifactory with kermintor in release-new-new 2. add deep_merge gem component to puppet-runtime - at this point you need to know if it's client-side, server-side, or bothif you're using something that might be used on the server, see ([https://github.com/puppetlabs/puppet-runtime/blob/6d8fb954c44f3d6c79c3756b2372b0dcc2136aca/configs/components/rubygem-semantic_puppet.rb#L17]) - this prefers the {{settings[:puppet_gem_vendor_dir]}} if set, otherwise falls back to {{settings[:gem_home]}}if only client side, refer to something such as https://github.com/puppetlabs/puppet-runtime/blob/master/configs/components/rubygem-httpclient.rb 3. add component to the different projects in puppet-runtime repo (semantic-puppet is a good example) 4. dockerfile in puppet-agent installs the gem when building the puppet-agent docker image (https://github.com/puppetlabs/puppet-agent/blob/master/docker/puppet-agent-alpine/windows-build/Dockerfile.build#L41) 5. add your gem to test to make sure it gets installed correctly: [https://github.com/puppetlabs/puppet-agent/blob/master/acceptance/tests/validate_vendored_ruby.rb#L154] 6. setting in puppet-runtime for destination directories that controls which directory it gets installed into. ([https://github.com/puppetlabs/puppet-runtime/blob/d5d4ee5835251beef3decfbf4ace790d3da139f0/configs/projects/agent-runtime-6.4.x.rb#L18]) where we want gems to go if shared with server: /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems _*Caveat: can't contain native code*_7. if the compiler or hiera code depends on it, it needs to be added for jruby: [https://github.com/puppetlabs/puppetserver/blob/e87fbaf09112aa7ffa9f31c192d879d12c9562ff/resources/ext/build-scripts/jruby-gem-list.txt] discover there's already a gem there and cryOnce it has been added everywhere it needs to be, actually remove vendored code from Puppet
Jira (PUP-9937) Docker Image - wrong version
Title: Message Title Morgan Rhodes commented on PUP-9937 Re: Docker Image - wrong version Hey Dennis, apologies in the delay getting back to this, it's been a busy couple of weeks. I just wanted to let you know I have an RFC up with my proposed updates to this process here. I'll also be sending this out to the puppet-users and puppet-dev mailing list and will hopefully be able to move forward with updates soon. 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.319591.1565013862000.1319.1571164860371%40Atlassian.JIRA.
Jira (PUP-10077) Send release announcement (Puppet Platform 6.4.4)
Title: Message Title Molly Waggett updated an issue Puppet / PUP-10077 Send release announcement (Puppet Platform 6.4.4) Change By: Molly Waggett Sprint: Release Engineering 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.327764.1570050724000.1168.1571163240194%40Atlassian.JIRA.
Jira (PUP-10088) Send release announcement (Puppet Platform 6.10.1)
Title: Message Title Molly Waggett updated an issue Puppet / PUP-10088 Send release announcement (Puppet Platform 6.10.1) Change By: Molly Waggett Sprint: Release Engineering 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.328060.157014000.1170.1571163240201%40Atlassian.JIRA.
Jira (PUP-10067) Send release announcement (Puppet Platform 5.5.17)
Title: Message Title Molly Waggett updated an issue Puppet / PUP-10067 Send release announcement (Puppet Platform 5.5.17) Change By: Molly Waggett Sprint: Release Engineering 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.327724.1570050379000.1166.1571163180110%40Atlassian.JIRA.
Jira (PUP-10100) Exec resource should not leak sensitive commands when a relative path is given
Title: Message Title Adam Winberg commented on PUP-10100 Re: Exec resource should not leak sensitive commands when a relative path is given Is it ok for the error message to specify only the executable in the error message? Yes, that would be fine for me. 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.329033.1570812974000.1148.1571162880084%40Atlassian.JIRA.
Jira (PDB-4513) puppetserver fails to connect to puppetdb 6.6.0
Title: Message Title Austin Blatt commented on PDB-4513 Re: puppetserver fails to connect to puppetdb 6.6.0 PuppetDB 6.7.1 has just been released. The default list in the jetty.ini conf file shipped with the PuppetDB packages is what I listed above, excluding the first cipher, SSL_CK_DES_192_EDE3_CBC_WITH_SHA, which is an SSLv3 cipher. If you are still using SSLv3, I first ask that you consider upgrading to TLS. If you still want to continue using SSLv3 you'll need to ensure the above SSL cipher is added to the list. 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.326149.1569370509000.1097.1571161500301%40Atlassian.JIRA.
Jira (PUP-10104) puppet device fails when using csr_attributes.yaml
Title: Message Title Josh Cooper commented on PUP-10104 Re: puppet device fails when using csr_attributes.yaml $ git --no-pager grep Puppet::SSL::Oids.register_puppet_oids lib/puppet/application/agent.rb:Puppet::SSL::Oids.register_puppet_oids lib/puppet/application/ssl.rb:Puppet::SSL::Oids.register_puppet_oids lib/puppet/test/test_helper.rb: Puppet::SSL::Oids.register_puppet_oids Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10104) puppet device fails when using csr_attributes.yaml
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10104 puppet device fails when using csr_attributes.yaml Change By: Josh Cooper Labels: beginner 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.329426.1571134076000.947.1571159281103%40Atlassian.JIRA.
Jira (PUP-10104) puppet device fails when using csr_attributes.yaml
Title: Message Title Josh Cooper commented on PUP-10104 Re: puppet device fails when using csr_attributes.yaml Looks like puppet device has the same problem as puppet ssl did. Really the OID registration should occur in the SSLProvider so that individual applications don't need to. 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.329426.1571134076000.944.1571159281091%40Atlassian.JIRA.
Jira (PUP-10064) Prepare release announcement (Puppet Platform 5.5.17)
Title: Message Title Jean Bond commented on PUP-10064 Re: Prepare release announcement (Puppet Platform 5.5.17) release notes: https://puppet.com/docs/puppet/5.5/release_notes.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327718.1570050334000.938.1571159220221%40Atlassian.JIRA.
Jira (PUP-10104) puppet device fails when using csr_attributes.yaml
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10104 puppet device fails when using csr_attributes.yaml Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.329426.1571134076000.940.1571159220241%40Atlassian.JIRA.
Jira (PUP-10074) Prepare release announcement (Puppet Platform 6.4.4)
Title: Message Title Jean Bond commented on PUP-10074 Re: Prepare release announcement (Puppet Platform 6.4.4) release note link: https://puppet.com/docs/puppet/6.4/release_notes_puppet.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327758.1570050677000.929.1571159160510%40Atlassian.JIRA.
Jira (PUP-10103) Device confdir should be located at deviceconfdir, not devicedir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10103 Device confdir should be located at deviceconfdir, not devicedir Change By: Josh Cooper Team: Network Automation 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.329422.157113170.931.1571159160517%40Atlassian.JIRA.
Jira (PUP-10102) Systemd provider is not correctly selected on Alpine Linux
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10102 Systemd provider is not correctly selected on Alpine Linux Change By: Josh Cooper Team: Night's Watch 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.329403.1571128033000.926.1571159102078%40Atlassian.JIRA.
Jira (PUP-10102) Systemd provider is not correctly selected on Alpine Linux
Title: Message Title Josh Cooper commented on PUP-10102 Re: Systemd provider is not correctly selected on Alpine Linux Did this used to work and was broken by one of those changes? 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.329403.1571128033000.924.1571159102033%40Atlassian.JIRA.
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Jean Bond commented on PUP-10085 Re: Prepare release announcement (Puppet Platform 6.10.1) release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328054.1570145509000.907.1571159040179%40Atlassian.JIRA.
Jira (PUP-10087) Publish documentation and updates and release notes (Puppet Platform 6.10.1)
Title: Message Title Jean Bond updated an issue Puppet / PUP-10087 Publish documentation and updates and release notes (Puppet Platform 6.10.1) Change By: Jean Bond Comment: release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328057.157014553.899.1571158980419%40Atlassian.JIRA.
Jira (PUP-10087) Publish documentation and updates and release notes (Puppet Platform 6.10.1)
Title: Message Title Jean Bond commented on PUP-10087 Re: Publish documentation and updates and release notes (Puppet Platform 6.10.1) release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328057.157014553.897.1571158920114%40Atlassian.JIRA.
Jira (PUP-10100) Exec resource should not leak sensitive commands when a relative path is given
Title: Message Title
Josh Cooper commented on PUP-10100
Re: Exec resource should not leak sensitive commands when a relative path is given
Brian Conner, Kledson Basso, Adam Winberg since you commented on PUP-6494, what do you think about the above approach to redact sensitive commands? For example, given
exec { "echo_passphrase":
command => Sensitive("echo \"${secretpw.unwrap}\""),
}
will fail since echo is not fully qualified. Is it ok for the error message to specify only the executable in the error message? Or would you expect the entire command is redacted? Trying to balance security with user experience when debugging failed exec resources.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-6494) exec resources leak the command string when execution fails
Title: Message Title Josh Cooper commented on PUP-6494 Re: exec resources leak the command string when execution fails Bengu Karaalioglu Yener please take a look at the Deferred data type https://puppet.com/docs/puppet/latest/integrating_secrets_and_retrieving_agent-side_data.html. Puppet can retrieve the password from a secret store like Vault, so that the password is not contained in the cached catalog. 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.141117.1468340396000.870.1571158560367%40Atlassian.JIRA.
Jira (PUP-10028) yumrepo misses support for minrate
Title: Message Title Josh Cooper commented on PUP-10028 Re: yumrepo misses support for minrate I missed this earlier, but since the fix was in the module, we should move this ticket to the MODULES project and add the yumrepo_core component and fix version. 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.325379.1568897737000.847.1571158320101%40Atlassian.JIRA.
Jira (PUP-5915) exec resources fail unless cwd is readable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5915 exec resources fail unless cwd is readable Change By: Josh Cooper Release Notes Summary: Previously exec resources now only change the current working directory if the `cwd` parameter is specified. Previously if the `cwd` parameter was not specified, puppet would change its working directory to the current working directory, which was redundant and could fail if the current working directory was not accessible. 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.117135.1455734657000.840.1571158260362%40Atlassian.JIRA.
Jira (PUP-5915) exec resources fail unless cwd is readable
Title: Message Title Josh Cooper commented on PUP-5915 Re: exec resources fail unless cwd is readable Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/a63ae7bb5517ec8699d7ec5d77280961257f399d 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.117135.1455734657000.783.1571157600823%40Atlassian.JIRA.
Jira (PDB-3300) Add command for deleting node data
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3300 Add command for deleting node data Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.176102.1487778838000.732.1571156763931%40Atlassian.JIRA.
Jira (PUP-9957) puppet apply command fails when external modules are installed
Title: Message Title Vadym Chepkov commented on PUP-9957 Re: puppet apply command fails when external modules are installed I think it's related to https://tickets.puppetlabs.com/browse/PUP-9602 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.313933.1561476226000.577.1571153100135%40Atlassian.JIRA.
Jira (PUP-10095) Better error handling for reading task metadata
Title: Message Title Cas Donoghue updated an issue Puppet / PUP-10095 Better error handling for reading task metadata Change By: Cas Donoghue 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.328355.1570487848000.526.1571149620369%40Atlassian.JIRA.
Jira (PUP-10095) Better error handling for reading task metadata
Title: Message Title Cas Donoghue updated an issue Puppet / PUP-10095 Better error handling for reading task metadata Change By: Cas Donoghue Fix Version/s: PUP 6.4.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328355.1570487848000.525.1571149560064%40Atlassian.JIRA.
Jira (BOLT-858) I want to apply a manifest remotely without a plan
Title: Message Title Mihail Mihaylov commented on BOLT-858 Re: I want to apply a manifest remotely without a plan Hi Michael Smith, is this the proper place (forum) to discuss a "challenge" I have with the "apply" option? Aside note: I accidentally change the status of the Jira to "needs information". I do apologize. Please, adjust accordingly. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276848.153754705.489.1571148360672%40Atlassian.JIRA.
Jira (FACT-2075) Implement kernelmajversion fact.
Title: Message Title Gheorghe Campean created an issue Facter / FACT-2075 Implement kernelmajversion fact. Issue Type: Task Assignee: Gheorghe Campean Created: 2019/10/15 6:04 AM Priority: Normal Reporter: Gheorghe Campean 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 (FACT-2072) Update the regex to get Infiniband MAC and IP address on CentOS 7.x platform
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2072 Update the regex to get Infiniband MAC and IP address on CentOS 7.x platform Change By: Mihai Buzgau Team: Night's Watch 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.329279.1571082153000.259.1571142000766%40Atlassian.JIRA.
Jira (FACT-2065) Add support for FIPS fact on Windows
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2065 Add support for FIPS fact on Windows Change By: Mihai Buzgau Team: Night's Watch 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.328977.1570798421000.254.1571141940226%40Atlassian.JIRA.
Jira (FACT-2065) Add support for FIPS fact on Windows
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2065 Add support for FIPS fact on Windows Change By: Mihai Buzgau Sprint: PR - 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.328977.1570798421000.252.1571141940220%40Atlassian.JIRA.
Jira (PUP-6569) Improve error messaging for Windows user management
Title: Message Title
Dorin Pleava updated an issue
Puppet / PUP-6569
Improve error messaging for Windows user management
Change By:
Dorin Pleava
While investigating PUP-6483, we found that we could be more specific with our error handling when performing some user password management tasks on Windows.Per [~rob] in PUP-6483:{quote} A few error codes we could explore handling some of the errors and providing better messages around how to correct. Possibly as a separate ticket though. [ https://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.85).aspx ] {code} * ERROR_LAST_ADMIN - 1322 (0x52A) - This operation is disallowed as it could result in an administration account being disabled, deleted or unable to log on.* ERROR_WRONG_PASSWORD - 1323 (0x52B) - Unable to update the password. The value provided as the current password is incorrect.* ERROR_ILL_FORMED_PASSWORD - 1324 (0x52C) - Unable to update the password. The value provided for the new password contains values that are not allowed in passwords.* ERROR_PASSWORD_RESTRICTION - 1325 (0x52D) - Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain.* ERROR_LOGON_FAILURE - 1326 (0x52E) - The user name or password is incorrect.* ERROR_ACCOUNT_RESTRICTION - 1327 (0x52F) - Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.* ERROR_INVALID_LOGON_HOURS - 1328 (0x530) - Your account has time restrictions that keep you from signing in right now.* ERROR_INVALID_WORKSTATION - 1329 (0x531) - This user isn't allowed to sign in to this computer.* ERROR_PASSWORD_EXPIRED - 1330 (0x532) - The password for this account has expired.* ERROR_ACCOUNT_DISABLED - 1331 (0x533) - This user can't sign in because this account is currently disabled.{code} {quote} *In Scope** Modify the Puppet Windows user provider or backing libs in puppet/util/windows to detect and surface some or all of the preceding errors to the user when applicable*Notes*From - [ https://github.com/puppetlabs/puppet/pull/5201#discussion_r75033133 ] {{ERROR_ACCOUNT_LOCKED_OUT = 1909}} - is raised if account is locked out even when supplied login credentials are validWith both {{ERROR_ACCOUNT_LOCKED_OUT = 1909}} and {{ERROR_ACCOUNT_EXPIRED = 1793}}, puppet will proceed to set the password anyway after failed logon.Both of these (and probably others) are cases we could improve on... for example, puppet should not try to set passwords for expired or locked out accounts, and possibly should log a debug message that this was encountered?
Jira (PUP-10104) puppet device fails when using csr_attributes.yaml
Title: Message Title Jonas Verhofsté created an issue Puppet / PUP-10104 puppet device fails when using csr_attributes.yaml Issue Type: Bug Assignee: Unassigned Created: 2019/10/15 3:07 AM Priority: Normal Reporter: Jonas Verhofsté Whilst trying to use trusted facts for my puppet device, I noticed the `puppet device --target devicename` fail with the error "OBJ_txt2obj: first num too large". However, manually requesting the cert with `puppet ssl` does work and behaves as expected. Guessing it's related to PUP-9746, or at least a similar issue. Desired Behavior: First `puppet device` run should request a cert with correct extension requests Actual Behavior: First `puppet device` run fails with "Cannot create CSR with extension request extension_name: OBJ_txt2obj: first num too large" Add Comment
Jira (PUP-10103) Device confdir should be located at deviceconfdir, not devicedir
Title: Message Title Jonas Verhofsté created an issue Puppet / PUP-10103 Device confdir should be located at deviceconfdir, not devicedir Issue Type: Improvement Assignee: Unassigned Created: 2019/10/15 2:28 AM Priority: Minor Reporter: Jonas Verhofsté PR 7612 added ssl cert persistence by symlinking the ssldir in /etc to the one in /opt, working around the fact that the device confdir is the same as the vardir. Not sure if that was ever a workaround for another issue, but since the deviceconfdir gets created anyway, why not use it as the confdir for the device too? For example: when you want to use csr_attributes.yaml for your devices, you need to put the file in /opt/puppetlabs/puppet/cache/devices/devicename/csr_attributes.yaml. Instead of the logical /etc/puppetlabs/puppet/devices/devicename/csr_attributes.yaml. I realize the absence of the file doesn't mean the extensions themselves get lost, they're still in the cert, but it's a real inconvenience in my opinion. As far as I can tell, the fix would be fairly small (just playing around with some parameters at the previously linked lines). It maybe even could remove the need for the symlinked ssl-dir, since it will go looking in the right dir in the first place (or am I missing something obvious here)? Either way, if setting the device confdir to puppet's vardir is a conscious choice/workaround for another issue, then this can be ignored. But if it isn't, I can make always make a PR.
Jira (FACT-2074) Implement kernel fact.
Title: Message Title Gheorghe Campean created an issue Facter / FACT-2074 Implement kernel fact. Issue Type: Task Assignee: Gheorghe Campean Created: 2019/10/15 1:49 AM Priority: Normal Reporter: Gheorghe Campean 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-10102) Systemd provider is not correctly selected on Alpine Linux
Title: Message Title
Tomasz Wolbach created an issue
Puppet / PUP-10102
Systemd provider is not correctly selected on Alpine Linux
Issue Type:
Bug
Affects Versions:
PUP 6.8.1, PUP 6.9.0, PUP 6.8.0, PUP 6.10.0
Assignee:
Unassigned
Created:
2019/10/15 1:27 AM
Priority:
Normal
Reporter:
Tomasz Wolbach
Puppet Version: 6.8.0 - 6.10.0 Running unit tests (i.e pdk test unit) on Alpine Linux with puppet agents >= 6.8.0 fails:
pdk (INFO): Using Ruby 2.4.6
pdk (INFO): Using Puppet 6.8.0
Run options: exclude {:bolt=>true}
Evaluated 83 tests in 30.530483644 seconds: 1 failures, 0 pending.
failed: rspec: ./spec/classes/common_spec.rb:9: Could not find the daemon directory (tested [/etc/sv,/var/lib/service])
Jira (FACT-2073) Implement system-uptime fact
Title: Message Title Gheorghe Campean created an issue Facter / FACT-2073 Implement system-uptime fact Issue Type: Task Assignee: Gheorghe Campean Created: 2019/10/15 12:31 AM Priority: Normal Reporter: Gheorghe Campean 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
