ambari-dev 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-10739) ConfigureAction Must Take Into Account Stack Versions
Date Fri, 24 Apr 2015 22:36:38 GMT

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

Hadoop QA commented on AMBARI-10739:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12728026/AMBARI-10739.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2512//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2512//console

This message is automatically generated.

> ConfigureAction Must Take Into Account Stack Versions
> -----------------------------------------------------
>
>                 Key: AMBARI-10739
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10739
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10739.patch
>
>
> The {{ConfigureAction}} that is used in the rolling upgrade process blindly creates new
configurations for every single change that is listed in the upgrade pack. This needs to change
in two fundamental ways:
> - When upgrading or downgrading within a stack version (hdp-2.2.x.x to hdp-2.2.y.y),
before making a new configuration with the value from the upgrade pack, compare the value
to the current value. If they are the same, do no work
> - When upgrading across stack versions (hdp-2.2 to hdp-2.3), new configurations are already
being created. There is no need to create new configurations since the upgrade has already
done this. The desired configurations should simply be modified with the new values.



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

Mime
View raw message