[JIRA] (JENKINS-60383) Remote nodes unable to checkout code

Remote nodes unable to checkout code

Issue Type:	Bug
Assignee:	Luca Domenico Milanesio
Components:	gerrit-code-review-plugin
Created:	2019-12-05 20:33
Environment:	jenkins 2.190.3 gerrit code review plugin 0.3.7
Labels:	slave
Priority:	Blocker
Reporter:	Will Wagner

Moving to 0.3.7 has broken checkout on remote nodes. They fail reporting unable to checkout the code after a 10 minute timeout.

In the log on the gerrit server are hundreds of lines saying:

WARN com.google.gerrit.httpd.ProjectBasicAuthFilter : Authentication failed for Username for 'https: account inactive or not provisioned in Gerrit

So it appears that the remote node is using the wrong credentials to try to do the checkout.

Reverting to .03.5 and everything works fine

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

willw@carallon.com (JIRA)

unread,

Dec 5, 2019, 4:43:04 PM12/5/19

to jenkinsc...@googlegroups.com

Will Wagner commented on

The output from the pipeline job that fails on a node is:

using credential 6e96f729-8440-40bf-8710-88689c791d3b
Cloning the remote Git repository
Cloning repository https://code.office.carallon.com/pharos/magpie
> C:\Program Files\Git\bin\git.exe init c:\jenkins\workspace\magpie-verify_01_8301_2 # timeout=10
Fetching upstream changes from https://code.office.carallon.com/pharos/magpie
> C:\Program Files\Git\bin\git.exe --version # timeout=10
using GIT_ASKPASS to set credentials
> C:\Program Files\Git\bin\git.exe fetch --tags --force --progress – https://code.office.carallon.com/pharos/magpie +refs/heads/:refs/remotes/origin/ # timeout=10
> C:\Program Files\Git\bin\git.exe config remote.origin.url https://code.office.carallon.com/pharos/magpie # timeout=10
> C:\Program Files\Git\bin\git.exe config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10
> C:\Program Files\Git\bin\git.exe config remote.origin.url https://code.office.carallon.com/pharos/magpie # timeout=10
Fetching upstream changes from https://code.office.carallon.com/pharos/magpie
using GIT_ASKPASS to set credentials
> C:\Program Files\Git\bin\git.exe fetch --tags --force --progress – https://code.office.carallon.com/pharos/magpie refs/changes/01/8301/2:refs/remotes/origin/01/8301/2 # timeout=10
Checking out Revision 787879583e36f6e3afc5b60d35d15409d2c6a11a (refs/remotes/origin/01/8301/2)
> C:\Program Files\Git\bin\git.exe rev-parse "01/8301/2^

{commit}" # timeout=10
> C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/01/8301/2^{commit}

" # timeout=10
> C:\Program Files\Git\bin\git.exe config core.sparsecheckout # timeout=10
> C:\Program Files\Git\bin\git.exe checkout -f 787879583e36f6e3afc5b60d35d15409d2c6a11a # timeout=10
ERROR: Timeout after 10 minutes

luca.milanesio@gmail.com (JIRA)

unread,

Dec 5, 2019, 5:33:01 PM12/5/19

to jenkinsc...@googlegroups.com

Luca Domenico Milanesio commented on

Have you checked which credentials are used and what are the ones you were expecting to use?

willw@carallon.com (JIRA)

unread,

Dec 5, 2019, 6:23:03 PM12/5/19

to jenkinsc...@googlegroups.com

Will Wagner commented on

I believe I am using the correct stored credentials, they work fine if I downgrade the module to 0.3.5.

They are https username and password that work everywhere else. Do they need to be something special?

willw@carallon.com (JIRA)

unread,

Dec 10, 2019, 3:37:03 AM12/10/19

to jenkinsc...@googlegroups.com

Will Wagner commented on

So looking at this some more, I believe it is the LFS Pull step that is using the wrong credentials. For some reason it previously used to say 'Enabling Git LFS pull' before it started this and did the config core.sparsecheckout.

nickb@carallon.com (JIRA)

unread,

Dec 19, 2019, 4:23:09 AM12/19/19

to jenkinsc...@googlegroups.com

Nick Bulleid commented on

https://review.gerrithub.io/c/jenkinsci/gerrit-code-review-plugin/+/477949

I've uploaded a fix for this issue to GerritHub.

luca.milanesio@gmail.com (JIRA)

unread,

Dec 30, 2019, 7:47:03 AM12/30/19

to jenkinsc...@googlegroups.com

Luca Domenico Milanesio commented on

Thanks Nick Bulleid looking at your fix right now.

luca.milanesio@gmail.com (JIRA)

unread,

Dec 30, 2019, 7:57:02 AM12/30/19

to jenkinsc...@googlegroups.com

Luca Domenico Milanesio commented on

Unfortunately, your fix is breaking existing functionality.

Let me reproduce the problem and see if there is another way to achieve the same result.

luca.milanesio@gmail.com (JIRA)

unread,

Dec 30, 2019, 8:31:02 AM12/30/19

to jenkinsc...@googlegroups.com

Luca Domenico Milanesio commented on

I just tried and it works for me. When the build is triggered on a remote host, I see:

using GIT_ASKPASS to set credentials jenkins-at-gerritci

In your case I see from your logs:

using GIT_ASKPASS to set credentials

luca.milanesio@gmail.com (JIRA)

unread,

Dec 30, 2019, 8:48:02 AM12/30/19

to jenkinsc...@googlegroups.com

Luca Domenico Milanesio commented on

Did you set the credentials id on the multi-branch pipeline job?

willw@carallon.com (JIRA)

unread,

Dec 30, 2019, 9:45:02 AM12/30/19

to jenkinsc...@googlegroups.com

Will Wagner updated an issue

Jenkins /

Remote nodes unable to checkout code

Change By:	Will Wagner
Attachment:	credentials.png

willw@carallon.com (JIRA)

unread,

Dec 30, 2019, 9:46:02 AM12/30/19

to jenkinsc...@googlegroups.com

Will Wagner commented on

We have set username/password credentials on the pipeline job, see uploaded image.

Out of interest what functionality is broken by our change?

luca.milanesio@gmail.com (JIRA)

unread,

Dec 30, 2019, 9:59:02 AM12/30/19

to jenkinsc...@googlegroups.com

Luca Domenico Milanesio commented on

https://gerrit.mycompany.com/a/myrepo

Can you try to use the Gerrit authenticated URL?

luca.milanesio@gmail.com (JIRA)

unread,

Dec 30, 2019, 11:15:03 AM12/30/19

to jenkinsc...@googlegroups.com

Luca Domenico Milanesio commented on