[JIRA] (JENKINS-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

[priyankarathi@gmail.com (JIRA)]

Priyanka Rathi updated an issue

Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Change By: Priyanka Rathi Summary: Unable to git clone on slave ,agent is launched via ssh . Git clone working fine on master Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[priyankarathi@gmail.com (JIRA)]

Priyanka Rathi commented on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Mark Waite If 1080 is non default port, it is still working for master. Not sure why it is not working for slave. Could you please throw some light ?

Add Comment

[priyankarathi@gmail.com (JIRA)]

Priyanka Rathi updated JENKINS-55972

Jenkins / JENKINS-55972

Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Change By: Priyanka Rathi Resolution: Not A Defect Status: Fixed but Unreleased Reopened

Add Comment

[priyankarathi@gmail.com (JIRA)]

Priyanka Rathi commented on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master new error now .It is not giving me any error related to port Cloning the remote Git repositoryCloning the remote Git repositoryCloning repository https://********.git > /usr/bin/git init /AutoCSA/${workspace} # timeout=10Fetching upstream changes from https://********.git > /usr/bin/git --version # timeout=10using GIT_ASKPASS to set credentials Bitbucket service user > /usr/bin/git fetch --tags --progress https://********.git +refs/heads/:refs/remotes/origin/ # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://********.git +refs/heads/:refs/remotes/origin/" returned status code 128:stdout: stderr: error: cannot run /AutoCSA//AutoCSA//AutoCSA/${workspace}@tmp/jenkins-gitclient-pass7876213394703629191.sh: No such file or directoryfatal: could not read Username for 'https://********.com': terminal prompts disabled at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1905) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:81) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:488) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:712) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to csa-automation-node1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor865.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy79.execute(Unknown Source) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1135) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1810) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)ERROR: Error cloning remote repo 'origin'Finished: FAILURE

Add Comment

[kshultz@cloudbees.com (JIRA)]

Karl Shultz updated an issue

Jenkins / JENKINS-55972

Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Change By: Karl Shultz Attachment: screenshot-1.png

Add Comment

[kshultz@cloudbees.com (JIRA)]

Karl Shultz commented on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Priyanka Rathi - what version of the git and git-client plugins are you running right now? You can see this by looking at https://your-jenkins:jenkins-port/pluginManager/installed. For example, here is one of mine. I've got it set up to use the experimental update center, meaning it's running beta-level code, including (but not limited to) these release-candidate versions of git and git-client.

Add Comment

[priyankarathi@gmail.com (JIRA)]

Priyanka Rathi commented on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Karl Shultz its same as yours.

Add Comment

[priyankarathi@gmail.com (JIRA)]

Priyanka Rathi updated an issue

Jenkins / JENKINS-55972

Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Change By: Priyanka Rathi Attachment: image-2019-02-05-23-28-19-792.png

Add Comment

[kshultz@cloudbees.com (JIRA)]

Karl Shultz updated an issue

Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Change By: Karl Shultz Attachment: screenshot-2.png

Add Comment

[kshultz@cloudbees.com (JIRA)]

Karl Shultz commented on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master OK, thanks for that. Next questions: 1. Did this job work correctly before you updated to the rc levels of the plugin? 2. Can you provide more details as far as the job? When you say "clone git repository" in the description of this bug report, do you mean: As part of a Jenkins Pipeline job? If yes, is it Declarative or Scripted? As part of a Freestyle job? As part of something else? 3. Let's assume it's a Multibranch Pipeline job for the moment. Did you use Git as your SCM provider, or GitHub? That's a mistake I've made before. I'm talking about this pulldown: 4. Any idea where the port number 1080 came from? Is that the port that your own Git server is listening on? 5. Is it possible that some other service is blocking port 1080? For my environments, that could be a security group setting in AWS, or a firewall setting who-knows-where, etc. Basically, some steps to recreate the issue would really help pin down what's wrong.

Add Comment

[priyankarathi@gmail.com (JIRA)]

Priyanka Rathi commented on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Did this job work correctly before you updated to the rc levels of the plugin? - This job was created yesterday itself. So I have not tried git clone on slave before.

2. Can you provide more details as far as the job? When you say "clone git repository" in the description of this bug report, do you mean:

As part of a Jenkins Pipeline job? If yes, is it Declarative or Scripted? - no As part of a Freestyle job? - yes

As part of something else?

3. Let's assume it's a Multibranch Pipeline job for the moment. Did you use Git as your SCM provider, or GitHub? That's a mistake I've made before. I'm talking about this pulldown:

its a freestyle job.  4. Any idea where the port number 1080 came from? Is that the port that your own Git server is listening on? - i have no clue about it.  5. Is it possible that some other service is blocking port 1080? For my environments, that could be a security group setting in AWS, or a firewall setting who-knows-where, etc. - if it was blocking , then it would have not worked for master as well. its not working only for slave

Add Comment

[priyankarathi@gmail.com (JIRA)]

Priyanka Rathi updated an issue

Jenkins / JENKINS-55972

Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Change By: Priyanka Rathi Attachment: image-2019-02-06-22-16-12-971.png

Add Comment

[priyankarathi@gmail.com (JIRA)]

Priyanka Rathi edited a comment on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master [~kshultz] # Did this job work correctly before you updated to the {{rc}} levels of the plugin? - This job was created yesterday itself. So I have not tried git clone on slave before.

2. Can you provide more details as far as the job? When you say "clone git repository" in the description of this bug report, do you mean:

* As part of a Jenkins Pipeline job? If yes, is it Declarative or Scripted? - no * As part of a Freestyle job? - yes * As part of something else? 3. Let's assume it's a Multibranch Pipeline job for the moment. Did you use {{Git}} as your SCM provider, or {{GitHub}}? That's a mistake I've made before. I'm talking about this pulldown: * its a freestyle job.  * !image-2019-02-06-22-16-12-971.png!

4. Any idea where the port number 1080 came from? Is that the port that your own Git server is listening on? - i have no clue about it.

5. Is it possible that some other service is blocking port 1080? For my environments, that could be a security group setting in AWS, or a firewall setting who-knows-where, etc. - if it was blocking , then it would have not worked for master as well. its not working only for slave :(

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-55972

Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Change By: Mark Waite Assignee: Mark Waite

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated JENKINS-55972

Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Change By: Mark Waite Status: Reopened Open

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated JENKINS-55972

Priyanka Rathi this is a bug database, not a place for help with configuration problems. I appreciate very much the questions from Karl Shultz to ask you enough questions so that you can find the configuration error in your environment. That's very kind of him. However, it is using a much smaller set of people that might be able to help with the configuratino problem and clutters the bug database with configuration related question and answer exchanges. If you can provide a numbered set of steps which will allow you to duplicate the problem on another computer, that dramatically increases the chances that you've found a bug. It also increases the chances that others can identify the area where the bug exists.

Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated JENKINS-55972

Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Change By: Mark Waite Status: Fixed but Unreleased Closed

Add Comment

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

[ashok.mohanty@oracle.com (JIRA)]

ASHOK MOHANTY commented on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master We are using git-client 3.0 and git plugin 4.0. Facing this error intermittently (inside a JNLP node). For cloning we are using a generic LDAP user without password. And/or please let me know the matching ticket where I can update this issue !! > GitLab: Your account has been blocked. fatal: Could not read from remote repository.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Gitlab blocking your account is not something that Jenkins or command line git can fix.

Add Comment

[ashok.mohanty@oracle.com (JIRA)]

ASHOK MOHANTY commented on JENKINS-55972

Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master

Its just intermittent issue, re-try/re-playing the job it works fine. Not really sure its issue from git-/client/plugin OR in GitLab repo side.

Add Comment