No ECDSA host key is known for github.houston.softwaregrp.net and you have requested strict checking.

[prathapar]

Describe the bug
Geting the issue : No ECDSA host key is known for github.houston.softwaregrp.net and you have requested strict checking.
A clear and concise description of what the bug is.
[root@hcmx-sonarqube ~]# fluxctl sync --k8s-fwd-ns flux
Error: git repository ssh://git@xxxx/CSA/poc.git is not ready to sync

Full error message: git clone --mirror: fatal: Could not read from remote repository., full output:
Cloning into bare repository '/tmp/flux-gitclone008195832'...
No ECDSA host key is known for github.houston.softwaregrp.net and you have requested strict checking.
Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Run 'fluxctl sync --help' for usage.

To Reproduce

Steps to reproduce the behaviour:

1. Provide Flux install instructions
2. Provide a GitHub repository with Kubernetes manifests

Expected behavior

A clear and concise description of what you expected to happen.

Logs

If applicable, please provide logs of fluxd. In a standard stand-alone installation of Flux, you'd get this by running kubectl logs deploy/flux -n flux.

Additional context

• Flux version:
• Kubernetes version:
• Git provider:
• Container registry provider:

[hiddeco]

https://docs.fluxcd.io/en/1.19.0/guides/use-private-git-host/ (indexed in the documentation search engine as ECDSA).

[prathapar]

Thank you

[oleksdovz]

one more stupid fix:
run inside flux pod:
bash-5.0# ssh-keyscan -p 30007 git.server > ~/.ssh/known_hosts

[JorgeMGuimaraes]

Dashboard > Manage Jenkins > Configure Global Security > Git Host Key Verification Configuration.
Then in Host Key Verification Strategy select Accept first connection.

[rajatroy-athene]

Dashboard > Manage Jenkins > Configure Global Security > Git Host Key Verification Configuration.
Then in Host Key Verification Strategy select Accept first connection.
@JorgeMGuimaraes :: Works fine . Thank you !!!

[guilhermexd11]

Dashboard > Manage Jenkins > Configure Global Security > Git Host Key Verification Configuration. Then in Host Key Verification Strategy select Accept first connection.

Worked for me, Thanks !!!!!!!!!!!!!

[Michael1337]

Dashboard > Manage Jenkins > Configure Global Security > Git Host Key Verification Configuration. Then in Host Key Verification Strategy select Accept first connection.

Worked, thanks!
I guess for security reasons it's best to set it back to only known hosts after the new IP address was added successfully.

Edit: Nevermind, I guess whenever the container gets restarted, the host file resets and the host will be unknown again. So we either have to bind the host file to the outside docker host or leave the config to accept first connections.

[siddhesh724]

Failed to connect to repository : Command "git ls-remote -h -- [email protected]:siddhesh724/XYZ.git HEAD" returned status code 128:
stdout:
stderr: command-line line 0: unsupported option "accept-new".
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

: comment how can i solve this. i did this :
Dashboard > Manage Jenkins > Configure Global Security > Git Host Key Verification Configuration.
Then in Host Key Verification Strategy select Accept first connection.
but not working

[kingdonb]

I am not sure how this issue is related to Flux, or why folks are finding it more often these days.

This repo will be archived soon:

• Repository Archival Proposal #3645

Is there a more relevant repo where we can link these visitors? I'm not certain what y'all have in common, save for Jenkins afaict. Are you all really using Flux v1, or is this issue a top search result for some other search terms that I'm unaware of?