|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Not sure if this helps or not, but I faced a similar issue with this network topology:
The CLI worked fine over the master node's private ip address, e.g. `java -jar jenkins-cli.jar -s http://192.168.2.10:8080/ help`
The CLI failed on any slave in either LAN when using the master node's public ip address, e.g., `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` raised the error "SEVERE: I/O error in channel Chunked connection"
The problem was ultimately the software firewall in the OpenStack cluster that only applied to the floating IPs (e.g., 10.166.140.0/24).
The resolution was to allowing UDP ingress on ports 1024-65535 and TCP ingress on ports 1024-65535 for my slaves public IPs (10.21.26.0/24 and 10.166.140.0/24). Executing `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` then worked as expected on all slaves in both data centers.
My $0.02 - there is some complex networking for CLI connections: there seems to be ICMP, UDP, and TCP in use at the same time, along with random (JNLP?) ports on the server. The CLI client could use connectivity checks and/or clearcut error messages to better explain when connectivity fails for a specific protocol/address/port.