Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 27 Jan 2015 22:01:34 +0000 (UTC)
From: "Alejandro Fernandez (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12770259.1422328934000.188692.1422396094922@Atlassian.JIRA>
In-Reply-To: <JIRA.12770259.1422328934000@Atlassian.JIRA>
References: <JIRA.12770259.1422328934000@Atlassian.JIRA>
 <JIRA.12770259.1422328934819@arcas>
Subject: [jira] [Updated] (AMBARI-9340) RU - Cluster install did not
 transition cluster_version to CURRENT because host has only AMS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Fernandez updated AMBARI-9340:
----------------------------------------
    Attachment:     (was: AMBARI-9340.patch)

> RU - Cluster install did not transition cluster_version to CURRENT because host has only AMS
> --------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-9340
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9340
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.0.0
>
>
> New cluster install through the Install Wizard correctly transitioned all of the host_versions into CURRENT, but did not propagate the changes to the cluster_version, which stayed stuck on UPGRADING, because one host only had AMS, so it could not create a host_version record.


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