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 2016/03/11 00:49:40 UTC

[jira] [Commented] (AMBARI-15374) Check To Ensure That All Components Are On The Same Version Before Upgrading

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

Hadoop QA commented on AMBARI-15374:
------------------------------------

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

This message is automatically generated.

> Check To Ensure That All Components Are On The Same Version Before Upgrading
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-15374
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15374
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.2.2
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15374.patch
>
>
> Before beginning an upgrade, there should be a pre-upgrade check which ensures that all known, versionable components are reporting the same version. If any host component is reporting a version which does not match the current repository version, then a warning should be produced. The warning should provide information on the failed components, the expected version, and the version they are reporting.
> Note that this is only for Ambari 2.2.x; Ambari 2.4.0 uses a new workflow for how versions are recorded and stored during upgrade and does not need this.
> There are two ways to go about this:
> - Compare each service component host version to that of the {{CURRENT}} {{repo_version}}. However, there could be cases where the {{repo_version}} has not been calculated yet.
> - Compare each service component host version to each other.



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