Jira (PUP-9119) Update pup acceptance tests to use the CA CLI to generate certs
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-9119 Update pup acceptance tests to use the CA CLI to generate certs Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9119) Update pup acceptance tests to use the CA CLI to generate certs
Title: Message Title Eric Thompson moved an issue Puppet / PUP-9119 Update pup acceptance tests to use the CA CLI to generate certs Change By: Eric Thompson Key: SERVER PUP - 2306 9119 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9119) Update pup acceptance tests to use the CA CLI to generate certs
Title: Message Title Eric Thompson updated an issue Puppet / PUP-9119 Update pup acceptance tests to use the CA CLI to generate certs Change By: Eric Thompson Acceptance Criteria: * all beaker tests in puppet , puppetserver, pe-pse, and pe-integration use `ca generate create ` to set up their CAs generate certs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7601) Remove built-in LDAP Node Terminus
Title: Message Title Kris Bosland updated an issue Puppet / PUP-7601 Remove built-in LDAP Node Terminus Change By: Kris Bosland Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title Michael Smith commented on PUP-9112 Re: :undef still shows up in types and providers Failing PEZ. I have a fix for PE up to make it handle nil. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-804) Bolt unable to connect to customer windows 2012 server over winrm
Title: Message Title Ethan Brown commented on BOLT-804 Re: Bolt unable to connect to customer windows 2012 server over winrm I would take a look at the diagnostic logs, which can be turned on following the directions at https://blogs.msdn.microsoft.com/wmi/2010/03/16/collecting-winrm-traces/ There's a good chance you'll get some useful info there. There's an article about using PowerShell to collect them at https://blogs.technet.microsoft.com/heyscriptingguy/2015/10/05/troubleshoot-winrm-with-powershellpart-1/ Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1651) log-slow-statements seems not to work
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-1651 log-slow-statements seems not to work Change By: Rob Browning Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4071) Test merge master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4071 Test merge master Issue Type: Bug Assignee: Unassigned Created: 2018/09/07 4:01 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs.
Jira (PDB-3935) Determine retirements, if any, for pdb 6
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3935 Determine retirements, if any, for pdb 6 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9116) Remove CA related deprecation warnings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9116 Remove CA related deprecation warnings Change By: Josh Cooper Summary: Deprecation warnings for Remove CA related settings are too verbose deprecation warnings Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6507) Puppet help: Hide bad subcommands, and sort remainder by usefulness
Title: Message Title Josh Cooper commented on PUP-6507 Re: Puppet help: Hide bad subcommands, and sort remainder by usefulness For Puppet 6, I think we need to: 1. Hide man and cert from puppet help output. 2. The face based cert apps, eg ca, will be deleted in 6 and the help will automatically be removed 3. Since we didn't complete the work for strings, let's just keep describe and doc for now. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6507) Puppet help: Hide bad subcommands, and sort remainder by usefulness
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-6507
Puppet help: Hide bad subcommands, and sort remainder by usefulness
Change By:
Josh Cooper
The CLI leads meeting recently discussed the current slate of built-in Puppet subcommands (all thirty of them), and came to the conclusion that some of them are useless and/or harmful.Deprecating and removing subcommands is a larger task, and improving the interfaces of useful-but-problematic ones is an even bigger one. But we identified two things we can do today to vastly improve the user experience. Namely: * {{puppet help}}'s list of subcommands should omit the useless or confusing ones completely. This won't break the workflow of anyone who's actually using them, but will keep new users from hitting their heads on exposed nails or stepping into the insulation. * The list of remaining subcommands should be sorted into categories according to their usefulness, so users who haven't memorized everything can more easily stay on the rails.h2. The useless commandsThe CLI leads team has broadly agreed that the following subcommands aren't good news. This list mostly focuses on the "indirector faces," but also includes some other stuff. * puppet file * puppet report * puppet resource_type * puppet status * puppet inspect * puppet plugin * puppet doc * puppet catalog * puppet ca * puppet certificate_request * puppet certificate_revocation_list * puppet keyh2. Categories of remaining commandsh3. Useful on a daily basis for most users * puppet agent * puppet apply * puppet cert * puppet resource * puppet moduleh3. Occasionally useful, or frequently useful for a smaller subset of users * puppet config * puppet describe * puppet device * puppet epp * puppet facts * puppet filebucket * puppet help * puppet lookup * puppet man * puppet node * puppet parserh3. Rarely useful * puppet certificate * puppet masterh3. Plugin-provided(We should have a section for PE-only or third-party subcommands.)Updated**Here is a list of subcommands in puppet#master:||Useful Subcommands||Status|||apply|keep||agent|keep||config|keep||help|keep||lookup|keep||module|keep||resource|keep|||Less Used||Status||What For?|||catalog|keep|download catalog||device|keep|run puppet on devices||epp|keep|interact with puppet's templating parser/render||facts|keep|generate puppet facts||filebucket|keep|interact with filebucket||generate|keep|environment isolation||parser|keep|validate catalogs||script|keep|runs puppet code without a catalog|||Could Be Useful With Work||Status||What For?|||node|???|retrieve node classification||plugin|???|force pluginsync||report|???|upload report||status|???|check server status|||Needs Work/Replacing||Status||What For?|||ca|delete|replace with {{`puppetserver ca`}}||cert| delete hide |split into puppetserver ca and agent cli||certificate|delete| ||certificate_request|delete| ||certificate_request_list|delete| ||key|delete| |||Documentation Related||Status||What For?|||describe|keep|list and describe types & providers||doc|keep|generate
Jira (PDB-4070) Test merge 5.2.x
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4070 Test merge 5.2.x Issue Type: Bug Assignee: Unassigned Created: 2018/09/07 3:26 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs.
Jira (BOLT-829) modulepath argument does not handle paths with spaces
Title: Message Title Michael Smith commented on BOLT-829 Re: modulepath argument does not handle paths with spaces This looks like invoking a task where the absolute path to the task contains a space is a problem. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4013) Find bash via /usr/bin/env in ext/cli/foreground, etc.
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4013 Find bash via /usr/bin/env in ext/cli/foreground, etc. Change By: Rob Browning Fix Version/s: PDB 6.0.0 Fix Version/s: PDB 6.y Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3888) (SPIKE) Investigate running PuppetDB under Java 10
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3888 (SPIKE) Investigate running PuppetDB under Java 10 Change By: Rob Browning Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3857) Fix fact path GC incompatibility with Postgres 10
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3857 Fix fact path GC incompatibility with Postgres 10 Change By: Rob Browning Fix Version/s: PDB 6.0.0 Fix Version/s: PDB 6.0.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3924) Avoid temp file flood during fact path gc
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3924 Avoid temp file flood during fact path gc Change By: Rob Browning Fix Version/s: PDB 6.0.0 Fix Version/s: PDB 6.0.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3914) Add travis tests for postgresql 10
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3914 Add travis tests for postgresql 10 Change By: Rob Browning Fix Version/s: PDB 6.0.0 Fix Version/s: PDB 6.0.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3923) Avoid set-returning functions in case in delete-unused-fact-paths
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3923 Avoid set-returning functions in case in delete-unused-fact-paths Change By: Rob Browning Fix Version/s: PDB 6.0.0 Fix Version/s: PDB 6.0.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9117) Fix should_run_command_as_user test for Arista
Title: Message Title Sean McDonald commented on PUP-9117 Re: Fix should_run_command_as_user test for Arista Failing acceptance run: https://jenkins-platform.delivery.puppetlabs.net/view/puppet-agent/view/Acceptance%20Suites/view/5.5.x/view/Suite/job/platform_puppet-agent_puppet-agent-integration-suite_daily-5.5.x/196/RMM_COMPONENT_TO_TEST_NAME=puppet,SLAVE_LABEL=beaker,TEST_TARGET=arista4-32a/consoleFull Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9118) Add a configurable option to Puppet::Resource#to_data_hash to user ToStringifiedConverter
Title: Message Title Austin Blatt created an issue Puppet / PUP-9118 Add a configurable option to Puppet::Resource#to_data_hash to user ToStringifiedConverter Issue Type: Improvement Assignee: Henrik Lindberg Created: 2018/09/07 3:01 PM Priority: Normal Reporter: Austin Blatt Currently, resource's are always serialized with ToDataConverter. For PuppetDB to store the stringified version of rich data, we need to be able to configure to_data_hash to return a hash that's the result of ToStringifiedConverter instead of ToDataConverter Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-804) Bolt unable to connect to customer windows 2012 server over winrm
Title: Message Title
Michael Smith commented on BOLT-804
Re: Bolt unable to connect to customer windows 2012 server over winrm
Configuring a server as detailed above
$cert = New-SelfSignedCertificate -CertstoreLocation Cert:\LocalMachine\My -DnsName $env:COMPUTERNAME
New-Item -Path WSMan:\LocalHost\Listener -Transport HTTPS -Address * -CertificateThumbPrint $cert.Thumbprint –Force
New-NetFirewallRule -DisplayName "Windows Remote Management (HTTPS-In)" -Name "Windows Remote Management (HTTPS-In)" -Profile Any -LocalPort 5986 -Protocol TCP
winrm delete winrm/config/Listener?Address=*+Transport=HTTP
winrm set winrm/config/service/Auth '@{Basic="false"}'
winrm set winrm/config/service/Auth '@{CredSSP="false"}'
winrm set winrm/config/service '@{AllowUnencrypted="false"}'
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 -Name "NtlmMinClientSec" -Value "0x20080030" -PropertyType DWORD -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 -Name "NtlmMinServerSec" -Value "0x20080030" -PropertyType DWORD -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\ -Name "LmCompatibilityLevel" -Value "0x0004" -PropertyType DWORD -Force
Jira (PUP-9117) Fix should_run_command_as_user test for Arista
Title: Message Title Sean McDonald created an issue Puppet / PUP-9117 Fix should_run_command_as_user test for Arista Issue Type: Task Assignee: Unassigned Created: 2018/09/07 2:59 PM Priority: Normal Reporter: Sean McDonald We reverted the additional tests added with https://github.com/puppetlabs/puppet/commit/bb08f3fd4a77cad13360aa884878c01dc2a09491 because those tests are failing on Arista. We should figure out what the failures are about and fix them, then re-add the tests Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-5921) Deprecate source_permissions
Title: Message Title Bill Sirinek commented on PUP-5921 Re: Deprecate source_permissions The puppet-supported puppet_agent module flags this deprecation warning. The offending code is in manifests/prepare.pp on line 28. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-265) @example doesn't work with 4.x functions
Title: Message Title Henrik Lindberg commented on PDOC-265 Re: @example doesn't work with 4.x functions Have you tried placing the @example above the @param ? (not sure it helps, but just a thought). This needs to be fixed - we were looking at the output for the regsubst function in puppet, and documentation for it is not coming out right either (it has @example tags as well) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9035) Puppet should load files from pluginsync during catalog application
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9035 Puppet should load files from pluginsync during catalog application Change By: Henrik Lindberg Release Notes Summary: Part A new feature where the use of the Deferred data type in a catalog makes it possible to call functions on the agent before the catalog is applied. It is now possible to call all functions / deferred values / secrets management feature does implemented in Ruby on the agent side. (Notably, it is not need a separate release note possible to call functions written in the puppet language as they are not available on the agent) . Release Notes: Not Needed New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit
Jira (PUP-9035) Puppet should load files from pluginsync during catalog application
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9035 Puppet should load files from pluginsync during catalog application Change By: Henrik Lindberg Release Notes Summary: Part of agent functions / deferred values / secrets management feature does not need a separate release note. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4017) Use Puppet's ToStringifiedConverter to handle rich data
Title: Message Title Austin Blatt commented on PDB-4017 Re: Use Puppet's ToStringifiedConverter to handle rich data We have decided instead to use a stringifying converter to keep the data from the rich data but lose the type information. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4017) Use Puppet's ToStringifiedConverter to handle rich data
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4017 Use Puppet's ToStringifiedConverter to handle rich data Change By: Austin Blatt Summary: Accommodate Use Puppet's ToStringifiedConverter to handle rich data (initially) by ignoring 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3942) Add travis testing for JDK 10
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-3942 Add travis testing for JDK 10 Change By: Austin Blatt Summary: Add travis testing for newer jdk to see what happens... JDK 10 Fix Version/s: PDB 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9116) Deprecation warnings for CA related settings are too verbose
Title: Message Title Josh Cooper created an issue Puppet / PUP-9116 Deprecation warnings for CA related settings are too verbose Issue Type: Bug Affects Versions: PUP 5.5.6 Assignee: Unassigned Created: 2018/09/07 10:24 AM Fix Versions: PUP 5.5.7 Priority: Normal Reporter: Josh Cooper Puppet 5.5.6 will emit deprecation warnings for ca related settings even if the setting is never set on the CLI or in settings: $ bx puppet agent -t Warning: Accessing 'ca' as a setting is deprecated. (location: /Users/josh/work/puppet/lib/puppet/settings.rb:1165:in `issue_deprecation_warning') Exiting; no certificate found and waitforcert is disabled
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title
Nick Maludy commented on BOLT-459
Re: Reboot a target and wait for it to become available.
encore_rp/last_boot_time.json
{
"description": "Gets the last boot time of a Linux or Windows system",
"implementations": [
{"name": "last_boot_time.sh", "requirements": ["shell"]},
{"name": "last_boot_time.ps1", "requirements": ["powershell"]}
]
}
encore_rp/last_boot_time.ps1
# this returns a big number that is the date + time serialized with no spaces or symbols
(Get-WmiObject -ClassName Win32_OperatingSystem).LastBootUpTime
encore_rp/last_boot_time.sh
#!/bin/sh
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title Michael Smith commented on BOLT-459 Re: Reboot a target and wait for it to become available. Are the tasks something you can also share? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4069) Document that we're assuming jdk >= 8 for 6.0
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4069 Document that we're assuming jdk >= 8 for 6.0 Issue Type: Improvement Assignee: Unassigned Created: 2018/09/07 9:08 AM Fix Versions: PDB 6.0.0 Priority: Normal Reporter: 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
Jira (PDB-4068) Migrate to clojure.java-time or directly to built-in Java time
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4068 Migrate to clojure.java-time or directly to built-in Java time Issue Type: Improvement Assignee: Unassigned Created: 2018/09/07 9:06 AM Priority: Normal Reporter: Rob Browning (If it turns out our uses are simple enough, might want to just drop the extra dependency instead of migrating to the new wrapper.) From https://github.com/clj-time/clj-time#clj-time---: A date and time library for Clojure, wrapping the Joda Time library. The Joda Time website says: Note that from Java SE 8 onwards, users are asked to migrate to java.time (JSR-310) - a core part of the JDK which replaces this project. If you are using Java 8 or later, consider using the built-in Java Time instead of Joda Time – and look at clojure.java-time if you want a Clojure wrapper for that. See Converting from Joda Time to java.time for more details about the similarities and differences between the two libraries. Add Comment
Jira (PDOC-265) @example doesn't work with 4.x functions
Title: Message Title Alexander Fisher commented on PDOC-265 Re: @example doesn't work with 4.x functions Affects-version should be 2.1.0, but that wasn't available in the dropdown. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9107) Deprecate non-manifest orderings
Title: Message Title Jacob Helwig commented on PUP-9107 Re: Deprecate non-manifest orderings This was merged into 5.5.x in fdae27eccb. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-265) @example doesn't work with 4.x functions
Title: Message Title Alexander Fisher created an issue Puppet Strings / PDOC-265 @example doesn't work with 4.x functions Issue Type: Bug Affects Versions: 2.0.0 Assignee: Unassigned Created: 2018/09/07 7:22 AM Priority: Normal Reporter: Alexander Fisher The style guide shows you how you're supposed to use puppet-strings with 4.x functions. # An example 4.x function. Puppet::Functions.create_function(:example) do # @param first The first parameter. # @param second The second parameter. # @return [String] Returns a string. # @example Calling the function
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9112 :undef still shows up in types and providers Change By: Henrik Lindberg Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-9112
:undef still shows up in types and providers
Change By:
Henrik Lindberg
Release Notes Summary:
In versions before Puppet 6.0.0 values from manifests assigned to resource attributes that contained undef values nested in arrays and hashes would use the Ruby symbol :undef to represent those values. When using puppet apply types and providers would see those as :undef or as the string "undef" depending on the implementation of the type. When using a puppet master, the same values were correctly handled. In Puppet 6.0.0 Ruby {{nil}} is used consistently for this. (Top level undef values are still encoded as empty string for backwards compatibility).
Release Notes:
Deprecation
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-9115) custom facts don't get compiled
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9115 custom facts don't get compiled Change By: Kenn Hussey Affects Version/s: PUP 5.3.5 Affects Version/s: PUP 5.5.6 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9104) YAML safe_load prevents aliases
Title: Message Title Thomas Franklin commented on PUP-9104 Re: YAML safe_load prevents aliases Josh Cooper I noticed you raised a question after the PR was merged regarding why aliases were showing in the first place, does this still apply? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9084) Build CI image for Ubuntu 18.10 x86
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-9084 Build CI image for Ubuntu 18.10 x86 Change By: Sebastian Miclea Learn the process of building a VMWare image using puppet puppetlabs - labs packer and platform-ci-utils on a ubuntu 18.10 image Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9114) Puppet PAL for catalog compilation cannot use resources in subsequent evaluations.
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9114 Puppet PAL for catalog compilation cannot use resources in subsequent evaluations. Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9115) custom facts don't get compiled
Title: Message Title
Uwe Bartels created an issue
Puppet / PUP-9115
custom facts don't get compiled
Issue Type:
Bug
Affects Versions:
PUP 5.3.5
Assignee:
Unassigned
Components:
Puppet Server
Created:
2018/09/07 4:07 AM
Priority:
Normal
Reporter:
Uwe Bartels
Puppet Version: 5.5.6 Puppet Server Version: 5.3.5 OS Name/Version: Ubuntu 16.04 LTS PuppetDB Version 5.2.4 custom fact don't get compiled. root@test-puppet04:~# puppet agent -t --noop --environment f20180907_fix_deprecated_code --tags netvault Info: Using configured environment 'f20180907_fix_deprecated_code' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, 'versioncmp' parameter 'b' expects a String value, got Undef (file: /etc/puppetlabs/code/environments/f20180907_fix_deprecated_code/modules/netvault/manifests/client/install.pp, line: 50, column: 6) on node test-puppet04.example.net Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Changes: Events: Resources: Time: {{ Fact generation: 0.01}} {{ Node retrieval: 0.13}} {{ Plugin sync: 0.64}} {{ Last run: 1536316270}} {{ Total: 3.25}} Version: {{ Config: }} {{ Puppet: 5.5.6}} root@test-puppet04:~# facter --puppet --debug| netvault 2018-09-07 12:32:10.358615 INFO puppetlabs.facter - loading custom facts from /opt/puppetlabs/puppet/cache/lib/facter/netvault.rb. 2018-09-07 12:32:12.238808 DEBUG puppetlabs.facter - fact "netvault_architecture" has resolved to "64". 2018-09-07 12:32:12.248292 DEBUG puppetlabs.facter - fact "netvault_version" has resolved to "12001.04". netvault_architecture => 64 netvault_version => 12001.04 root@test-puppet04:~#
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title Henrik Lindberg commented on PUP-9112 Re: :undef still shows up in types and providers This is because we are still using a 3x API for resources in puppet and it is specified that undef must be encoded as Ruby symbol :undef inside of nested structures, and as '' for top level values. When using a master, the catalog is serialized correctly and you will see a JSON null for an undef value. In the apply case, the catalog is never serialized - it simply contains whatever is in the catalog, and thus, it is possible that :undef appears in nested structures. We have almost gotten rid of :undef everywhere - hoping we may be able to get rid of it also for this case in Puppet 6.0.0 (but time is short as code freeze is imminent). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9114) Puppet PAL for catalog compilation cannot use resources in subsequent evaluations.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9114 Puppet PAL for catalog compilation cannot use resources in subsequent evaluations. Change By: Henrik Lindberg Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9114) Puppet PAL for catalog compilation cannot use resources in subsequent evaluations.
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-9114 Puppet PAL for catalog compilation cannot use resources in subsequent evaluations. Issue Type: Bug Assignee: Henrik Lindberg Created: 2018/09/07 3:17 AM Priority: Major Reporter: Henrik Lindberg When using Puppet PAL to compile a catalog (new in Puppet 6.0.0) it is not possible to use any catalog related definitions in code evaluated after the initial evaluation. This is because the evaluate method is inherited from basic script compiler and it can only define non catalog related definitions. This is a major issue with using the new API. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9103) Build Puppet Agent for Ubuntu 16.04
Title: Message Title Mihai Buzgau commented on PUP-9103 Re: Build Puppet Agent for Ubuntu 16.04 Hey Michael Smith! I currently learning the build process for the Puppet Agent. The purpose of this ticket is to manually build the Puppet Agent using a process that we know works. By doing this I hope to understand the build process (Vanagon, Image provisioning, Puppet-Runtime build process, PA build process, etc.) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9028) Create a `puppet ssl` subcommand that can perform SSL client actions on the agent
Title: Message Title Josh Cooper commented on PUP-9028 Re: Create a `puppet ssl` subcommand that can perform SSL client actions on the agent Adding these as nice to haves as some point: printing client cert and CA information (expiration, fingerprint, extensions) refresh/download CA and CRL bundles. There should be an option to insecurely refresh the CA bundle if the current ca has expired (like the certregen module). removing client's private key, public key, CSR, and cert (some of which may not exist or may be inconsistent with each other). This task will allow a client to be rekeyed (such as if its cert was accidentally revoked). nuking the client's ssl directory to "start over". For example, see https://docs.puppet.com/puppet/4.4/ssl_regenerate_certificates.html#step-3-clear-and-regenerate-certs-for-puppet-agents Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-9028) Create a `puppet ssl` subcommand that can perform SSL client actions on the agent
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9028
Create a `puppet ssl` subcommand that can perform SSL client actions on the agent
Change By:
Josh Cooper
As a complement to the new {{puppetserver ca}} CLI, we need a new puppet subcommand for performing SSL client tasks on the agent.These tasks include: * submitting a CSR to the CA * retrieving a certificate from a CA * verifying a local certificate against the CA * printing client cert and CA information (expiration, fingerprint, extensions) * refresh/download CA and CRL bundles. There should be an option to insecurely refresh the CA bundle if the current ca has expired (like the certregen module). * removing client's private key, public key, CSR, and cert (some of which may not exist or may be inconsistent with each other). This task will allow a client to be rekeyed (such as if its cert was accidentally revoked). * nuking the client's ssl directory to "start over". For example, see https://docs.puppet.com/puppet/4.4/ssl_regenerate_certificates.html#step-3-clear-and-regenerate-certs-for-puppet-agents
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
