Mattermost version check failure on fresh install due to missing config and log directory
The mattermost recipe was checking the mattermost version before the config and directories were put in place. In addition our migration error logging for mattermost now logs as the mattermost user. Previously, on error the log may not have been created before this error message, and logging as root would cause a permission problem on the file for future runs.
Split from !898 (closed) to more tightly address the current problem. .
Fixes: #1388 (closed)
Merge request reports
Activity
mentioned in merge request !898 (closed)
Tested the upgrade from mattermost 2.2 I think it works the same as before, which isn't great. As in on upgrade, even though the recipe shuts it down, the upgrade script starts mattermost back up because it was running before the upgrade, which burries our logged message a bit in mattermost.log. Also the warning isn't really seen in omnibus output, just in the mattermost log. Once I set the team and backup in the gitlab.rb it upgraded fine.
I also tested fresh install, and also upgrading from 8.10.3 with a root owned log file, to the new release. And that all worked.
added workflowproduction label and removed workflowstaging-ref label