[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.

6 views
Skip to first unread message

wb8tyw@gmail.com (JIRA)

unread,
Jun 19, 2018, 5:46:03 PM6/19/18
to jenkinsc...@googlegroups.com
John Malmberg created an issue
 
Jenkins / Bug JENKINS-52051
git-parameter exec: nc: not found.
Issue Type: Bug Bug
Assignee: Boguslaw Klimas
Components: git-parameter-plugin
Created: 2018-06-19 21:45
Environment: master: Ubuntu 14.04, Agents: Ubuntu 14.04, CentOS 7.5, SLES-12SP2
Jenkins 2.128, git-parameter 0.9.2
Priority: Minor Minor
Reporter: John Malmberg

Occasionally not getting a list of tags for build with parameters.
The jenkins.log has this message:

WARNING: [ project-release ] Download tags from the repository failed
hudson.plugins.git.GitException: Command "git ls-remote -t ssh://gerrit.example.com:29418/group/project v18.*" returned status code 128:
stdout:
stderr: /bin/bash: line 0: exec: nc: not found
ssh_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.

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

.
On the CentOS 7.5 system, nc is at /usr/bin.

 nc --help
Ncat 7.50 ( https://nmap.org/ncat )

On the other systems, nc is at /bin and nc reports:

 nc -h
OpenBSD netcat (Debian patchlevel 1.105-7ubuntu1)
This is nc from the netcat-openbsd package. An alternative nc is available
in the netcat-traditional package.
jemalmbe@coral-sles12-1:~> nc -h
OpenBSD netcat (SUSE Linux)
This is nc from the netcat-openbsd package. An alternative nc is available
in the netcat-traditional package.

The access to the git repository is through ssh and the git repository is working.
If I configure a default tag value in the git parameter, that is used for building.
But when this happens, I have no way to automatically build the top tag sorted from the list by default.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

klimas7@gmail.com (JIRA)

unread,
Jun 22, 2018, 3:30:02 PM6/22/18
to jenkinsc...@googlegroups.com

klimas7@gmail.com (JIRA)

unread,
Feb 18, 2019, 5:02:03 PM2/18/19
to jenkinsc...@googlegroups.com
Boguslaw Klimas commented on Bug JENKINS-52051
 
Re: git-parameter exec: nc: not found.

Hi,

I can't reproduce this issue, but I found code smells, which can provide to unexpected behavior. commit: f85678c3 I changed  it in release 0.9.10.

Additional I changed error handling, please look on wiki page

If this issue steal occurred in your environment after update the plugin. Please add more information which I can use to reproduce this issue and reopen this issue. 

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

klimas7@gmail.com (JIRA)

unread,
Feb 18, 2019, 5:02:03 PM2/18/19
to jenkinsc...@googlegroups.com
Boguslaw Klimas resolved as Cannot Reproduce
 

Release 0.9.10

Change By: Boguslaw Klimas
Status: Open Resolved
Resolution: Cannot Reproduce

wb8tyw@gmail.com (JIRA)

unread,
Feb 19, 2019, 12:01:01 PM2/19/19
to jenkinsc...@googlegroups.com
John Malmberg commented on Bug JENKINS-52051
 
Re: git-parameter exec: nc: not found.

I will try to verify this week.

The issue appears to be that the code was looking only for "/usr/bin/nc", and on the systems where the plugin was failing for me, the path needed is "/bin/nc".

So it should have been easy to reproduce by temporary moving nc to /bin/nc on a test system.

wb8tyw@gmail.com (JIRA)

unread,
Feb 19, 2019, 3:07:02 PM2/19/19
to jenkinsc...@googlegroups.com

It is still failing to find the releases when using Ubuntu or SLESS/(Open SUSE Leap) build agents.

It looks like it is still coded to use /usr/bin/nc instead of checking to see where the nc program really is.

wb8tyw@gmail.com (JIRA)

unread,
Feb 19, 2019, 3:08:02 PM2/19/19
to jenkinsc...@googlegroups.com
John Malmberg reopened an issue
 
Change By: John Malmberg
Resolution: Cannot Reproduce
Status: Resolved Reopened

wb8tyw@gmail.com (JIRA)

unread,
Feb 19, 2019, 3:12:02 PM2/19/19
to jenkinsc...@googlegroups.com
John Malmberg edited a comment on Bug JENKINS-52051
It is still failing to find the releases when using Ubuntu or SLESS/(Open SUSE Leap) build agents.

It looks like it is still coded to use generating a different message in the log.
{code}
WARNING: [ argobots-release ]  Download tags from the repository failed
hudson.plugins.git.GitException: Command "git ls-remote -t ssh:
/ usr / bin review.hpdd.intel.com:29418 / nc instead of checking to see where the nc program really daos/argobots v1" returned status code 128:
stdout:
stderr: Permission denied (publickey).

fatal: Could not read from remote repository.
{code}

The repository
is access via a SSH-AGENT supplied credentials .

wb8tyw@gmail.com (JIRA)

unread,
Feb 19, 2019, 3:20:01 PM2/19/19
to jenkinsc...@googlegroups.com
John Malmberg edited a comment on Bug JENKINS-52051
It is still failing to find the releases when using Ubuntu or SLESS/(Open SUSE Leap) build agents.

It is generating a different message in the log.

{code}
WARNING: [ argobots-release ]  Download tags from the repository failed
hudson.plugins.git.GitException: Command "git ls-remote -t ssh://review. hpdd example . intel. com:29418/daos/argobots v1" returned status code 128:

stdout:
stderr: Permission denied (publickey).
fatal: Could not read from remote repository.
{code}

The repository is access via a SSH-AGENT supplied credentials.

wb8tyw@gmail.com (JIRA)

unread,
Feb 19, 2019, 3:21:02 PM2/19/19
to jenkinsc...@googlegroups.com

Except for the error message, the behavior seems to be the same. It is only working if the build agent is running CentOS,
It is not working if the build agent is running Ubuntu 14.04, or SLES 12SP2.

wb8tyw@gmail.com (JIRA)

unread,
Feb 19, 2019, 3:30:03 PM2/19/19
to jenkinsc...@googlegroups.com

Changing the repository entry to have the ssh credentials with it did not change the behavior.

klimas7@gmail.com (JIRA)

unread,
Jun 18, 2019, 3:37:02 PM6/18/19
to jenkinsc...@googlegroups.com
Boguslaw Klimas resolved as Fixed
 

Hi,

I released plugin in version 0.9.11 where this issue was resolved, could you check that and confirm the issue is resolved

 
Regards
Boguslaw

Change By: Boguslaw Klimas
Status: Reopened Resolved
Resolution: Fixed

wb8tyw@gmail.com (JIRA)

unread,
Jul 15, 2019, 12:27:03 PM7/15/19
to jenkinsc...@googlegroups.com
 
Re: git-parameter exec: nc: not found.

Still not working.
Only change is now nothing is logged to the /var/log/jenkins/log on failure.

Did you try reproducing this by temporarily moving where the nc command is located on the build agent?
That is what I see different on the for the distros where it works and does not work, and that also goes along with the original bug report.

wb8tyw@gmail.com (JIRA)

unread,
Jul 15, 2019, 12:28:02 PM7/15/19
to jenkinsc...@googlegroups.com
John Malmberg reopened an issue
 

Still not working.

Change By: John Malmberg
Resolution: Fixed
Status: Resolved Reopened
Reply all
Reply to author
Forward
0 new messages