Upgrade to v1.8.0 fails due to failing migration

[christianhueserhzdr]

Summary

Upgrade fails from v1.7.2 to v1.8.0 due to migration errors that spam the log with messages such as {"timestamp":"2025-05-15 05:51:34.350 Z","level":"warn","msg":"Failed to apply upgrade function","caller":"app/plugin_api.go:1014","plugin_id":"com.github.matterpoll.matterpoll","poll_id":"poll_xxx","error":"Failed to get post for migration: GetSinglePost: Unable to get the post."}

Steps to reproduce

Steps to reproduce the behavior:

1. Upgrade plugin from v1.7.2 to v1.8.0 by replacing archive in folder prepackaged_plugins.

Expected behavior

Upgrade with migration succeeds.

Observed behavior (that appears unintentional)

Service went down due to failing plugin migrations. Log contains messages such as:

{"timestamp":"2025-05-15 05:51:34.350 Z","level":"warn","msg":"Failed to apply upgrade function","caller":"app/plugin_api.go:1014","plugin_id":"com.github.matterpoll.matterpoll","poll_id":"poll_xxx","error":"Failed to get post for migration: GetSinglePost: Unable to get the post."}

Server configuration

Operating system:

Ubuntu 24.04.1 LTS

Mattermost version:

10.6.1

Matterpoll version:

1.8.0

Updated from an older Matterpoll version or fresh install:

Mattermost server logs

{"timestamp":"2025-05-15 05:51:34.350 Z","level":"warn","msg":"Failed to apply upgrade function","caller":"app/plugin_api.go:1014","plugin_id":"com.github.matterpoll.matterpoll","poll_id":"poll_xxx","error":"Failed to get post for migration: GetSinglePost: Unable to get the post."}

[hanzei]

Thanks for the report @christianhueserhzdr. Would you be open to sharing the log messages around the migration? There might be other related logs line.

[christianhueserhzdr]

Thanks for the report @christianhueserhzdr. Would you be open to sharing the log messages around the migration? There might be other related logs line.

Dear Ben, thank you very much for looking into this issue. These are a couple of logs around the migration. Other than that, there is not much more to see. Please let me know if you have further questions. Thanks!

{"timestamp":"2025-05-15 05:29:56.660 Z","level":"warn","msg":"The database schema version of 1.7.2 appears to be out of date.","caller":"app/plugin_api.go:1014","plugin_id":"com.github.matterpoll.matterpoll"}
{"timestamp":"2025-05-15 05:29:56.661 Z","level":"warn","msg":"Attempting to upgrade the database schema version to 1.8.0.","caller":"app/plugin_api.go:1014","plugin_id":"com.github.matterpoll.matterpoll"}
{"timestamp":"2025-05-15 05:30:34.019 Z","level":"warn","msg":"Failed to apply upgrade function","caller":"app/plugin_api.go:1014","plugin_id":"com.github.matterpoll.matterpoll","poll_id":"poll_1euhdi45pjrzbn9cwhef71sgjo","error":"Failed to get post for migration: GetSinglePost: Unable to get the post."}
{"timestamp":"2025-05-15 05:31:05.178 Z","level":"warn","msg":"Failed to apply upgrade function","caller":"app/plugin_api.go:1014","plugin_id":"com.github.matterpoll.matterpoll","poll_id":"poll_1urpj84463drixx3rrymz6ga4a","error":"Failed to get post for migration: GetSinglePost: Unable to get the post."}
{"timestamp":"2025-05-15 05:31:22.085 Z","level":"warn","msg":"Failed to apply upgrade function","caller":"app/plugin_api.go:1014","plugin_id":"com.github.matterpoll.matterpoll","poll_id":"poll_3149dgeec7dmxmscyfiaaax4ny","error":"Failed to update post after migration: UpdatePost: Can not update a post in a deleted channel."}
{"timestamp":"2025-05-15 05:31:43.267 Z","level":"warn","msg":"Failed to apply upgrade function","caller":"app/plugin_api.go:1014","plugin_id":"com.github.matterpoll.matterpoll","poll_id":"poll_3dhtetjwwpynfjxoh35uop56se","error":"Failed to get post for migration: GetSinglePost: Unable to get the post."}
[...]

[kaakaa]

Thanks @christianhueserhzdr. Those kind of message are just warning message, and should not cause the plugin startup failure. Once migration run, the database schema version should be successfully updated. Could you try starting Matterpoll v1.8.0 again, and if it doesn't start properly, could you check if other types of logs are being output?

[christianhueserhzdr]

Dear Yusuke @kaakaa, you were completely right. Indeed, those warnings did not interrupt the migration, but the server showed for about 1h30min the error status 503. After completion the server was available again. Would it be possible to run the migration more in the background in order to not make it unavailable during the migration? Thank you very much!