nailgun-agent is unreachable if we set http_proxy on target nodes.

[Chandra]

Hi,

if we use http_proxy on target nodes then nailgun-agent is not reachable to fule node. this cause fuel node to show target nodes as offline.

nailgun-agent.log

/usr/lib/ruby/1.9.1/openssl/buffering.rb:53:in `sysread': execution expired (HTTPClient::ConnectTimeoutError)
 from /usr/lib/ruby/1.9.1/openssl/buffering.rb:53:in `sysread'
 from /usr/lib/ruby/1.9.1/openssl/buffering.rb:53:in `fill_rbuff'
 from /usr/lib/ruby/1.9.1/openssl/buffering.rb:200:in `gets'
 from /usr/lib/ruby/vendor_ruby/httpclient/session.rb:352:in `gets'
 from /usr/lib/ruby/vendor_ruby/httpclient/session.rb:879:in `block in parse_header'
 from /usr/lib/ruby/1.9.1/timeout.rb:69:in `timeout'
 from /usr/lib/ruby/1.9.1/timeout.rb:100:in `timeout'
 from /usr/lib/ruby/vendor_ruby/httpclient/session.rb:875:in `parse_header'
 from /usr/lib/ruby/vendor_ruby/httpclient/session.rb:836:in `connect_ssl_proxy'
 from /usr/lib/ruby/vendor_ruby/httpclient/session.rb:758:in `block in connect'
 from /usr/lib/ruby/vendor_ruby/httpclient/session.rb:751:in `connect'
 from /usr/lib/ruby/vendor_ruby/httpclient/session.rb:609:in `query'
 from /usr/lib/ruby/vendor_ruby/httpclient/session.rb:164:in `query'
 from /usr/lib/ruby/vendor_ruby/httpclient.rb:1083:in `do_get_block'
 from /usr/lib/ruby/vendor_ruby/httpclient.rb:887:in `block in do_request'
 from /usr/lib/ruby/vendor_ruby/httpclient.rb:981:in `protect_keep_alive_disconnected'
 from /usr/lib/ruby/vendor_ruby/httpclient.rb:886:in `do_request'
 from /usr/lib/ruby/vendor_ruby/httpclient.rb:774:in `request'
 from /usr/lib/ruby/vendor_ruby/httpclient.rb:677:in `get'
 from /usr/bin/nailgun-agent:155:in `get_scheme_and_port'
 from /usr/bin/nailgun-agent:145:in `initialize'
 from /usr/bin/nailgun-agent:861:in `new'
 from /usr/bin/nailgun-agent:861:in `<main>'

[Dmitry Guryanov (dguryanov)]

Hello, Chandu! Could you, please, write, how exactly did you set http_proxy?

[Arthur Svechnikov (asvechnikov)]

Probably no_proxy should be configured as well

[Chandra (reddydodda)]

Hi,

i configured no_proxy also. but the result is same.

[Chandra (reddydodda)]

here is my proxy settings in /etc/environment

export http_proxy='http://192.168.96.6:88'
export https_proxy='http://192.168.96.6:88'
export ftp_proxy='http://192.168.96.6.88'
export no_proxy='192.168.96.0/22,192.168.92.0/24,192.168.93.0/24,192.168.94.0/24,192.168.95.0/24,localhost,127.0.0.0/8,127.0.1.1'
export NO_PROXY=$no_proxy

[Maksim Malchuk (mmalchuk)]

We don't backport medium bugs due to HCF.

[Roman Prykhodchenko (romcheg)]

IIRC, no_proxy cannot contain networks.

[Roman Prykhodchenko (romcheg)]

Chandu, could you please try to specify specific IP addresses in no_proxy? According to the documentation no_proxyshould contain a comma-separated list of domain extensions proxy should not be used for.

You can use this thread on stack exchange for more information:
http://unix.stackexchange.com/questions/23452/set-a-network-range-in-the-no-proxy-environment-variable

[Roman Prykhodchenko (romcheg)]

Please let us know if that solution resolved the issue

[Roman Prykhodchenko (romcheg)]

I refered to the official ruby documentation, it's indeed impossible to set CIDR to no_proxy: http://www.rubydoc.info/gems/httpclient/2.1.5.2/HTTPClient#no_proxy-instance_method