Jira (PUP-2645) puppet module build checksums.json has incorrect metadata.json md5
Title: Message Title Jascha Lee created an issue Puppet / PUP-2645 puppet module build checksums.json has incorrect metadata.json md5 Issue Type: Bug Affects Versions: 3.6.0 Assignee: Unassigned Created: 22/May/14 3:32 PM Labels: module Priority: Minor Reporter: Jascha Lee 'puppet module build' modifies metadata.json. However, the checksum in checksums.json is for the unmodified metadata.json file, not the one that is built for the module. The consequence is that 'puppet module changes' shows: Warning: 1 files modified metadata.json Either it should not modify the metadata.json or it should checksum the modified file. Add Comment
Jira (PUP-2421) stringify_facts needs to be in agent, not master conf file
Title: Message Title Jascha Lee created an issue Puppet / PUP-2421 stringify_facts needs to be in agent, not master conf file Issue Type: Bug Affects Versions: 3.5.0 Assignee: Eric Sorenson Components: DOCS Created: 01/May/14 12:09 PM Priority: Minor Reporter: Jascha Lee http://docs.puppetlabs.com/puppet/3.5/reference/release_notes.html state: You have to manually enable this by setting stringify_facts = false in puppet.conf on your puppet master(s) I believe this is incorrect. This should be set in the [main] section on each agent. I think this is also true for the global facts hash Add Comment
Jira (PUP-1748) mco package status "undefined method `new' for nil:NilClass"
Title: Message Title Jascha Lee created an issue Puppet / PUP-1748 mco package status "undefined method `new' for nil:NilClass" Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Attachments: errors.txt Created: 21/Feb/14 2:40 PM Environment: CentOS 5.8 mcollective-2.4.0-1.el5 mcollective-package-4.2.2-1.el5 Priority: Normal Reporter: Jascha Lee After upgrading from 3.3.1 to 3.4.3, mco package status reports: undefined method `new' for nil:NilClass related to not being able to autoload various puppet/provider/package for most hosts. This makes mco package status unreliable. Downgrading back to puppet 3.3.1 fixes the problem.
Jira (PDB-107) PuppetDB must accept CA certificate chains
Title: Message Title Jascha Lee commented on an issue Re: PuppetDB must accept CA certificate chains Agent outputs: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for sp01.en1.company.com to PuppetDB at sp01.en1.company.com:3274: Connection refused - connect(2) puppetdb exception in the attached file: In the puppetdb log, the following exception is written: 2013-12-31 23:56:27,080 WARN [qtp2125787399-47] [io.nio] javax.net.ssl.SSLHandshakeException: General SSLEngine problem Add Comment PuppetDB / PDB-107 PuppetDB must accept CA certificate chains We are using puppet with external CA and we are trying introduce PuppetDB. We have the following CA chain: ROOT CA -> Intermediate CA -> node certs (configured according to http://docs.puppetlabs.com/puppet/3/reference/config_ssl_external_ca.html#option-2-single-intermediate-ca) When we run the agent, we get the following error: "[unable to get ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-107) PuppetDB must accept CA certificate chains
Title: Message Title Jascha Lee updated an issue PuppetDB / PDB-107 PuppetDB must accept CA certificate chains Exception thrown by /usr/sbin/puppetdb-foreground --debug when agent runs when puppetdb's ca.pem has multiple certs. Change By: Jascha Lee Attachment: puppetdb.txt Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
