Jira (PDB-4945) Allow configuring the fact cache type to be json
Title: Message Title Josh Cooper commented on PDB-4945 Re: Allow configuring the fact cache type to be json I have a PR open for this in the puppetlabs-puppetdb module. I'm not sure if anything needs to be done in the puppetdb repo itself? 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.376183.1603814027000.71140.1604453760035%40Atlassian.JIRA.
Jira (PDB-4944) Set up a primary server using the JSON fact cache
Title: Message Title Josh Cooper commented on PDB-4944 Re: Set up a primary server using the JSON fact cache I tested this by running the puppetserver presuite which installs puppetdb using the puppetlabs-puppetdb module. I ssh'ed to the server and edited routes.yaml.erb to use json as the fact terminus, and then ran all of puppet's server beaker tests using the last passing puppetserver#main build. All of the tests passed: $ env | grep BEAKER BEAKER_LOADPATH=ruby/puppet/acceptance/lib BEAKER_OPTIONSFILE=acceptance/config/beaker/options.rb BEAKER_HELPER=acceptance/lib/helper.rb BEAKER_PRESUITE=acceptance/suites/pre_suite/foss BEAKER_TESTSUITE=ruby/puppet/acceptance/tests BEAKER_POSTSUITE=acceptance/suites/post_suite BEAKER_TYPE=aio $ echo $GEM_SOURCE https://artifactory.delivery.puppetlabs.net/artifactory/api/gems/rubygems/ $ ./acceptance/scripts/generic/testrun.sh -p ...
Jira (PDB-4877) Prefer JSON fact terminus for fact cache to YAML
Title: Message Title Josh Cooper commented on PDB-4877 Re: Prefer JSON fact terminus for fact cache to YAML This looks like a dup of PDB-4945, so I'm going to close it. 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.371010.1599070036000.71076.1604452140026%40Atlassian.JIRA.
Jira (PDB-4961) Change deprecation warning for PG 9.6 to non fatal error message for Puppet 7
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4961 Change deprecation warning for PG 9.6 to non fatal error message for Puppet 7 Change By: Josh Cooper Labels: platform7 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.376722.160409420.71071.1604451960381%40Atlassian.JIRA.
Jira (PUP-10720) Update `cadir` default to return the new location post-migration
Title: Message Title Tony Vu updated an issue Puppet / PUP-10720 Update `cadir` default to return the new location post-migration Change By: Tony Vu Release Notes: Deprecation Release Notes Summary: Beginning in Puppet 7, the default value for the `cadir` setting will be located in the puppetserver conf directory, specifically at /etc/puppetlabs/puppetserver/ca. Previously, the default location was inside puppet's own ssldir. This change will make it safer to delete the puppet's own `ssldir` without accidentally deleting your CA certificates.The puppetserver ca cli provides a `migrate` command to move the ca directory from the puppet conf to the puppetserver conf. It will leave behind a symlink on the old ca location, pointing to the new location at /etc/puppetlabs/puppetserver/ca. This link will provide backwards compatibility for tools still expecting the cadir to exist in the old location. In a future version of puppet, the cadir setting will be removed entirely. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10720) Update `cadir` default to return the new location post-migration
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-10720 Update `cadir` default to return the new location post-migration Change By: Maggie Dreyer Fix Version/s: PUP 7.0.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.375129.1602802813000.70773.1604440380091%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper commented on PUP-10772 Re: fresh puppet agent installation fails when msgpack is enabled on puppetserver Merged to master in https://github.com/puppetlabs/puppet/commit/09405d485a3411597773f2e8a2873fc09f77caba. Note this fixes the agent side of the problem. It would still be good to understand why puppetserver used `rich_data_msgpack` when `Puppet[:preferred_serialization_format]` defaults to json, so `rich_data_json` should have taken precedence. 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.376434.1603966281000.70727.1604438880070%40Atlassian.JIRA.
Jira (PDB-4961) Change deprecation warning for PG 9.6 to non fatal error message for Puppet 7
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4961 Change deprecation warning for PG 9.6 to non fatal error message for Puppet 7 Change By: Zachary Kent Assignee: Zachary Kent 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.376722.160409420.70712.1604438340201%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10772 fresh puppet agent installation fails when msgpack is enabled on puppetserver Change By: Josh Cooper Sprint: 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.376434.1603966281000.70631.1604433780041%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10772 fresh puppet agent installation fails when msgpack is enabled on puppetserver 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.376434.1603966281000.70632.1604433780096%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10772 fresh puppet agent installation fails when msgpack is enabled on puppetserver Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: The agent claimed to accept catalogs serialized using the "rich_data_msgpack" format, but if the "msgpack" gem wasn't installed, then the agent would fail to deserialize the catalog and fail the run. Now the agent only claims to support that format when the "msgpack" gem is installed. 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.376434.1603966281000.70624.1604432820026%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper commented on PUP-10772 Re: fresh puppet agent installation fails when msgpack is enabled on puppetserver Also wanted to mention there is an issue with JRuby sorting arrays PUP-8615. While that ticket is about sorting formats used in pops serialization, it may explain some non-deterministic behavior with how puppetserver is sorting network formats based on their weight? 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.376434.1603966281000.70623.1604432580104%40Atlassian.JIRA.
Jira (PUP-10773) Add a server alias for routes.yaml
Title: Message Title Josh Cooper created an issue Puppet / PUP-10773 Add a server alias for routes.yaml Issue Type: Task Assignee: Unassigned Created: 2020/11/03 8:08 AM Priority: Normal Reporter: Josh Cooper The puppetlabs-puppetdb module used to configure puppetdb and its terminus, creates a routes.yaml to configure various termini. The file defines a hash where each key is the name of a puppet application and the termini each indirected class should be using. See https://github.com/puppetlabs/puppetlabs-puppetdb/blob/78b9df2f20d623ad59259ad8b507cb322484473a/manifests/master/routes.pp#L7 Puppet should add an alias so that when routes.yaml is parsed, it accepts either server or master applications. /cc Austin Blatt Add Comment
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Sebastian Miclea commented on FACT-2847 Re: Facter 4 breaks rspec on fact test Martin Alfke, yes unfortunately Facter 4 cannot run with Puppet5. Puppet5 has the Facter dependency locked to > 2.0.1, < 4 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.376201.1603820546000.70260.1604415840033%40Atlassian.JIRA.
Jira (PDB-3311) Improve error message on "index row size" exceptions
Title: Message Title zendesk.jira updated an issue PuppetDB / PDB-3311 Improve error message on "index row size" exceptions Change By: zendesk.jira Zendesk Ticket Count: 1 Zendesk Ticket IDs: 41774 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.177208.1488227809000.70170.1604399880099%40Atlassian.JIRA.
Jira (PDB-3311) Improve error message on "index row size" exceptions
Title: Message Title zendesk.jira updated an issue PuppetDB / PDB-3311 Improve error message on "index row size" exceptions Change By: zendesk.jira Labels: jira_escalated maintenance 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.177208.1488227809000.70169.1604399880057%40Atlassian.JIRA.
