-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Debian Linux 9.13
OpenSSH 7.4p1
-
-
3.11.2
After updating jenkins to 2.361 and all plugins to latest versions, jenkins ssh attempts to clone gitlab repository (standard git client) and fails with output:
Setting origin to git@gitlab.xxxxx:yyyy/project.git
> git config remote.origin.url git@gitlab.xxxxx:yyyy/project.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
> git --version # timeout=10
> git --version # 'git version 2.11.0'
> git config --get remote.origin.url # timeout=10
using GIT_SSH to set credentials Gitlab Jenkins SSH Key
Verifying host key using known hosts file, will automatically accept unseen keys
> git fetch --tags --progress – origin +refs/heads/:refs/remotes/origin/ # timeout=10
hudson.plugins.git.GitException: Command "git fetch --tags --progress – origin +refs/heads/:refs/remotes/origin/" returned status code 128:
stdout:
stderr: command-line line 0: unsupported option "accept-new".
fatal: Could not read from remote repository.
Manually executing "ssh -o StrictHostKeyChecking=accept-new gitlab" returns error. Substituting 'accept-new' with 'no' results in no error.
- causes
-
JENKINS-69310 Host key verification failed.Could not read from remote repository
- Closed
- is duplicated by
-
JENKINS-69201 Git checkout fails with 'returned status code 128' on Linux agent with OpenSSH 7.4
- Closed
-
JENKINS-69213 Update to 3.11.1 breaks ssh auth with AWS Linux 2 and other OpenSSH 7.4 implementations
- Closed
- links to