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 E18CE17E0C for ; Thu, 23 Oct 2014 13:02:34 +0000 (UTC) Received: (qmail 86247 invoked by uid 500); 23 Oct 2014 13:02:34 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 86210 invoked by uid 500); 23 Oct 2014 13:02: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 86197 invoked by uid 99); 23 Oct 2014 13:02:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Oct 2014 13:02:33 +0000 Date: Thu, 23 Oct 2014 13:02:33 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-7920) Unable to go to Manage Ambari from Installer step9 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-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181302#comment-14181302 ] Hadoop QA commented on AMBARI-7920: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12676573/AMBARI-7920_branch-1.7.0.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-admin. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/316//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/316//console This message is automatically generated. > Unable to go to Manage Ambari from Installer step9 > -------------------------------------------------- > > Key: AMBARI-7920 > URL: https://issues.apache.org/jira/browse/AMBARI-7920 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web > Affects Versions: 1.7.0 > Reporter: Aleksandr Kovalenko > Assignee: Aleksandr Kovalenko > Fix For: 1.7.0 > > Attachments: AMBARI-7920.patch, AMBARI-7920_branch-1.7.0.patch > > > During install user is unable to go to Manage Ambari. We should either provide this action or hide/disable "Manage Ambari" option in menu. Also if user will have ability to go to the Manage Ambari during install, we will get another issue: rename cluster button will be enabled and user can rename cluster right during install. It will cause issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)