Jira (PDB-4280) Ensure PE upgrade will work properly with reports migration

[Nick Walker (JIRA)]

Title: Message Title

Nick Walker commented on PDB-4280   Re: Ensure PE upgrade will work properly with reports migration Based on what I'm seeing in PE we only configure sync on the replica node. Looking something like this: [root@pe-replica ~]# cat /etc/puppetlabs/puppetdb/conf.d/sync.ini   [sync] server_urls = https://master201903-centos.puppetdebug.vlan:8081 intervals = 2m And sync is not configured on the primary. So if the primary is upgraded to a version of PuppetDB that has the new hash then I think it can require that the initiating PuppetDB sync sends along its schema_migration number. If no schema_migration number is sent along then the new PuppetDB version should not sync. Make sense? 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.