Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 009B717344 for ; Sat, 8 Nov 2014 02:48:34 +0000 (UTC) Received: (qmail 41289 invoked by uid 500); 8 Nov 2014 02:48:34 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 41260 invoked by uid 500); 8 Nov 2014 02:48:33 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 41246 invoked by uid 99); 8 Nov 2014 02:48:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Nov 2014 02:48:33 +0000 Date: Sat, 8 Nov 2014 02:48:33 +0000 (UTC) From: "John Speidel (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-7665) Dashboard doesn't display after installing from BP MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Speidel resolved AMBARI-7665. ---------------------------------- Resolution: Fixed had been fixed for a while > Dashboard doesn't display after installing from BP > -------------------------------------------------- > > Key: AMBARI-7665 > URL: https://issues.apache.org/jira/browse/AMBARI-7665 > Project: Ambari > Issue Type: Bug > Components: blueprints > Affects Versions: 1.7.0 > Reporter: John Speidel > Assignee: John Speidel > Fix For: 1.7.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > After installing a cluster via a blueprint, the Ambari dashboard doesn't display. Instead of the dashboard, the install cluster wizard is displayed. This is caused by a recent change in how the UI keeps track of cluster state and the blueprints processor wasn't updated to account for these changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)