fix: handle migration rename errors for v444→v445 upgrades #7320
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
cloud_init_scriptsmigration to handle rename from120000to120002webhook_notification_settingsmigration to handle rename from120000to120002Issues
Fixes: Users unable to upgrade from v4.0.0-beta.444 to v4.0.0-beta.445 due to "SQLSTATE[42P07]: Duplicate table" errors