gdk install fails on db seed and other possible side effects

Apologies in advance if this is covered under an existing issue somewhere. I've searched for something similar, but have not found anything similar.

I am experiencing what I think are actually few issues.

The first issue I see is already called out here: #389 (closed). WARNING: This version of GitLab depends on gitlab-shell 8.1.0, but you're running 8.0.0. Please update gitlab-shell.

The second issue I see happens after the db migrations are run and we begin to seed the db. For some reason, all of the project seeds appear to fail without any feedback: Screen_Shot_2018-08-14_at_8.39.39_AM

Seeding continues but once I get to environments, I run into this error Gitlab::Git::CommandError: 4:Deadline Exceeded: Screen_Shot_2018-08-14_at_8.40.30_AM

--

I have attempted to update gitlab-shell using the make gitlab-shell-update, but that does not appear to actually update gitlab-shell. Which makes sense, based on the issue called out above.

Now, even though I see these errors on gdk install, I am still able to run the app locally. I see 8 projects, but none have a supporting repo or any other meta data.

The last thing I tried was to create a new repo using a template. That also eventually results in this error: Screen_Shot_2018-08-14_at_7.24.32_AM

Curiously, I see another reference to a deadline exceeded error. Perhaps this is related to the error(s) I see on db seed?

--

Last week I was able to install and run locally without issue and, somewhere along the way, things broke. The issues and steps here are based on a fresh install following the set-up-gdk doc.

Again, I apologize for the multiple issue issue. I'm hopeful that these errors are all somewhat related or that I've missed a configuration change somewhere along the way. I'm happy to split this issue up if that makes more sense.

  • os: osx 10.11.6
  • rvm: ruby-2.4.4
Edited by Nate Geslin