Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 14 Jan 2015 21:46:34 +0000 (UTC)
From: "Alejandro Fernandez (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12766613.1420855681000.85474.1421271994856@Atlassian.JIRA>
In-Reply-To: <JIRA.12766613.1420855681000@Atlassian.JIRA>
References: <JIRA.12766613.1420855681000@Atlassian.JIRA>
 <JIRA.12766613.1420855681165@arcas>
Subject: [jira] [Updated] (AMBARI-9081) Rolling Upgrades: clients do not
 send information about their version on restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-9081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Fernandez updated AMBARI-9081:
----------------------------------------
    Attachment: AMBARI-9081.patch

> Rolling Upgrades: clients do not send information about their version on restart
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-9081
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9081
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9081.patch
>
>
> See AMBARI-8995, after that changes master components have their version in the results of START command, but clients do not execute this command and thus it's not possible to track their new version. As the result some components of the cluster remain in non upgraded state and it prevents from setting cluster to upgraded state and finalize upgrade.


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