Jira (PDB-3357) PuppetDB fails to update catalogs when rich data types are enabled
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3357 PuppetDB fails to update catalogs when rich data types are enabled Change By: Rob Browning Team: Data Platform 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-3357) PuppetDB fails to update catalogs when rich data types are enabled
Title: Message Title Thomas Hallgren commented on PDB-3357 Re: PuppetDB fails to update catalogs when rich data types are enabled I created PUP-7427 as a quick way to get PuppetDB working with rich-data enabled, even it if doesn't recognize it as such. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3357) PuppetDB fails to update catalogs when rich data types are enabled
Title: Message Title
Charlie Sharpsteen created an issue
PuppetDB / PDB-3357
PuppetDB fails to update catalogs when rich data types are enabled
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/03/15 12:37 PM
Priority:
Normal
Reporter:
Charlie Sharpsteen
When a rich data type is added to a resource, the resulting catalog contains resources with ext_parameters keys. PuppetDB tries to work these new keys into an UPDATE operation on the catalog_resources table, which fails during statement preparation with a 'No hstore extension installed' error. No errors occur if the resource is initially stored with sensitive data.
The root cause for this behavior is the same as PDB-3322, which concerns the Sensitive data type.
Reproduction Case
Install PE 2017.1.0 on CentOS 7.
Add a file resource to the default node in /etc/puppetlabs/code/environments/production/manifests/site.pp that uses the binary_file function to manage content with binary data:
file{'/tmp/rich_data_test':
