Database migration 20200425182634 failed: Unknown column 'background_file_id' #584

New Issue

deanishe · 2020-06-13T05:57:05Z

deanishe commented

2020-06-13 05:57:05 +00:00

Vikunja version: 0.13.1+51-980be0e4e0
Database: MySQL

I've just updated from 0.12+36-12e18de8ad, and Vikunja is throwing the following error:

2020/06/13 05:49:18 Using config file: /etc/vikunja/config.yml
2020/06/13 05:49:18 Redis initialized
2020-06-13T05:49:18.362694843Z: WARNING ▶ [DATABASE] 005 Table migration Column id db default is 'NULL', struct default is
2020-06-13T05:49:18.363319731Z: WARNING ▶ [DATABASE] 006 Table migration Column description db default is 'NULL', struct default is
2020-06-13T05:49:18.437209656Z: CRITICAL        ▶ migration/Migrate 02c Migration failed: migration 20200425182634 failed: Error 1054: Unknown column 'background_file_id' in 'field list'

Vikunja version: 0.13.1+51-980be0e4e0 Database: MySQL I've just updated from 0.12+36-12e18de8ad, and Vikunja is throwing the following error: ``` 2020/06/13 05:49:18 Using config file: /etc/vikunja/config.yml 2020/06/13 05:49:18 Redis initialized 2020-06-13T05:49:18.362694843Z: WARNING ▶ [DATABASE] 005 Table migration Column id db default is 'NULL', struct default is 2020-06-13T05:49:18.363319731Z: WARNING ▶ [DATABASE] 006 Table migration Column description db default is 'NULL', struct default is 2020-06-13T05:49:18.437209656Z: CRITICAL ▶ migration/Migrate 02c Migration failed: migration 20200425182634 failed: Error 1054: Unknown column 'background_file_id' in 'field list' ```

mp68 commented

2020-06-13 10:11:30 +00:00

I'm also experiencing migration issues on MySQL using the latest release (docker vikunja/api:0.13.1):

2020/06/13 10:06:21 Config File "config" Not Found in "[/app/vikunja /etc/vikunja /app/vikunja/.config/vikunja]",
2020/06/13 10:06:21 Using default config.,
2020-06-13T10:06:21.393034112Z: WARNING	▶ [DATABASE] 004 Table migration Column id db default is 'NULL', struct default is ,
2020-06-13T10:06:21.393101088Z: WARNING	▶ [DATABASE] 005 Table migration Column description db default is 'NULL', struct default is ,
2020-06-13T10:06:21.398580341Z: CRITICAL	▶ migration/Migrate 026 Migration failed: migration 20200516123847 failed: Error 1146: Table 'vikunja.list20200516123847' doesn't exist

I'm also experiencing migration issues on MySQL using the latest release (docker vikunja/api:0.13.1): ``` 2020/06/13 10:06:21 Config File "config" Not Found in "[/app/vikunja /etc/vikunja /app/vikunja/.config/vikunja]", 2020/06/13 10:06:21 Using default config., 2020-06-13T10:06:21.393034112Z: WARNING ▶ [DATABASE] 004 Table migration Column id db default is 'NULL', struct default is , 2020-06-13T10:06:21.393101088Z: WARNING ▶ [DATABASE] 005 Table migration Column description db default is 'NULL', struct default is , 2020-06-13T10:06:21.398580341Z: CRITICAL ▶ migration/Migrate 026 Migration failed: migration 20200516123847 failed: Error 1146: Table 'vikunja.list20200516123847' doesn't exist ```

konrad added the

kind/bug

label 2020-06-13 11:42:09 +00:00

konrad commented

2020-06-13 17:20:27 +00:00

Migrations are difficult to test, therefore they can contain bugs. I'll try to put up a fix later today.

konrad commented

2020-06-13 17:34:55 +00:00

@deanishe I've pushed a possible fix for that migration in a15b1bebba. Could you test with the new version once the ci passes (in aprox. 45min)?

@mp68 Interesting you got that error, because the failing migration is not part of 0.13.1, only on master. It is faulty though. I've fixed it in d9d00ba60c.
Maybe you were upgrading from 0.13.1?

And now I'm gonna figure out how to get this stuff in the test pipeline...

@deanishe I've pushed a possible fix for that migration in https://kolaente.dev/vikunja/api/commit/a15b1bebbab6758841d66f9380590c50e159309d. Could you test with the new version once [the ci passes](http://drone.kolaente.de/vikunja/api/1823) (in aprox. 45min)? @mp68 Interesting you got that error, because the failing migration is not part of 0.13.1, only on master. It is faulty though. I've fixed it in https://kolaente.dev/vikunja/api/commit/d9d00ba60c0a095a006821805bfac33939018c0b. Maybe you were upgrading from 0.13.1? And now I'm gonna figure out how to get this stuff in the test pipeline...

konrad referenced this issue

2020-06-13 19:48:52 +00:00

Add migration test in drone #585

deanishe commented

2020-06-13 21:19:19 +00:00

Maybe you were upgrading from 0.13.1?

Not originally, though I tried that, too. Same problem.

To be clear, I tried to upgrade to one of the daily builds, not a tagged release.

Thanks for the super-quick fix. I'll give it another try in the morning.

> Maybe you were upgrading from 0.13.1? Not originally, though I tried that, too. Same problem. To be clear, I tried to upgrade to one of the daily builds, not a tagged release. Thanks for the super-quick fix. I'll give it another try in the morning.

konrad commented

2020-06-13 21:23:59 +00:00

Maybe you were upgrading from 0.13.1?

That was meant towards the issue @mp68 had :)

I’ll give it another try in the morning.

Looking forward! Unfortuntately, this is a bit hard to test for me but I've since added an extra step in the test pipeline to catch issues like this one earlier in the process. Hopefully this means no more issues like this one.

> Maybe you were upgrading from 0.13.1? That was meant towards the issue @mp68 had :) > I’ll give it another try in the morning. Looking forward! Unfortuntately, this is a bit hard to test for me but I've since [added an extra step in the test pipeline](https://kolaente.dev/vikunja/api/pulls/585) to catch issues like this one earlier in the process. Hopefully this means no more issues like this one.

mp68 commented

2020-06-14 09:12:34 +00:00

@mp68 Interesting you got that error, because the failing migration is not part of 0.13.1, only on master. It is faulty though. I've fixed it in d9d00ba60c.
Maybe you were upgrading from 0.13.1?

Running super smooth again! Thanks a lot! I had some issues with my docker deploy setup, it might be possible it skipped a few versions.

> @mp68 Interesting you got that error, because the failing migration is not part of 0.13.1, only on master. It is faulty though. I've fixed it in https://kolaente.dev/vikunja/api/commit/d9d00ba60c0a095a006821805bfac33939018c0b. > Maybe you were upgrading from 0.13.1? Running super smooth again! Thanks a lot! I had some issues with my docker deploy setup, it might be possible it skipped a few versions.

👍 1

deanishe commented

2020-06-16 12:02:20 +00:00

Works like a charm. Thanks very much!

deanishe closed this issue

2020-06-16 12:02:23 +00:00

Sign in to join this conversation.