ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21999) Always Take Target Read-Only Properties On Stack Upgrade
Date Tue, 19 Sep 2017 22:21:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-21999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172438#comment-16172438
] 

Hadoop QA commented on AMBARI-21999:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12887950/AMBARI-21999.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/12290//console

This message is automatically generated.

> Always Take Target Read-Only Properties On Stack Upgrade
> --------------------------------------------------------
>
>                 Key: AMBARI-21999
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21999
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21999.patch
>
>
> STR:
> - Install a stack, such as HDP 2.3
> - Modify the {{cluster-env/stack_features}} structure
> - Upgrade to HDP 2.6
> The auto-merge which happens can't properly merge {{cluster-env/stack_features}} since
it has deviated from the stock values of HDP 2.3. This is dangerous since this is needed for
proper operation.
> Because it's defined as a read-only value, we should be able to detect this in the auto-merge
fro the upgrade and force it to the new stack's default value...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message