You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2015/06/03 07:26:49 UTC

[jira] [Created] (AMBARI-11640) During initial Stack Install, tarballs will not be copied to HDFS because the current_version is not yet known

Alejandro Fernandez created AMBARI-11640:
--------------------------------------------

             Summary: During initial Stack Install, tarballs will not be copied to HDFS because the current_version is not yet known
                 Key: AMBARI-11640
                 URL: https://issues.apache.org/jira/browse/AMBARI-11640
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.1.0
            Reporter: Alejandro Fernandez
            Assignee: Alejandro Fernandez
             Fix For: 2.1.0


During Install of services, Ambari doesn't yet know about the current_version, so it doesn't get passed to command-###.json, for this reason, the copying of tarballs fails.

The workaround is to start all services so that the CURRENT version exists, and then rerun a HiveServer2 Start, Spark History Server2, or Tez Service Check.

The fix will be to detect if params.current_version is None, and if so, call hdp-select versions, and use the value if only one version number is reported.
Also, HiveServer2 Start needs to copy the tez tarball.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)