Bug#893450: gitlab: fresh install have no root account, default root password does not work
Please check the latest MR I made on to the gitlab project on salsa. I have updated the Debian README to include granting of admin rights to a selective user. Regards, Pavi
Bug#893450: gitlab: fresh install have no root account, default root password does not work
On Monday, 19 March 2018 9:19:32 PM AEDT Pirate Praveen wrote: > We need to update debian/rake-tasks.sh as given here, > > https://gitlab.com/gitlab-org/gitlab-ce/blob/v10.5.5/doc/install/installati > on.md#initialize-database-and-activate-advanced-features Unfortunately that does not create an account and freshly installed GitLab ends up without any accounts at all. To fix the problem I had to register new user (without logging in) then run the following from GitLab console: u = User.where(id: 1).first u.admin = true u.save exit Took me a while to find out that... ;) Regards, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part.
Bug#893450: gitlab: fresh install have no root account, default root password does not work
On Mon, 19 Mar 2018 11:15:11 +1100 Dmitry Smirnov wrote:> It is impossible to log in to fresh install of Gitlab using default root > password as per "/usr/share/doc/gitlab/README.md.gz" line 63. > > Could it be because root account does not exist? > > Although eventually it would be nice to fix the problem in the meantime > this issue should be documented in README.Debian... We need to update debian/rake-tasks.sh as given here, https://gitlab.com/gitlab-org/gitlab-ce/blob/v10.5.5/doc/install/installation.md#initialize-database-and-activate-advanced-features signature.asc Description: OpenPGP digital signature
Bug#893450: gitlab: fresh install have no root account, default root password does not work
Package: gitlab Version: 9.5.4+dfsg-7 Severity: normal It is impossible to log in to fresh install of Gitlab using default root password as per "/usr/share/doc/gitlab/README.md.gz" line 63. Could it be because root account does not exist? Although eventually it would be nice to fix the problem in the meantime this issue should be documented in README.Debian... Thanks, Dmitry Smirnov.
