Jira (PDB-5352) Re-allow branched migrations
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5352 Re-allow branched migrations Change By: David McTavish Priority: Normal Low Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.422927.1636493401000.13334.164450456%40Atlassian.JIRA.
Jira (PDB-5352) Re-allow branched migrations
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5352 Re-allow branched migrations Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.422927.1636493401000.12817.1644436380574%40Atlassian.JIRA.
Jira (PDB-5352) Re-allow branched migrations
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5352 Re-allow branched migrations Change By: Austin Blatt Our migration code properly distinguishes between "pending" migrations that it recognizes and has yet to apply, and unrecognized migrations, migrations that have been applied that it doesn't know about. But other parts of the migration orchestration code only look at the highest numbered migration. So in a world where we apply a migration to an old branch (6.x) you might have a set of migrations like...7879__81and this version would not notice that the schema was out of sync when the db is upgraded to the new branch (main) with the migrations...78798081It's important to keep in mind that we have done migration "roll-ups" as well. This means that migrations lower than the lowest number in our migration map should not be treated as "unrecognized" migrations.Our work to manage upgrades in multi-PuppetDB environments broke our migration model because it only check the most recent migration number and assumes we have all the others. This could result in a PuppetDB misidentifying a Postgres as having "valid schema" when in reality an upgrade is required. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PDB-5352) Re-allow branched migrations
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5352 Re-allow branched migrations Issue Type: Improvement Assignee: Unassigned Created: 2021/11/09 1:30 PM Priority: Normal Reporter: Austin Blatt Our work to manage upgrades in multi-PuppetDB environments broke our migration model because it only check the most recent migration number and assumes we have all the others. This could result in a PuppetDB misidentifying a Postgres as having "valid schema" when in reality an upgrade is required. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
