Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image Updater not able to connect to Gitlab Repo #735

Closed
vipul0805 opened this issue Jun 4, 2024 · 1 comment · Fixed by #737
Closed

Image Updater not able to connect to Gitlab Repo #735

vipul0805 opened this issue Jun 4, 2024 · 1 comment · Fixed by #737
Labels
bug Something isn't working

Comments

@vipul0805
Copy link

Describe the bug
A clear and concise description of what the bug is.
I recently upgraded ArgoCD image updater to the latest version v0.13.1. I checked the docs and set the value of applicationsAPIKind: kubernetes as both ArgoCd and the image updater run in the same cluster.

After the update the image updater cannot connect to the gitlab repo. Here is the error:

level=error msg="`git fetch origin --tags --force` failed exit status 128: error: cannot run argocd: No such file or directory\nfatal: could not read Username for 'http://10.29.218.114:10002': terminal prompts disabled" execID=bbbb3

I cannot figure out where it is looking for the credentials.

Additional context
In the docs the image updater is reading the token from a secret named argocd-image-updater-secret. I do not have any secret created and its not clear from the docs whether it needs to be created if using Method 1 in the Install guide.

Version
ArgoCD image updater: v0.13.1
ArgoCD: 2.11.2

@vipul0805 vipul0805 added the bug Something isn't working label Jun 4, 2024
@chengfang
Copy link
Collaborator

The errors are the same in the other issue #728 . Can you check if this is the same issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants