argo-cd: v2.5.0-rc1 HA argocd-repo-server CrashLoopBackOff

Checklist:

  • I’ve searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I’ve included steps to reproduce the bug.
  • I’ve pasted the output of argocd version.

Describe the bug Update argocd from 2.4.14 to 2.5.0-rc1 via kustomize old url: https://raw.githubusercontent.com/argoproj/argo-cd/v2.4.14/manifests/ha/install.yaml new url: https://raw.githubusercontent.com/argoproj/argo-cd/v2.5.0-rc1/manifests/ha/install.yaml

Everything is comming up except argocd-repo-server, log can be found below

Expected behavior No issues with gpg inside the repo server

Version

argocd: v2.5.0-rc1+2bf51f4
  BuildDate: 2022-10-05T17:41:04Z
  GitCommit: 2bf51f401d6700f8e8b9565d9fc3f66dcf60a0b6
  GitTreeState: clean
  GoVersion: go1.18.6
  Compiler: gc
  Platform: linux/amd64
argocd-server: v2.5.0-rc1+2bf51f4
  BuildDate: 2022-10-05T17:14:51Z
  GitCommit: 2bf51f401d6700f8e8b9565d9fc3f66dcf60a0b6
  GitTreeState: clean
  GoVersion: go1.18.7
  Compiler: gc
  Platform: linux/amd64
  Kustomize Version: v4.5.7 2022-08-02T16:35:54Z
  Helm Version: v3.10.0+gce66412
  Kubectl Version: v0.24.2
  Jsonnet Version: v0.18.0

Logs

k -n argocd logs -f argocd-repo-server-7b4d9b979-cf8dg
time="2022-10-10T14:15:51Z" level=info msg="ArgoCD Repository Server is starting" built="2022-10-05T17:14:51Z" commit=2bf51f401d6700f8e8b9565d9fc3f66dcf60a0b6 port=8081 version=v2.5.0-rc1+2bf51f4
time="2022-10-10T14:15:51Z" level=info msg="Generating self-signed TLS certificate for this session"
time="2022-10-10T14:15:51Z" level=info msg="Initializing GnuPG keyring at /app/config/gpg/keys"
time="2022-10-10T14:15:51Z" level=info msg="gpg --no-permission-warning --logger-fd 1 --batch --gen-key /tmp/gpg-key-recipe735869143" dir= execID=30201
time="2022-10-10T14:15:57Z" level=error msg="`gpg --no-permission-warning --logger-fd 1 --batch --gen-key /tmp/gpg-key-recipe735869143` failed exit status 2" execID=30201
time="2022-10-10T14:15:57Z" level=info msg=Trace args="[gpg --no-permission-warning --logger-fd 1 --batch --gen-key /tmp/gpg-key-recipe735869143]" dir= operation_name="exec gpg" time_ms=6010.954976

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (4 by maintainers)

Most upvoted comments

@benjamin-bergia thanks a lot, that worked nicely. @crenshaw-dev I tried to hack my way around having to do a custom build (changing the entrypoint to do that/opening a shell and running the command with debug options), but I did not succeed in a reasonable timeframe, sorry! Might look into it again

Just as @benjamin-bergia I had the same issue upgrading v2.4.14 to v2.5.0 just now. The workaround that you mentioned @crenshaw-dev did not work for me.