You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/07/10 21:59:00 UTC
[jira] [Commented] (AMBARI-21439) Hive/MapRed2 restart fails after
Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081237#comment-16081237 ]
Hadoop QA commented on AMBARI-21439:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12876504/AMBARI-21439.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/11766//console
This message is automatically generated.
> Hive/MapRed2 restart fails after Ambari upgrade
> -----------------------------------------------
>
> Key: AMBARI-21439
> URL: https://issues.apache.org/jira/browse/AMBARI-21439
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: branch-feature-AMBARI-21348
> Reporter: Di Li
> Assignee: Di Li
> Fix For: branch-feature-AMBARI-21348
>
> Attachments: AMBARI-21439.patch
>
>
> The BI stacks copied to HDP uses old copy_to_hdfs Python API from ambari-common that uses the now-renamed "host_system_prepped", It's renamed to "skip".
> This issue only happens on BI 4.2 GA clusters. References to the copy_to_hdfs API need to use the new parameter - skip
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)