hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Singh (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-12988) upgrading the HDP stack through Ambari (from 2.3 to 2.4)
Date Thu, 31 Mar 2016 23:28:25 GMT
Arun Singh created HADOOP-12988:

             Summary: upgrading the HDP stack through Ambari (from 2.3 to 2.4)
                 Key: HADOOP-12988
                 URL: https://issues.apache.org/jira/browse/HADOOP-12988
             Project: Hadoop Common
          Issue Type: Bug
         Environment: SLES11 SP4
            Reporter: Arun Singh

 - Issue 3: When upgrading the HDP stack through Ambari (from 2.3 to 2.4), at some point a
YARN smokescreen test is performed. This smoke screen test fails, as it is trying to call
an API command using curl with the --negotiate option. The problem is that on SUSE 11, the
version of curl does not ship with one that understands "--negotiate", grinding the whole
upgrade process to a halt. 
There are quite a few files in Ambari where this seems to be the case, although I personally
only encountered it during the YARN component: 
    Execute(format("curl -s -o /dev/null -w'%{{http_code}}' --negotiate -u: -k {ranger_external_url}/login.jsp
| grep 200"),
    Execute(format("curl -s -o /dev/null -w'%{{http_code}}' --negotiate -u: -khttp://{spark_history_server_host}:{spark_history_ui_port}
| grep 200"),
    get_app_info_cmd = "curl --negotiate -u : -ksL --connect-timeout " + CURL_CONNECTION_TIMEOUT
+ " " + info_app_url
    smoke_cmd = format('curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o
/dev/null -w "%{{http_code}}"http://{metadata_host}:{metadata_port}/')
    cmd="${kinitcmd}curl --negotiate -u : -s -w 'http_code <%{http_code}>'  $ttonurl/status
    cmd="${kinitcmd}curl --negotiate -u : -s -w 'http_code <%{http_code}>'  $ttonurl/status?user.name=$smoke_test_user
    cmd="${kinitcmd}curl --negotiate -u : -s -w 'http_code <%{http_code}>' -d  \@${destdir}/show_db.post.txt
 $ttonurl/ddl 2>&1"

For example, in this file: /var/lib/ambari-server/resources/common-services/YARN/
You will see the code as:
for rm_webapp_address in params.rm_webapp_addresses_list:
      info_app_url = params.scheme + "://" + rm_webapp_address + "/ws/v1/cluster/apps/" +

      get_app_info_cmd = "curl --negotiate -u : -ksL --connect-timeout " + CURL_CONNECTION_TIMEOUT
+ " " + info_app_url

      return_code, stdout, _ = get_user_call_output(get_app_info_cmd,
There is no code checking whether RHEL vs SUSE, to run the correct usage of curl. Or alternatively,
there is no code to check for version of curl, and run a "deprecated" version of the command
as a fallback should it detect that the installed curl does not support --negotiate. This
is just blindly assuming to work on SUSE 11 (or any version of curl). 
Information about the curl installed on the system: 
hdplab02:~ # curl -V 
curl 7.45.0 (x86_64-pc-linux-gnu) libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8 
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps
telnet tftp 
Features: IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP UnixSockets

This message was sent by Atlassian JIRA

View raw message