Failed Migrations when upgrading from v3.7.8 to v4.1.7 #19539
Unanswered
kevinscottuk
asked this question in
Q&A
Replies: 1 comment
-
I had a similar issue when doing the change from v3.7.8 to 4.2.x. For me it turned out that one of my custom scripts caused the migration to fail. The script in question was accesing device_type, but that key had changed names from v3 to v4 and is now called only device. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When running
./upgrade.sh
when the process gets to Running Migrations it fails with this output.Beta Was this translation helpful? Give feedback.
All reactions