Jira (PUP-10420) Observe waitforlock when acquiring the ssl lock
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10420 Observe waitforlock when acquiring the ssl lock Change By: Josh Cooper Fix Version/s: PUP 6.16.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.355521.1586889868000.42524.1587447780033%40Atlassian.JIRA.
Jira (PUP-10420) Observe waitforlock when acquiring the ssl lock
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10420 Observe waitforlock when acquiring the ssl lock Change By: Josh Cooper Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.355521.1586889868000.42497.1587430920047%40Atlassian.JIRA.
Jira (PUP-10429) Add method for registering runtime implementations
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10429 Add method for registering runtime implementations Change By: Josh Cooper Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356111.1587406746000.42498.1587430920103%40Atlassian.JIRA.
Jira (PUP-8051) puppet agent option to wait for lock
Title: Message Title Melissa Stone commented on PUP-8051 Re: puppet agent option to wait for lock We merged this, then found some issues and had to revert the merge. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.216234.1507933383000.42495.1587429420032%40Atlassian.JIRA.
Jira (PDOC-274) Add provider attribute to docs output
Title: Message Title Jesse Scott assigned an issue to Jesse Scott Puppet Strings / PDOC-274 Add provider attribute to docs output Change By: Jesse Scott Assignee: Jesse Scott Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295581.1549669062000.42490.1587428580444%40Atlassian.JIRA.
Jira (PUP-10429) Add method for registering runtime implementations
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10429 Add method for registering runtime implementations Change By: Josh Cooper Sprint: Coremunity Grooming Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356111.1587406746000.42424.1587423540040%40Atlassian.JIRA.
Jira (PUP-10429) Add method for registering runtime implementations
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10429 Add method for registering runtime implementations Change By: Josh Cooper Epic Link: PUP-8550 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356111.1587406746000.42350.1587418680088%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Dan33l commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider I know that exists resource API. I already said to doc team and David that i need something like was done in the chapter 3 of the Book written by Nan Liu and Dan Bod. But the documentation is too short and so sibylline Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42338.1587418080363%40Atlassian.JIRA.
Jira (PUP-10429) Add method for registering runtime implementations
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10429 Add method for registering runtime implementations Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356111.1587406746000.42283.1587416340083%40Atlassian.JIRA.
Jira (PUP-10429) Add method for registering runtime implementations
Title: Message Title Josh Cooper commented on PUP-10429 Re: Add method for registering runtime implementations Earlier we discussed using `Puppet.initialize_settings` and passing in specific runtime implementations to be registered similar to what was done in https://github.com/puppetlabs/puppetserver/blob/f63607ed1dc7296654e1d962fa00626f242de113/src/ruby/puppetserver-lib/puppet/server/puppet_config.rb#L34-L38 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356111.1587406746000.42282.1587416340040%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Josh Cooper commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider Ah I didn't realize you were trying to declare a generic property and then "pass thru" values. Puppet's newproperty method isn't designed for that really. It's intended to be used a specific type of property. I'd double-recommend the resource API in that case. David Schmitt may have thoughts about this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42281.1587416280296%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Dan33l commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider When array_matching, all settings are considered as an Array. But only one setting is an Array (trusted_domains). Others are String or Hash. So it does not look possible to use array_matching . I confirmed this buy testing the suggested solution. It breaks the config.php file. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42219.1587412380055%40Atlassian.JIRA.
Jira (PUP-10429) Add method for registering runtime implementations
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10429 Add method for registering runtime implementations Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356111.1587406746000.42098.1587406800223%40Atlassian.JIRA.
Jira (PUP-10429) Add method for registering runtime implementations
Title: Message Title Josh Cooper created an issue Puppet / PUP-10429 Add method for registering runtime implementations Issue Type: Bug Assignee: Unassigned Created: 2020/04/20 11:19 AM Fix Versions: PUP 6.15.0 Priority: Normal Reporter: Josh Cooper Puppetserver needs to be able to register its http client implementation (See SERVER-2780). This ticket is to make the change in puppet so puppetserver can do that. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10429) Add method for registering runtime implementations
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10429 Add method for registering runtime implementations Change By: Josh Cooper Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356111.1587406746000.42099.1587406800267%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Josh Cooper commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider Yeah you have to pass :array_matching => :all in the options hash to the newproperty DSL method in order for it to be multi-valued. You might also want to look at the resource API https://puppet.com/docs/puppet/latest/about_the_resource_api.html Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42091.1587406500057%40Atlassian.JIRA.
Jira (PUP-9644) Improve documentation around sensitive data in puppet
Title: Message Title Rob Braden commented on PUP-9644 Re: Improve documentation around sensitive data in puppet We should probably add some clarification that the "core" types and providers make an effort to redact sensitive information, custom types and providers may need to be updated to respect the sensitive flag. For example: https://github.com/puppetlabs/puppet/blob/f482005b92807a4bdd350e86fa80f2da39c936a2/lib/puppet/util/execution.rb#L159 sets it as 'false' by default, anyone that needs to redact sensitive information from the execution API should pass the value as 'true' Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304741.1555347266000.42069.1587406020023%40Atlassian.JIRA.
Jira (PUP-10426) if certname entry is not in [main] section of puppet.conf file provide a warning
Title: Message Title Rob Braden updated an issue Puppet / PUP-10426 if certname entry is not in [main] section of puppet.conf file provide a warning Change By: Rob Braden Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.355976.1587134534000.42043.1587405480184%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Rob Braden commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider Hi Dan33l, I think in your type you have to declare that you are using an Array. Look at the members property of the Group type for an example. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42006.1587404880300%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title
Dan33l updated an issue
Puppet / PUP-10428
Puppet parser only consider first element of array for properties in custom provider
Change By:
Dan33l
*Puppet Version: Tested with 5.5.19 , 6.14.0 * *Puppet Server Version: Without server, puppet apply* *OS Name/Version: Ubuntu 1804*I am working on this custom provider : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/lib/puppet/provider/nextcloud_config/php.rb]When the Puppet manifest have an Array as with setting trusted_domains, the setter receive the first element of the Array as a String and not an Array.To reproduce you can run acceptance tests like here :[https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/acceptance/nextcloud_spec.rb]Nextcloud is a PHP app. It requires a webserver and a database server before, like with spec helper acceptance : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/spec_helper_acceptance.rb]The module take care of PHP.*Desired Behavior:*Puppet take care of Array with following output :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to [['localhost','cloud.example.com']|http://cloud.example.com/]}}{quote}*Actual Behavior:*The Nextcloud's configuration is done in a config.php file like this one (have a look to setting trusted_domains that is array :{quote}See attached file.{quote}The manifests to reproduce (apply helper before) :{quote}See attached file {quote}The output when applyed is :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to 'localhost'}}{quote} The expected output is :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to [['localhost','cloud.example.com']|http://cloud.example.com/]}}{quote} With pry :{quote}From: /etc/puppetlabs/code/modules/nextcloud/lib/puppet/provider/nextcloud_config/php.rb:78 php#value=:77: def value=(val) => 78: binding.pry 79: set_config_system(resource[:name], val) 80: end[1] pry(#)> val => "localhost" [2] pry(#)> val.class => String{quote}
Add
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Dan33l updated an issue Puppet / PUP-10428 Puppet parser only consider first element of array for properties in custom provider Change By: Dan33l Affects Version/s: PUP 6.14.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.41763.1587396780284%40Atlassian.JIRA.
Jira (FACT-2565) Debian development versions cause fatal error when resolving os.release
Title: Message Title David Schmitt updated an issue Facter / FACT-2565 Debian development versions cause fatal error when resolving os.release Change By: David Schmitt Affects Version/s: FACT 4.0.14 Affects Version/s: FACT 4.0.15 Affects Version/s: FACT 4.0.16 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356068.158739506.41727.1587395220026%40Atlassian.JIRA.
Jira (FACT-2565) Debian development versions cause fatal error when resolving os.release
Title: Message Title David Schmitt created an issue Facter / FACT-2565 Debian development versions cause fatal error when resolving os.release Issue Type: Bug Assignee: Unassigned Created: 2020/04/20 8:04 AM Environment: Debian bullseye/sid Priority: Normal Reporter: David Schmitt When running facter on Debian bullseye/sid, the code in https://github.com/puppetlabs/facter-ng/blob/b4917e6244b044bbb1cfa646f4e2fa85f3b12b4e/lib/facts/debian/os/release.rb#L16-L20 fails, because while - in contrast to FACT-2475 - determine_release_for_os does return a value, it does not match facter's expectations. To illustrate, here's the key values from the linked function: fact_value: "bullseye/sid" versions: ["bullseye/sid"] without versions[1] having a value, the gsub fails with the following exception: david@zion:~/git/puppetlabs-motd (master)$ ruby2.5 /usr/bin/bundle
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Dan33l updated an issue Puppet / PUP-10428 Puppet parser only consider first element of array for properties in custom provider Change By: Dan33l Attachment: apply_1_helper.pp Attachment: apply_2_module.pp Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.41704.1587392582085%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title
Dan33l updated an issue
Puppet / PUP-10428
Puppet parser only consider first element of array for properties in custom provider
Change By:
Dan33l
*Puppet Version: Tested with 5.5.19* *Puppet Server Version: Without server, puppet apply* *OS Name/Version: Ubuntu 1804*I am working on this custom provider : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/lib/puppet/provider/nextcloud_config/php.rb]When the Puppet manifest have an Array as with setting trusted_domains, the setter receive the first element of the Array as a String and not an Array.To reproduce you can run acceptance tests like here :[https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/acceptance/nextcloud_spec.rb]Nextcloud is a PHP app. It requires a webserver and a database server before, like with spec helper acceptance : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/spec_helper_acceptance.rb]The module take care of PHP.*Desired Behavior:*Puppet take care of Array with following output :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to [['localhost','cloud.example.com']|http://cloud.example.com/]}}{quote}*Actual Behavior:*The Nextcloud's configuration is done in a config.php file like this one (have a look to setting trusted_domains that is array :{quote}See attached file.{quote}The manifests to reproduce (apply helper before) :{quote} class See attached file { 'nextcloud' : database_name => 'nextcloud_example', database_user => 'user_example', database_password => 'secret', system_user => 'www-data', config =>Unknown macro: \{ 'trusted_domains' => [ 'localhost', 'cloud.example.com', ], }}{ quote}The output when applyed is :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to 'localhost'}}{quote} The expected output is :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to [['localhost','cloud.example.com']|http://cloud.example.com/]}}{quote} With pry :{quote}From: /etc/puppetlabs/code/modules/nextcloud/lib/puppet/provider/nextcloud_config/php.rb:78 php#value=:77: def value=(val) => 78: binding.pry 79: set_config_system(resource[:name], val) 80: end[1] pry(#)> val => "localhost" [2] pry(#)> val.class => String{quote}
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title
Dan33l updated an issue
Puppet / PUP-10428
Puppet parser only consider first element of array for properties in custom provider
Change By:
Dan33l
*Puppet Version: Tested with 5.5.19* *Puppet Server Version: Without server, puppet apply* *OS Name/Version: Ubuntu 1804*I am working on this custom provider : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/lib/puppet/provider/nextcloud_config/php.rb]When the Puppet manifest have an Array as with setting trusted_domains, the setter receive the first element of the Array as a String and not an Array.To reproduce you can run acceptance tests like here :[https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/acceptance/nextcloud_spec.rb]Nextcloud is a PHP app. It requires a webserver and a database server before, like with spec helper acceptance : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/spec_helper_acceptance.rb]The module take care of PHP.*Desired Behavior:*Puppet take care of Array with following output :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to [['localhost','cloud.example.com']|http://cloud.example.com/]}}{quote}*Actual Behavior:*The Nextcloud's configuration is done in a config.php file like this one (have a look to setting trusted_domains that is array :{quote} $CONFIG = array ( 'passwordsalt' => 'XqxWppqWQ0/zMN/ur4wHn6SFTHhYLb', 'secret' => '+XEHiU8/1tfVkFL43QRepi5ev6i+vzU5jD3ZZjDd5MKuGEB8', 'trusted_domains' => array( 0 => 'localhost', ), 'datadirectory' => '/var/nextcloud-data', 'dbtype' => 'mysql', 'version' => '18 See attached file . 0.3.0', 'overwrite.cli.url' => 'http://localhost', 'dbname' => 'nextcloud_example', 'dbhost' => '127.0.0.1', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'user_example', 'dbpassword' => 'secret', 'installed' => true, 'instanceid' => 'ocrdo3b60mb3', 'memcache.local' => ' OC Memcache Redis', 'memcache.distributed' => ' OC Memcache Redis', 'memcache.locking' => ' OC Memcache Redis', 'filelocking.enabled' => 'true', 'redis' => array ( 'host' => '127.0.0.1', 'port' => '6379', 'timeout' => '1.5', ), 'mail_smtpmode' => 'smtp', 'mail_smtphost' => 'smtp.example.com', 'mail_smtpport' => '425', 'mail_smtpsecure' => 'tls', 'mail_smtpauth' => 'true', 'mail_smtpauthtype' => 'LOGIN', 'mail_smtpname' => 'username', 'mail_smtppassword' => 'password', ); {quote}The manifests to reproduce (apply helper before) :{quote}class { 'nextcloud' : database_name => 'nextcloud_example', database_user => 'user_example', database_password => 'secret', system_user => 'www-data', config => Unknown macro: \ { 'trusted_domains' => [ 'localhost', 'cloud.example.com', ], } }{quote}The output when applyed is :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost']
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Dan33l updated an issue Puppet / PUP-10428 Puppet parser only consider first element of array for properties in custom provider Change By: Dan33l Attachment: config.php Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.41700.1587391980027%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title
Dan33l updated an issue
Puppet / PUP-10428
Puppet parser only consider first element of array for properties in custom provider
Change By:
Dan33l
*Puppet Version: Tested with 5.5.19* *Puppet Server Version: Without server, puppet apply* *OS Name/Version: Ubuntu 1804*I am working on this custom provider : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/lib/puppet/provider/nextcloud_config/php.rb]When the Puppet manifest have an Array as with setting trusted_domains, the setter receive the first element of the Array as a String and not an Array.To reproduce you can run acceptance tests like here :[https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/acceptance/nextcloud_spec.rb]Nextcloud is a PHP app. It requires a webserver and a database server before, like with spec helper acceptance : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/spec_helper_acceptance.rb]The module take care of PHP.*Desired Behavior:*Puppet take care of Array with following output :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to [['localhost','cloud.example.com']|http://cloud.example.com/]}}{quote} *Actual Behavior:*The Nextcloud's configuration is done in a config.php file like this one (have a look to setting trusted_domains that is array :{quote} $CONFIG = array ( 'passwordsalt' => 'XqxWppqWQ0/zMN/ur4wHn6SFTHhYLb', 'secret' => '+XEHiU8/1tfVkFL43QRepi5ev6i+vzU5jD3ZZjDd5MKuGEB8', 'trusted_domains' => array( 0 => 'localhost', ), 'datadirectory' => '/var/nextcloud-data', 'dbtype' => 'mysql', 'version' => '18.0.3.0', 'overwrite.cli.url' => 'http://localhost', 'dbname' => 'nextcloud_example', 'dbhost' => '127.0.0.1', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'user_example', 'dbpassword' => 'secret', 'installed' => true, 'instanceid' => 'ocrdo3b60mb3', 'memcache.local' => 'OC Memcache Redis', 'memcache.distributed' => 'OC Memcache Redis', 'memcache.locking' => 'OC Memcache Redis', 'filelocking.enabled' => 'true', 'redis' => array ( 'host' => '127.0.0.1', 'port' => '6379', 'timeout' => '1.5', ), 'mail_smtpmode' => 'smtp', 'mail_smtphost' => 'smtp.example.com', 'mail_smtpport' => '425', 'mail_smtpsecure' => 'tls', 'mail_smtpauth' => 'true', 'mail_smtpauthtype' => 'LOGIN', 'mail_smtpname' => 'username', 'mail_smtppassword' => 'password', );{quote}The manifests to reproduce (apply helper before) :{quote} class { 'nextcloud' : database_name => 'nextcloud_example', database_user => 'user_example', database_password => 'secret', system_user => 'www-data', config => { 'trusted_domains' => [ 'localhost', 'cloud.example.com', ], }}{quote} The output when applyed is :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to 'localhost'}}{quote} The
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title
Dan33l updated an issue
Puppet / PUP-10428
Puppet parser only consider first element of array for properties in custom provider
Change By:
Dan33l
*Puppet Version: Tested with 5.5.19* *Puppet Server Version: Without server, puppet apply* *OS Name/Version: Ubuntu 1804*I am working on this custom provider : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/lib/puppet/provider/nextcloud_config/php.rb]When the Puppet manifest have an Array as with setting trusted_domains, the setter receive the first element of the Array as a String and not an Array.To reproduce you can run acceptance tests like here :[https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/acceptance/nextcloud_spec.rb]Nextcloud is a PHP app. It requires a webserver and a database server before, like with spec helper acceptance : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/spec_helper_acceptance.rb]The module take care of PHP.*Desired Behavior:*Puppet take care of Array with following output :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to [['localhost','cloud.example.com']|http://cloud.example.com/] '] }}{quote} {{}} *Actual Behavior:*The Nextcloud's configuration is done in a config.php file like this one (have a look to setting trusted_domains that is array :{quote} $CONFIG = array ( 'passwordsalt' => 'XqxWppqWQ0/zMN/ur4wHn6SFTHhYLb', 'secret' => '+XEHiU8/1tfVkFL43QRepi5ev6i+vzU5jD3ZZjDd5MKuGEB8', 'trusted_domains' => array( 0 => 'localhost', ), 'datadirectory' => '/var/nextcloud-data', 'dbtype' => 'mysql', 'version' => '18.0.3.0', 'overwrite.cli.url' => 'http://localhost', 'dbname' => 'nextcloud_example', 'dbhost' => '127.0.0.1', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'user_example', 'dbpassword' => 'secret', 'installed' => true, 'instanceid' => 'ocrdo3b60mb3', 'memcache.local' => ' \\ OCMemcache Redis', 'memcache.distributed' => ' \\ OCMemcache Redis', 'memcache.locking' => ' \\ OCMemcache Redis', 'filelocking.enabled' => 'true', 'redis' => array ( 'host' => '127.0.0.1', 'port' => '6379', 'timeout' => '1.5', ), 'mail_smtpmode' => 'smtp', 'mail_smtphost' => 'smtp.example.com', 'mail_smtpport' => '425', 'mail_smtpsecure' => 'tls', 'mail_smtpauth' => 'true', 'mail_smtpauthtype' => 'LOGIN', 'mail_smtpname' => 'username', 'mail_smtppassword' => 'password', );{quote}The manifests is to reproduce (apply helper before) : {quote} class { 'nextcloud' : database_name => 'nextcloud_example', database_user => 'user_example', database_password => 'secret', system_user => 'www-data', config => { 'trusted_domains' => [ 'localhost', ' [ cloud.example.com |http://cloud.example.com/] ', ], }} {quote} The output when applyed is :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value:
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title
Dan33l updated an issue
Puppet / PUP-10428
Puppet parser only consider first element of array for properties in custom provider
Change By:
Dan33l
*Puppet Version: Tested with 5.5.19* *Puppet Server Version: Without server, puppet apply* *OS Name/Version: Ubuntu 1804*I am working on this custom provider : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/lib/puppet/provider/nextcloud_config/php.rb]When the Puppet manifest have an Array as with setting trusted_domains, the setter receive the first element of the Array as a String and not an Array.To reproduce you can run acceptance tests like here :[https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/acceptance/nextcloud_spec.rb]Nextcloud is a PHP app. It requires a webserver and a database server before, like with spec helper acceptance : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/spec_helper_acceptance.rb]The module take care of PHP.*Desired Behavior:*Puppet take care of Array with following output :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to [ [ 'localhost',' [ cloud.example.com '] |http://cloud.example.com/]']}}{quote}{{}} *Actual Behavior:*The Nextcloud's configuration is done in a config.php file like this one (have a look to setting trusted_domains that is array :{quote} $CONFIG = array ( 'passwordsalt' => 'XqxWppqWQ0/zMN/ur4wHn6SFTHhYLb', 'secret' => '+XEHiU8/1tfVkFL43QRepi5ev6i+vzU5jD3ZZjDd5MKuGEB8', 'trusted_domains' => array( 0 => 'localhost', ), 'datadirectory' => '/var/nextcloud-data', 'dbtype' => 'mysql', 'version' => '18.0.3.0', 'overwrite.cli.url' => 'http://localhost', 'dbname' => 'nextcloud_example', 'dbhost' => '127.0.0.1', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'user_example', 'dbpassword' => 'secret', 'installed' => true, 'instanceid' => 'ocrdo3b60mb3', 'memcache.local' => '\\OC \\ MemcacheRedis', 'memcache.distributed' => '\\OC \\ MemcacheRedis', 'memcache.locking' => '\\OC \\ MemcacheRedis', 'filelocking.enabled' => 'true', 'redis' => array ( 'host' => '127.0.0.1', 'port' => '6379', 'timeout' => '1.5', ), 'mail_smtpmode' => 'smtp', 'mail_smtphost' => 'smtp.example.com', 'mail_smtpport' => '425', 'mail_smtpsecure' => 'tls', 'mail_smtpauth' => 'true', 'mail_smtpauthtype' => 'LOGIN', 'mail_smtpname' => 'username', 'mail_smtppassword' => 'password', );{quote}The manifests is class { 'nextcloud' : database_name => 'nextcloud_example', database_user => 'user_example', database_password => 'secret', system_user => 'www-data', config =>{ 'trusted_domains' => [ 'localhost', '[cloud.example.com|http://cloud.example.com/] ', ], }} The output when applyed is :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to 'localhost'}}{quote} The expected output is
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title
Dan33l updated an issue
Puppet / PUP-10428
Puppet parser only consider first element of array for properties in custom provider
Change By:
Dan33l
*Puppet Version: Tested with 5.5.19* *Puppet Server Version: Without server, puppet apply* *OS Name/Version: Ubuntu 1804*I am working on this custom provider : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/lib/puppet/provider/nextcloud_config/php.rb]When the Puppet manifest have an Array as with setting trusted_domains, the setter receive the first element of the Array as a String and not an Array.To reproduce you can run acceptance tests like here :[https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/acceptance/nextcloud_spec.rb]Nextcloud is a PHP app. It requires a webserver and a database server before, like with spec helper acceptance : [https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/spec_helper_acceptance.rb]The module take care of PHP.*Desired Behavior:*Puppet take care of Array with following output :{quote}{{Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to ['localhost','[cloud.example.com|http://cloud.example.com/]']}} {quote}{{}}*Actual Behavior:*The Nextcloud's configuration is done in a config.php file like this one (have a look to setting trusted_domains that is array :{quote}$CONFIG = array ( 'passwordsalt' => 'XqxWppqWQ0/zMN/ur4wHn6SFTHhYLb', 'secret' => '+XEHiU8/1tfVkFL43QRepi5ev6i+vzU5jD3ZZjDd5MKuGEB8', 'trusted_domains' => array( 0 => 'localhost', ), 'datadirectory' => '/var/nextcloud-data', 'dbtype' => 'mysql', 'version' => '18.0.3.0', 'overwrite.cli.url' => 'http://localhost', 'dbname' => 'nextcloud_example', 'dbhost' => '127.0.0.1', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'user_example', 'dbpassword' => 'secret', 'installed' => true, 'instanceid' => 'ocrdo3b60mb3', 'memcache.local' => '\\OC\\Memcache \\ Redis', 'memcache.distributed' => '\\OC\\Memcache \\ Redis', 'memcache.locking' => '\\OC\\Memcache \\ Redis', 'filelocking.enabled' => 'true', 'redis' => array ( 'host' => '127.0.0.1', 'port' => '6379', 'timeout' => '1.5', ), 'mail_smtpmode' => 'smtp', 'mail_smtphost' => 'smtp.example.com', 'mail_smtpport' => '425', 'mail_smtpsecure' => 'tls', 'mail_smtpauth' => 'true', 'mail_smtpauthtype' => 'LOGIN', 'mail_smtpname' => 'username', 'mail_smtppassword' => 'password',);{quote}The manifests is class { 'nextcloud' :database_name => 'nextcloud_example',database_user => 'user_example',database_password => 'secret',system_user => 'www-data',config=> { { 'trusted_domains' => [ 'localhost', '[cloud.example.com|http://cloud.example.com/] ', ], } }The output when applyed is :{quote}{{Notice:
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title
Tim Meusel commented on PUP-10351
Re: Puppet Agent fails to self-restart on config change or update
I've multiple centos boxes, but most of them have nothing in their journal except the restart message.
root ~ # facter -p os
{
architecture => "x86_64",
family => "RedHat",
hardware => "x86_64",
name => "CentOS",
release => {
full => "7.7.1908",
major => "7",
minor => "7"
},
selinux => {
config_mode => "enforcing",
config_policy => "targeted",
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title
Dan33l created an issue
Puppet / PUP-10428
Puppet parser only consider first element of array for properties in custom provider
Issue Type:
Bug
Affects Versions:
PUP 5.5.19
Assignee:
Unassigned
Created:
2020/04/20 6:50 AM
Priority:
Normal
Reporter:
Dan33l
Puppet Version: Tested with 5.5.19 Puppet Server Version: Without server, puppet apply OS Name/Version: Ubuntu 1804 I am working on this custom provider : https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/lib/puppet/provider/nextcloud_config/php.rb When the Puppet manifest have an Array as with setting trusted_domains, the setter receive the first element of the Array as a String and not an Array. To reproduce you can run acceptance tests like here : https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/acceptance/nextcloud_spec.rb Nextcloud is a PHP app. It requires a webserver and a database server before, like with spec helper acceptance : https://gitlab.adullact.net/adullact/puppet-nextcloud/-/blob/36-add-nextcloud_config-type-provider/spec/spec_helper_acceptance.rb The module take care of PHP. Desired Behavior: Puppet take care of Array with following output :
Notice: /Stage[main]/Nextcloud::Config/Nextcloud_config[trusted_domains]/value: value changed ['localhost'] to 'localhost','[cloud.example.com
{{}} Actual Behavior: The Nextcloud's configuration is done in a config.php file like this one (have a look to setting trusted_domains that is array :
$CONFIG = array ( 'passwordsalt' => 'XqxWppqWQ0/zMN/ur4wHn6SFTHhYLb', 'secret' => '+XEHiU8/1tfVkFL43QRepi5ev6i+vzU5jD3ZZjDd5MKuGEB8', 'trusted_domains' =>
Jira (FACT-2494) Facts should not throw exception when resolver returns nill
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2494 Facts should not throw exception when resolver returns nill Change By: Andrei Filipovici Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.351078.1585137985000.41668.1587383580036%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Mihai Buzgau commented on PUP-10351 Re: Puppet Agent fails to self-restart on config change or update Tim Meusel can you paste the log before the first lock started happening? Can you also provide more information about your environment (eg. are you using PE)? Do you have an insight about what changed that triggered the puppet agent restart, did you upgrade the puppet agent version, what configuration changed? It would be great if you could set your log_level to debug and post the full log of an affected node. Can you provide information about your environment (Mater OS, Agent OS) Are you using any specific module to manage the Puppet Agent configuration? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.348520.1583329295000.41606.1587373440035%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Tim Meusel commented on PUP-10351 Re: Puppet Agent fails to self-restart on config change or update I thought to try something new and noticed that I could just start the agent on the cmdline, if the daemon logs `Shutdown/restart in progress (:restart_requested); skipping run`. At least on this box it wasn't required to kill the agent. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.348520.1583329295000.41585.158736927%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Tim Meusel commented on PUP-10351 Re: Puppet Agent fails to self-restart on config change or update Hello people, I see this error on multiple nodes in my environment, at the moment all of them are running puppet 6.12.0 and 6.14.0: Apr 09 12:03:19 puppet-agent[27550]: Starting Puppet client version 6.12.0 Apr 09 12:03:19 puppet-agent[27550]: Could not run: Could not create PID file: /var/run/puppetlabs/agent.pid Apr 09 12:03:19 systemd[1]: puppet.service: main process exited, code=exited, status=1/FAILURE Apr 09 12:03:19 systemd[1]: Unit puppet.service entered failed state. Apr 09 12:03:19 systemd[1]: puppet.service failed. Apr 09 12:03:23 puppet-agent[21586]: Config file /etc/puppetlabs/puppet/puppet.conf changed; triggering re-parse of all config files. Apr 09 13:59:35 puppet-agent[21586]: Shutdown/restart in progress (:restart_requested); skipping run Apr 09 15:59:35 puppet-agent[21586]: Shutdown/restart in progress (:restart_requested); skipping run Apr 09 17:59:35 puppet-agent[21586]: Shutdown/restart in progress (:restart_requested); skipping run Apr 09 19:59:35 puppet-agent[21586]: Shutdown/restart in progress (:restart_requested); skipping run Apr 09
