org.apache.hc.client5.http.HttpHostConnectException: Connect to unix://localhost:2375 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused #59
Comments
|
Same issue as in a previous version (#29 (comment)) Again, I fear there is nothing we can do besides downgrading the plugin and wait for a fix in the docker-plugin, docker-java or httpclient5. I’ll leave the issue open to update with new information and for others to see. |
|
Also reported to the docker plugin as:
|
|
Is there an upstream ticket for this issue? |
|
There is not an upstream ticket for this issue. I've not had the time to create the upstream ticket yet. It needs evaluation to understand the root of the failure. The last time there was a regression due to httpclient 5, I believe that it was related to packaging. I don't know the root cause of this regression. |
|
I believe the issue is far more likely to be resolved in a timely fashion if an upstream ticket is created |
|
I believe that we should either report an upstream ticket and push this process along with momentum, or revert the relevant upgrade in the Jenkins library plugin and block downloads of the problematic version from the Update Center. The status quo, wherein we do not take action upstream but continue to deliver the problematic release in the Update Center, results in pain for operators and end users. |
Agreed. I'll look for time this week or early next week to investigate the issue deeply enough so that I can submit an upstream issue. |
|
@MarkEWaite Is there a reason we continue to leave our users exposed to this issue one week after I brought it to your attention (as opposed to reverting the breaking change)? This puts our users in the unfortunate position of having broken software by default. |
I've left our users exposed because I hoped to find a better path to a solution. The weekend didn't allow it. I'll propose the revert of the httpclient 5 library upgrade and then will try later today to investigate more deeply. If a workaround is available that avoids reverting the library upgrade, that would be better than reverting the httpclient 5 library upgrade. |
Reverts 1991154 from jenkinsci#57 jenkinsci/docker-plugin#1032 describes the failure that end users encounter with httpclient 5.4 when connecting to the Docker daemon over a Unix domain socket. jenkinsci/docker-plugin#1103 describes the test automation failure that happens with httpclient 5.4. jenkinsci#29 notes that there may have been a breaking change in httpclient 5.4. jenkinsci#59 also notes that there is an issue in httpclient 5.4.
Pending fix of jenkinsci#59
The revert of httpclient 5.4 has been released as 5.4-124.v31e2987e48f4. The version is called 5.4-124.v31e2987e48f4 but contains httpclient 5.3.1 I hope to investigate more deeply tomorrow and create an upstream issue so that the httpclient 5.4 maintainers can investigate further. |
|
I did some more investigation and found that the issue was likely introduced by apache/httpcomponents-client#540 I'm still not entirely convinced we are facing a regression in HttpClient but will try creating a MRE that preferably does not require Docker. With that, raising and hopefully fixing the issue should be easier. |
|
I have filed HTTPCLIENT-2348 upstream |
|
Okay, that’s embarrassing for me - I was unable to reproduce the test failure on my machine and went in the wrong direction from there on. Thanks for your effort! |
|
I have filed docker-java/docker-java#2363 to track this upgrade in |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Ubuntu LTS
Reproduction steps
unix:///var/run/docker.sockExpected Results
Connection to local Docker API.
Actual Results
Anything else?
After downgrading to Version
apache-httpcomponents-client-5-api:5.3.1-117.v4d95117cd34fits working again.Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: