sameersbn / sameersbn/docker-gitlab
Issue with gitlab image in OCP 4
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hello
I have deployed gitlab "image = " with postgres and redis , but every time it shows an error with puma and pod goes for crashloopbackoff error.
I have also tried with image with latest tag in quay,io
command used for deployment
oc new-app quay.io/sameersbn/gitlab:13.12.4 --name=gitlab -e 'GITLAB_HOST=https://gitlab.apps.example.com' -e 'DB_TYPE=postgres' -e 'DB_HOST=postgresql' -e 'DB_PORT=5432' -e 'DB_NAME=gitlab' -e 'DB_USER=admin' -e 'DB_PASS=redhat' -e 'REDIS_HOST=redis' -e 'REDIS_PORT=6379' -e 'GITLAB_SECRETS_DB_KEY_BASE=1234567890'
Error message
2021-09-06 10:44:36,458 INFO exited: puma (exit status 1; not expected)
rake aborted!
NoMethodError: undefined method `empty?' for 1234567890:Integer
/home/git/gitlab/lib/gitlab/utils.rb:54:in `ensure_utf8_size'
/home/git/gitlab/config/settings.rb:142:in `attr_encrypted_db_key_base_32'
/home/git/gitlab/app/models/concerns/ci/new_has_variable.rb:12:in `block in module:NewHasVariable'
/home/git/gitlab/vendor/bundle/ruby/2.7.0/gems/activesupport-6.0.3.6/lib/active_support/concern.rb:122:in `class_eval'
/home/git/gitlab/vendor/bundle/ruby/2.7.0/gems/activesupport-6.0.3.6/lib/active_support/concern.rb:122:in `append_features'
/home/git/gitlab/app/models/ci/instance_variable.rb:7:in `include'
/home/git/gitlab/app/models/ci/instance_variable.rb:7:in `class:InstanceVariable'
/home/git/gitlab/app/models/ci/instance_variable.rb:4:in `module:Ci'
/home/git/gitlab/app/models/ci/instance_variable.rb:3:in `<top (required)>'
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the exact oc new-app command and the puma crash log, then inspect the referenced files: lib/gitlab/utils.rb and config/settings.rb, along with the CI model files in the trace. Reproduce the deployment using the stated GitLab image, PostgreSQL, Redis, and environment variables. Done means puma starts successfully and the pod no longer enters CrashLoopBackOff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgres, redis, ruby
- Domain
- backend, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100