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-14734) RU/EU, add PreCheck to prevent starting upgrade if a previous upgrade skipped the step Save DB State
Date Thu, 21 Jan 2016 15:04:39 GMT

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

Hadoop QA commented on AMBARI-14734:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12783478/AMBARI-14734.trunk.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 2 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/5006//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5006//console

This message is automatically generated.

> RU/EU, add PreCheck to prevent starting upgrade if a previous upgrade skipped the step
Save DB State
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14734
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14734
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.2.1
>
>         Attachments: AMBARI-14734.trunk.patch
>
>
> Customer quit on Save Cluster State and finalized the upgrade later without running "ambari-server
set-current --cluster-name=$CLUSTERNAME --version-display-name=$VERSION_NAME".
> Next upgrade from 2.3.2 to 2.3.4 deleted configs from desired stack 2.2
> STR:
> RU/EU HDP 2.2->2.3 (don't Save Cluster State so that desired stack remains on 2.2)
> RU/EU from HDP 2.3.0.0-2.3.4.0 and Downgrade (this will remove the configs for the desired
stack, which is still 2.2!)
> Need stronger prechecks to prevent starting RU/EU if the previous upgrade did not have
a downgrade path and the "Save Cluster State" step is not COMPLETED.



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

Mime
View raw message