Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2

[Charlie Sharpsteen (JIRA)]

Title: Message Title

Charlie Sharpsteen commented on PDB-4642   Re: Puppet 2019.3 upgrade failure from 2019.2.2 This issue appears to be caused by PuppetDB running migrations in a non-UTC timezone. One workaround that doesn't require truncating the resource events table is to temporarily run PuppetDB with the timezone set to UTC: On RedHat 6: service pe-puppetdb stop systemctl stop pe-puppetdb /usr/bin/env TZ=utc /opt/puppetlabs/server/bin/puppetdb foreground Use Ctrl-C to stop PuppetDB after "PDBMigrationsPool - Shutdown completed" is logged On RedHat 6: service pe-puppetdb start systemctl start pe-puppetdb {bash} The above steps should work for Open Source PuppetDB 6.8.1 as well, use puppetdb as the service name instead of pe-puppetdb. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344931.1580780081000.22138.1581450840670%40Atlassian.JIRA.