Make sure to run gitlab:db:lock_writes when setting new database
When testing #393145 (closed), I realised gitlab:setup
is not called by Omnibus at all. It is only used by source install (https://docs.gitlab.com/ee/install/installation.html)
Proposal
Make gitlab:db:lock_writes
be called after some other rake task. Maybe gitlab:db:configure
? I think gitlab:db:configure
is called by Omnibus
We also need to make sure that this is not run too often. It should only run during initialisation of a new database
Edited by Rutger Wessels