-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Creds-init container process caused "invalid value "tekton-ssh-key={my own gitlab domain name}" for flag -ssh-git: exit status 1" #1350
Comments
/kind bug |
Additional Info Againwhen I add the "known_hosts" data into my Secret:
It works ! |
@gejunqiang thanks for the additional info. |
There are some instances where we can't add |
@dibyom are you still working on this or can we throw it back in the backlog? |
@dibyom We've been hitting by the same error for quite a long time...
For past 4 weeks there were at least 50 |
Hi, I was also facing this issue. We have a corporate github instance and this is reproducible whenever my VPN connection is not available. Maybe this info helps! |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle rotten |
@vdemeester: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The reason this error occurred was when ssh-keyscan couldn't reach a server over the internet (fixed by f112277). And the reason it appeared as a generic flag error was because we silently swallowed it during flag initialization (fixed by 1caf5bf). I'm reasonably confident we can safely consider this issue resolved now. Sorry for the churn! |
Expected Behavior
The task run normally.
Actual Behavior
The creds-init container step-credential-initializer (using the image of gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/creds-init@sha256:c8544b7182b53608f7b71f42c31295d8bf534ceeed14be735977c7e289fd37b7) is alway Error !
Steps to Reproduce the Problem
Additional Info
The text was updated successfully, but these errors were encountered: