Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 14 Jul 2015 14:41:14 +0000 (UTC)
From: "Robert Nettleton (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12840798.1435316154000.182716.1436884874826@Atlassian.JIRA>
In-Reply-To: <JIRA.12840798.1435316154000@Atlassian.JIRA>
References: <JIRA.12840798.1435316154000@Atlassian.JIRA>
 <JIRA.12840798.1435316154055@arcas>
Subject: [jira] [Updated] (AMBARI-12161) Perf Cluster: Repo Version install
 stuck in INSTALLING state
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Nettleton updated AMBARI-12161:
--------------------------------------
    Fix Version/s:     (was: 2.1.0)
                   2.1.1

> Perf Cluster: Repo Version install stuck in INSTALLING state
> ------------------------------------------------------------
>
>                 Key: AMBARI-12161
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12161
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.1
>
>         Attachments: AMBARI-12161.patch
>
>
> *Steps to reproduce:*
> # Register Repo Version
> # Start Install Version
> # Wait till the request will be completed
> *Actual Result:*
> Request successfully completed, but Stack Version of host still has INSTALLING status and so entire stack version has status INSTALLING
> Looks like it is an issue with how repo version is added. I always include build number into repo version name, and guys seem to skip it. Both workflows are correct, but in latter case there is a corner case on hosts without versionable components (and /usr/hdp dir)


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