[jira] [Created] (AMBARI-5757) Agent can not download modified stack files if wrong http_proxy is set up

["Dmitry Lysnichenko (JIRA)" <ji...@apache.org>]

Dmitry Lysnichenko created AMBARI-5757:
------------------------------------------

             Summary: Agent can not download modified stack files if wrong http_proxy is set up
                 Key: AMBARI-5757
                 URL: https://issues.apache.org/jira/browse/AMBARI-5757
             Project: Ambari
          Issue Type: Task
          Components: agent
    Affects Versions: 1.6.0
            Reporter: Dmitry Lysnichenko
            Assignee: Dmitry Lysnichenko
             Fix For: 1.7.0


Agent can not download (update) modified stack scripts/templates from the server if there is a problem with proxy configuration. That is because python's urllib2.urlopen() function also tries to make use of proxies.
>From the docs:
{code}
The urlopen() function works transparently with proxies which do not require authentication. In a Unix or Windows environment, set the http_proxy, or ftp_proxy environment variables to a URL that identifies the proxy server before starting the Python interpreter
{code}
I've created a separate jira to be able to provide fix for BUG-17737 as soon as possible

STR:
# Create 2-node cluster
# Install server&agent
# Define wrong proxy on both hosts e.g. 
{code}
export http_proxy="http://8.8.8.8:23"
{code}
# Restart ambari-agent from the same shell to make use of this proxy
# Try modifying some service scripts at ambari-server
# Restart ambari-server
# Ambari-agent should download updated scripts to a local cache (during installation of the relevant stack), but he can not do that due to proxy settings. There are error messages at log about that. 

Possible solution:  Disable proxy settings when creating urllib2 opener (at FileCache)
The same urllib2 is used at Controller, so agent might not be able to connect to ambari-server at all with wrong proxy settings. But I did not notice such behaviour for some reason



--
This message was sent by Atlassian JIRA
(v6.2#6252)