500 error on initial login? about puppet-gitlab HOT 5 CLOSED

Just realized why gitlab-ci-rake of course wouldn't work - here's the output of the correct command:

[root@linvm2346 etc]# gitlab-rake db:migrate:status
Schema migrations table does not exist yet.

from puppet-gitlab.

I figured out that I needed to have the following code run:

if is_hash($postgresql) {
  unless $postgresql[enable] {
    exec { 'gitlab_setup':
      command     => '/bin/echo yes | /usr/bin/gitlab-rake gitlab:setup',
      refreshonly => true,
      timeout     => 1800,
      require     => Exec['gitlab_reconfigure'],
      unless      => "/bin/grep complete ${git_data_dir}/postgresql.setup"
    }
    ->
    file { "${git_data_dir}/postgresql.setup":
      content => 'complete'
    }

I don't see anything in the module documentation as to what should be placed into the postgresql hash - I would have tried just using enable => true, but it looks like that would also keep the setup code from firing, which is a bit confusing - am I reading this incorrectly? Is there a basic postgresql hash that can be used for an install that wants to use the defaults but configure the provided postgres db?

Also, it looks like $git_data_dir should be set to /var/opt/gitlab/postgresql/data (when using the default install location from the omnibus / module)? It looks like it defaults to undef, which means that the postgresql.setup file won't be created anywhere useful. The init file doesn't provide much clarification.

I'm happy to make a doc PR after I have this all figured out - I just want to make sure whatever I submit is correct. Thanks!

from puppet-gitlab.

Maybe we can ping @robbruce / @sd-robbruce, he did the implementation of this part in the module in #15

from puppet-gitlab.

As I didn't hear back any news on this issue, I'll close it right now. Feel free to open a new one.

from puppet-gitlab.

I re-opened this, as I ran into this block of code while working on #159.

I'm going to remove this block entirely, as it's likely to cause problems, (specifically this will cause #195).

Running this command will rebuild authorized keys, and will migrate the db, and neither will be wanted by the admin.

With gitlab 10.4 onward, gitlab has built in support for HA, which has many scenarios where postgres in disabled on a node, but the postgresql hash still has configuration in it allowing the application_role, consul_role, and pgbouncer_role nodes to connect to the postgres database.

from puppet-gitlab.