Jira (PUP-9931) Make Context thread local
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9931 Make Context thread local Change By: Maggie Dreyer 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306716.1556578082000.84221.1567551960713%40Atlassian.JIRA.
Jira (PUP-9931) Make Context thread local
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9931 Make Context thread local Change By: Maggie Dreyer Fix Version/s: PUP 6.9.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306716.1556578082000.84219.1567551960694%40Atlassian.JIRA.
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4487 PuppetDB Terminus with Masterless Fails on SSL Errors Change By: Austin Blatt Fix Version/s: PDB 6.6.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321961.1566490124000.83833.1567543380388%40Atlassian.JIRA.
Jira (PUP-9989) Bug with attributes "purge_ssh_keys" in resource type "user"
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9989 Bug with attributes "purge_ssh_keys" in resource type "user" Change By: Jorie Tappa 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.322526.156696125.83555.1567536061548%40Atlassian.JIRA.
Jira (PUP-9992) FAIL COMMAND "PUPPET AGENT --TEST" for puppet agent versión 6 on node client Error: Could not run: 403 "Forbidden"
Title: Message Title
Josh Cooper commented on PUP-9992
Re: FAIL COMMAND "PUPPET AGENT --TEST" for puppet agent versión 6 on node client Error: Could not run: 403 "Forbidden"
The call to /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/state_machine.rb:47:in `next_state' shows that the agent is trying to download the CA certificate, but the server is returning a 403. Since the CA certificate is public, it should be downloadable by unauthenticated nodes (since they may not have a client certificate yet). Verify the command {{curl -k https://foremanpuppet6.dap.es/puppet-ca/v1/certificate/ca -H 'Accept: text/plain' }} works.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323109.1567411706000.83539.1567535940452%40Atlassian.JIRA.
Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title Jorie Tappa commented on PUP-9993 Re: lookup's knockout_prefix cannot be undef, contrary to the documentation Jean Bond we suggest perhaps updating the linked documentation in the ticket to state that the `knockout_prefix` is disabled by default, instead of stating that it's set to undef, which may suggest users need to specify it as such in their code. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.83470.1567535400874%40Atlassian.JIRA.
Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9993 lookup's knockout_prefix cannot be undef, contrary to the documentation Change By: Jorie Tappa Component/s: Docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.83475.1567535400933%40Atlassian.JIRA.
Jira (PUP-9995) Examine thread safety for additional indirector variables
Title: Message Title Tony Vu created an issue Puppet / PUP-9995 Examine thread safety for additional indirector variables Issue Type: Task Assignee: Unassigned Created: 2019/09/03 10:57 AM Priority: Normal Reporter: Tony Vu Some of the indirector's variables initialized have been made thread-safe in PUP-9933, but there are other variables/accessors that can change. This ticket is to determine if those variables should be also be made threadsafe. They include the name, model, ttl, and @@indirections. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper commented on PUP-9990 Re: no_proxy config setting is ignored by puppet agent I'm not able to reproduce. If I set the proxy host to a bogus value, then the connection will only succeed if the proxy matches the `no_proxy` list: $ bundle exec puppet config print no_proxy --section agent 10.0.0.0/8,example.com,*.example.com,local,*.local,127.0.0.1,localhost,master1,master2,g327wjgy9sjg0ut.delivery.puppetlabs.net $ bundle exec puppet agent -t --server_list g327wjgy9sjg0ut.delivery.puppetlabs.net --http_proxy_host doesntexist.example.com Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Caching catalog for XXX Info: Applying configuration version '1567531578' Notice: Applied catalog in 0.01 seconds But if I remove my server from the no_proxy setting, then the agent tries to use the proxy and fails to connect:
Jira (PUP-9990) no_proxy config setting is ignored by puppet agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9990 no_proxy config setting is ignored by puppet agent Change By: Josh Cooper 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.322755.1567086003000.83036.1567530600506%40Atlassian.JIRA.
Jira (PDB-4455) Add support for syncing catalog inputs
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4455 Add support for syncing catalog inputs 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.317965.1563991774000.82877.1567528500623%40Atlassian.JIRA.
Jira (PDB-4487) PuppetDB Terminus with Masterless Fails on SSL Errors
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4487 PuppetDB Terminus with Masterless Fails on SSL Errors Change By: Austin Blatt Assignee: Austin Blatt 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.321961.1566490124000.82861.1567527840662%40Atlassian.JIRA.
Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title Henrik Lindberg commented on PUP-9993 Re: lookup's knockout_prefix cannot be undef, contrary to the documentation Fabien Wernli what is your expectations should happen when it is specified as `undef`? I would assume it should treat it the same way as if no knockout prefix value was given at all... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.82799.1567527241814%40Atlassian.JIRA.
Jira (PUP-9994) External/Extended trusted data
Title: Message Title David Schmitt assigned an issue to David Schmitt Puppet / PUP-9994 External/Extended trusted data Change By: David Schmitt Assignee: David Schmitt 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.323248.1567522563000.82757.1567526412323%40Atlassian.JIRA.
Jira (PUP-9994) External/Extended trusted data
Title: Message Title David Schmitt created an issue Puppet / PUP-9994 External/Extended trusted data Issue Type: Improvement Assignee: Unassigned Created: 2019/09/03 7:56 AM Priority: Normal Reporter: David Schmitt To facilitate enhancing catalog compilation with dynamic trusted data from third parties (i.e. not the ENC or the agent), this change adds $trusted_ext. The data gets loaded from the indirector (currently only through calling a script that needs to return JSON). This is an experimental feature. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2009) Replacement of : with => should not be done inside fact values
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2009 Replacement of : with => should not be done inside fact values 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.323197.1567507573000.82606.1567521780244%40Atlassian.JIRA.
Jira (PUP-9074) Windows scheduled_task name cannot us a path
Title: Message Title Peter J Krawetzky commented on PUP-9074 Re: Windows scheduled_task name cannot us a path Any idea if this has been fixed? 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.271714.1534514997000.82561.1567518420074%40Atlassian.JIRA.
Jira (PUP-9992) FAIL COMMAND "PUPPET AGENT --TEST" for puppet agent versión 6 on node client Error: Could not run: 403 "Forbidden"
Title: Message Title
Francisco José Fernández Cabezón updated an issue
Puppet / PUP-9992
FAIL COMMAND "PUPPET AGENT --TEST" for puppet agent versión 6 on node client Error: Could not run: 403 "Forbidden"
Change By:
Francisco José Fernández Cabezón
*Puppet Version: 6.8.1* *Puppet Server Version:6.5.0* *OS Name/Version: Debian 9*Fail connect puppet agent 6 with puppetserver 6 *Desired Behavior:**Actual Behavior:* Debug: Applying settings catalog for sections main, agent, sslDebug: Could not find library 'selinux' required to enable feature 'selinux'Debug: Using settings: adding file resource 'confdir': 'File[/etc/puppetlabs/puppet] \ {:path=>"/etc/puppetlabs/puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'codedir': 'File[/etc/puppetlabs/code] \ {:path=>"/etc/puppetlabs/code", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Could not find library 'cfpropertylist' required to enable feature 'cfpropertylist'Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not existDebug: Puppet::Type::User::ProviderPw: file pw does not existDebug: Could not find library 'ldap' required to enable feature 'ldap'Debug: Puppet::Type::User::ProviderLdap: feature ldap is missingDebug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/uuidgen does not existDebug: /User[puppet]: Provider useradd does not support features libuser; not managing attribute forcelocalDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: Puppet::Type::Group::ProviderLdap: feature ldap is missingDebug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not existDebug: /Group[puppet]: Provider groupadd does not support features libuser; not managing attribute forcelocalDebug: Using settings: adding file resource 'vardir': 'File[/opt/puppetlabs/puppet/cache] \ {:path=>"/opt/puppetlabs/puppet/cache", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'logdir': 'File[/var/log/puppetlabs/puppet] \ {:path=>"/var/log/puppetlabs/puppet", :mode=>"750", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'statedir': 'File[/opt/puppetlabs/puppet/cache/state] \ {:path=>"/opt/puppetlabs/puppet/cache/state", :mode=>"1755", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'rundir': 'File[/var/run/puppetlabs] \ {:path=>"/var/run/puppetlabs", :mode=>"755", :owner=>"root", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'libdir': 'File[/opt/puppetlabs/puppet/cache/lib] \ {:path=>"/opt/puppetlabs/puppet/cache/lib", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'hiera_config': 'File[/etc/puppetlabs/puppet/hiera.yaml] \
Jira (FACT-1983) Detect OS (without Windows)
Title: Message Title Sebastian Miclea commented on FACT-1983 Re: Detect OS (without Windows) In this task OS fact was implemented for SLES, Debian, Ubuntu 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.319545.1564991823000.82443.1567512180113%40Atlassian.JIRA.
Jira (FACT-2010) Implement Os fact for Fedora
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2010 Implement Os fact for Fedora Issue Type: Task Assignee: Sebastian Miclea Created: 2019/09/03 5:01 AM Priority: Normal Reporter: Sebastian Miclea 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-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation
Title: Message Title
Fabien Wernli created an issue
Puppet / PUP-9993
lookup's knockout_prefix cannot be undef, contrary to the documentation
Issue Type:
Bug
Affects Versions:
PUP 6.7.0
Assignee:
Unassigned
Components:
Hiera & Lookup
Created:
2019/09/03 4:46 AM
Priority:
Normal
Reporter:
Fabien Wernli
Puppet Version: 6.7.0 Puppet Server Version: N/A OS Name/Version: Debian Buster The documentation states at various places (e.g. https://puppet.com/docs/puppet/5.2/hiera_use_function.html) that lookup's knockout_prefix parameter is either a string or undef. However, when running puppet apply on the following code, we get an error: lookup( { 'name' => 'foobar', 'value_type' => Hash, 'merge' => { 'strategy' => 'deep', 'knockout_prefix' => undef, } , 'default_value' => {}, }, ) Error: Evaluation Error: Error while evaluating a Function Call, 'lookup' expects one of: (NameType = Variant[String, Array[String]] name, ValueType = Type value_type?, MergeType = Variant[String[1], Hash[String, Scalar]] merge?) rejected: parameter 'name' expects a NameType = Variant[String, Array[String]] value, got Struct (NameType = Variant[String, Array[String]] name, Optional[ValueType] value_type, Optional[MergeType] merge, DefaultValueType = Any default_value) rejected: expects 4 arguments, got 1 (NameType = Variant[String, Array[String]] name, ValueType = Type value_type?, MergeType = Variant[String[1], Hash[String, Scalar]] merge?) rejected: parameter 'name' expects a NameType = Variant[String, Array[String]] value, got Struct (OptionsWithName = Struct[{'name' => NameType = Variant[String, Array[String]], 'value_type' => Optional[ValueType = Type], 'default_value' => DefaultValueType = Any, 'override' => Optional[Hash[String, Any]], 'default_values_hash' => Optional[Hash[String,
Jira (FACT-2009) Replacement of : with => should not be done inside fact values
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2009 Replacement of : with => should not be done inside fact values Issue Type: Bug Assignee: Unassigned Created: 2019/09/03 3:46 AM Priority: Normal Reporter: Bogdan Irimie path => "C =>\\Windows\\system32;C =>\\Windows;C =>\\Windows\\System32\\Wbem;C =>\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C =>\\Windows\\System32\\OpenSSH\\;C =>\\Packer\\SysInternals;C =>\\Program Files\\Git\\cmd;C =>\\Program Files\\PowerShell\\6\\;C =>\\Program Files\\Puppet Labs\\Puppet\\bin;C =>\\Program Files\\Puppet Labs\\Puppet\\puppet\\bin;C =>\\Users\\Administrator\\AppData\\Local\\Microsoft\\WindowsApps;", should be path => "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\Windows\\System32\\OpenSSH\\;C:\\Packer\\SysInternals;C:\\Program Files\\Git\\cmd;C:\\Program Files\\PowerShell\\6\\;C:\\Program Files\\Puppet Labs\\Puppet\\bin;C:\\Program Files\\Puppet Labs\\Puppet\\puppet\\bin;C:\\Users\\Administrator\\AppData\\Local\\Microsoft\\WindowsApps;",
