[
https://issues.apache.org/jira/browse/AMBARI-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536231#comment-14536231
]
Hadoop QA commented on AMBARI-11039:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12731675/AMBARI-11039.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2673//console
This message is automatically generated.
> RU wrong version of tez.tar.gz uploaded to HDFS
> -----------------------------------------------
>
> Key: AMBARI-11039
> URL: https://issues.apache.org/jira/browse/AMBARI-11039
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.0.1
>
> Attachments: AMBARI-11039.patch
>
>
> Summary: Customers with Ambari 2.0.0 that performed an RU from say HDP
> 2.2.0.0 to 2.2.4.2 will not have the correct version of tez.tar.gz uploaded
> to HDFS.
> Details: During HiveServer2 Restart in RU, it copied to wrong tez.tar.gz to
> HDFS (because the symlink in /usr/hdp/current/tez is still pointing to the
> old version at this time).
> The reason why Service Checks pass is that these tarballs are compatible
> enough with each other. However, during RU from 2.2.* to 2.3.*, this is
> likely to break.
> Impact: Applications that depend on this tarball (Pig, Tez, Hive) will be
> running with older classes. This does not appear to be breaking in HDP 2.2,
> otherwise customers would have reported it. However, it certainly does have
> to be fixed in Ambari 2.1.0 because tez.tar.gz has more significant changes
> and does encounter a version incompatibility error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
