Jira (PDB-2590) /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Title: Message Title Frédéric Lespez commented on PDB-2590 Re: /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini Seeing this bug since PDB 6.15 on Debian Buster. I have never seen it before. Running puppetdb ssl-setup -f also changes the permissions of the jetty.ini file from 644 to 640 which prevents PuppetDB to start. Before running puppetdb ssl-setup -f: # ls -l /etc/puppetlabs/puppetdb/conf.d/jetty.ini-rw-r--r-- 1 root root 2554 mars 27 17:18 /etc/puppetlabs/puppetdb/conf.d/jetty.ini After running puppetdb ssl-setup -f: # ls -l /etc/puppetlabs/puppetdb/conf.d/jetty.ini-rw-r- 1 root root 2592 mars 27 17:19 /etc/puppetlabs/puppetdb/conf.d/jetty.ini Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97
Jira (PDB-5084) Fix ssl-setup client-auth insinuation
Title: Message Title Frédéric Lespez commented on PDB-5084 Re: Fix ssl-setup client-auth insinuation Running puppetdb ssl-setup -f also changes the permissions of the jetty.ini file from 644 to 640 which prevents PuppetDB to start. Before running puppetdb ssl-setup -f: # ls -l /etc/puppetlabs/puppetdb/conf.d/jetty.ini -rw-r--r-- 1 root root 2554 mars 27 17:18 /etc/puppetlabs/puppetdb/conf.d/jetty.ini After running puppetdb ssl-setup -f: # ls -l /etc/puppetlabs/puppetdb/conf.d/jetty.ini -rw-r- 1 root root 2592 mars 27 17:19 /etc/puppetlabs/puppetdb/conf.d/jetty.ini This permission problem seems to be old (See PDB-2590). But I have never seen it before. As far I can see, it has been introduced with the last version (6.15.0) Add Comment
Jira (PDB-5084) Fix ssl-setup client-auth insinuation
Title: Message Title Frédéric Lespez commented on PDB-5084 Re: Fix ssl-setup client-auth insinuation Seeing this bug with PDB 6.15 on Debian Buster. 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.393060.1616792845000.175694.1616861760050%40Atlassian.JIRA.
Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname
Title: Message Title Frédéric Lespez commented on FACT-2944 Re: During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname Hi Josh Cooper , I made a test on another platform (not a test one but a production one) where the problem was present too. And I can confirm it is now fixed. Thanks ! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387583.1613309929000.165526.1615621440033%40Atlassian.JIRA.
Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname
Title: Message Title Frédéric Lespez commented on FACT-2944 Re: During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname Hi Mihai Buzgau , I used this package (the one without the debug symbols) : http://nightlies.puppet.com/apt/pool/buster/puppet7-nightly/p/puppet-agent/puppet-agent_7.4.1.109.g573c9c580-1buster_amd64.deb And it is a success ! Great job ! Thanks a lot. Here is the full log. root@puppetdev:~# ls -1 /etc/puppetlabs/puppet/ssl/*/puppetdev*.pem /etc/puppetlabs/puppet/ssl/certs/puppetdev.example.org.pem /etc/puppetlabs/puppet/ssl/certs/puppetdev.pem /etc/puppetlabs/puppet/ssl/private_keys/puppetdev.example.org.pem /etc/puppetlabs/puppet/ssl/private_keys/puppetdev.pem /etc/puppetlabs/puppet/ssl/public_keys/puppetdev.example.org.pem /etc/puppetlabs/puppet/ssl/public_keys/puppetdev.pem root@puppetdev:~# puppetserver ca list --all The cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info. Signed Certificates
Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname
Title: Message Title Frédéric Lespez commented on FACT-2944 Re: During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname Hi Oana Tanasoiu, Here the output you ask (with puppet-agent_7.4.1.90.g54cd2d413-1buster_amd64.deb installed) : root@puppetdev:~# puppet --version 7.5.0 root@puppetdev:~# puppetserver --version puppetserver version: 7.0.3 root@puppetdev:~# facter --version 4.0.52 root@puppetdev:~# puppetserver irb irb(main):001:0> require 'facter' => true irb(main):002:0> Facter.version => "4.0.52" If you need the output with another package ver
Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname
Title: Message Title Frédéric Lespez commented on FACT-2944 Re: During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname Hi Oana Tanasoiu , I just tried the puppet-agent nightly package on the same platform. The problem is till there. I don't see any differences root@puppetdev:~# puppetserver ca list --all The cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info. Signed Certificates: puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19 puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0 puppetdev (SHA256) 74:44:78:C8:66:97:1E:38:E5:73:E0:47:02:38:21:CD:2C:EF:FB:C0:05:C1:D9:9C:55:2A:7F:9F:D9:0C:F8:3E alt names: ["DNS:puppetdev.example.org", "DNS:puppetdev", "DNS:puppetdev"] authorization extensions: [pp_cli_auth: true] puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20 alt names: ["DNS:puppetdev.example.org", "DNS:puppetdev", "DNS:puppetdev.example.org"] authorization extensions: [pp_cli_auth: true] root@puppetdev:~# puppet node clean puppetdev Warn
Jira (PUP-10321) Resource 'notify': Attribute 'message' accepts Array but only use the first element
Title: Message Title Frédéric Lespez commented on PUP-10321 Re: Resource 'notify': Attribute 'message' accepts Array but only use the first element Ticket PUP-10346 opened to improve the documentation. 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.348009.1582967531000.2814.1583260260050%40Atlassian.JIRA.
Jira (PUP-10346) Resource 'notify': Attribute 'message' should be more precise about the type of data accepted
Title: Message Title Frédéric Lespez created an issue Puppet / PUP-10346 Resource 'notify': Attribute 'message' should be more precise about the type of data accepted Issue Type: Improvement Assignee: Unassigned Created: 2020/03/03 10:27 AM Priority: Normal Reporter: Frédéric Lespez Since PUP-10321 won't be fixed, I think that the documentation of 'notify' resource should be improved. It should precise that even if the 'message' attributes accepts hashes or arrays, its behavior is only guaranteed for strings. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935
Jira (PUP-10321) Resource 'notify': Attribute 'message' accepts Array but only use the first element
Title: Message Title Frédéric Lespez commented on PUP-10321 Re: Resource 'notify': Attribute 'message' accepts Array but only use the first element I will open a ticket to update the docs. For the record, I discovered this when I was debugging a manifest. I lost a lot of time figuring out it was notify that was mangling the data. At the beginning, I wasn't even expecting the 'message' attributes to accept hashes, but it does and it handles them 'logically'. So in the end, I assumed it was also the case for arrays... My bad. Allowing notify to do the string conversion may not be the solution but doing nothing is endorsing weird behavior. Why not changing the 'message' attributes so that it only accepts strings ? At least, notify behavior will be coherent with predicable results. 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.348009.1582967531000.2613.1583255520028%40Atlassian.JIRA.
Jira (PUP-10321) Resource 'notify': Attribute 'message' accepts Array but only use the first element
Title: Message Title
Frédéric Lespez created an issue
Puppet / PUP-10321
Resource 'notify': Attribute 'message' accepts Array but only use the first element
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/02/29 1:12 AM
Priority:
Normal
Reporter:
Frédéric Lespez
Puppet Version: 6.13.0 Puppet Server Version: 6.9.0 OS Name/Version: Debian 10 (Buster) Consider the following code:
class test_notify {
$a = ['a', 'b', 'c']
$b = {'a' => 1, 'b' => 2, 'c' => 3 }
notify {
'Array':
