Last Update (6.3.0) broke Boards
-
Hey there,
does anybody else experience the same?
We were using Mattermost Boards (introduced in V6) and they disappeared after the last update to 6.3.0.I can still find the setting and tried disabling and enabling (hoping that would set a flag in DB). Unfortunately, it did not help.
I guess it would make sense to add boards to the tests too.
Best
Eugene
-
@mtd-sales same issue here
-
Indeed the Boards feature is not tested currently with out update tests. Is there already an upstream bug report for that or does it seem like a packaging bug? I have never used Boards in Mattermost, so have to try it out first to understand what it is.
-
@nebulon so I couldn’t find any upstream bugs reported but here is some info on what it is and how it is accessed:
https://docs.mattermost.com/guides/boards.html
https://docs.mattermost.com/boards/accessing-boards.html -
Thank you, guys.
Unfortunately, it didn't fix it for me, since plugins were already enabled.Then I found this in my logs:
Jan 18 11:25:23 {"timestamp":"2022-01-18 10:25:23.926 Z","level":"error","msg":"Not activating plugin because diagnostics are disabled","caller":"app/plugin_api.go:928","plugin_id":"com.mattermost.nps"}
So I enabled diagnostics. However this was the result (not sure if its related to this update):
Jan 18 11:28:35 {"timestamp":"2022-01-18 10:28:35.229 Z","level":"error","msg":"Unable to activate plugin","caller":"app/plugin.go:142","plugin_id":"focalboard","error":"error initializing the DB: Dirty database version 15. Fix and force version."}
-
@mtd-sales said in Last Update (6.3.0) broke Boards:
focalboard_schema_migrations
Was having the same issue and this seemed to work. TLDR; Seems like I only had to update
dirty
.Before Mattermost update:
select * from focalboard_schema_migrations; +---------+-------+ | version | dirty | +---------+-------+ | 14 | 0 | +---------+-------+
After Mattermost update:
select * from focalboard_schema_migrations; +---------+-------+ | version | dirty | +---------+-------+ | 15 | 1 | +---------+-------+
Then I ran the following:
update focal_schema_migrations set dirty=1 where dirty=0; commit;
Then I rebooted the Mattermost instance and checked the table again:
select * from focalboard_schema_migrations; +---------+-------+ | version | dirty | +---------+-------+ | 16 | 0 | +---------+-------+
Finally, I restarted Mattermost Desktop and checked that I could load Boards again, and it all works great.
-
@ashughes Perfect, that's correct.
Here is the answer:
https://github.com/mattermost/focalboard/issues/2119#issuecomment-1013751739@robi It's not an issue with cloudron. So I guess as soon as there is a fix by Mattermost it will also land here.
The only action step from @nebulon and cloudron would be to add some tests for boards in future releases.