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 9B17217290 for ; Fri, 10 Oct 2014 15:01:34 +0000 (UTC) Received: (qmail 45460 invoked by uid 500); 10 Oct 2014 15:01:34 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 45429 invoked by uid 500); 10 Oct 2014 15:01:34 -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 45417 invoked by uid 99); 10 Oct 2014 15:01:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2014 15:01:34 +0000 Date: Fri, 10 Oct 2014 15:01:33 +0000 (UTC) From: "Anthony Penniston (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-7727) Stuck progress bar on loading dashboard 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-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Penniston updated AMBARI-7727: -------------------------------------- Attachment: screenshot-1.png > Stuck progress bar on loading dashboard > --------------------------------------- > > Key: AMBARI-7727 > URL: https://issues.apache.org/jira/browse/AMBARI-7727 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 1.7.0 > Reporter: Anthony Penniston > Assignee: vitthal (Suhas) Gogate > Attachments: Screen Shot 2014-10-10 at 10.37.54 AM.png > > > On loading the dashboard after creating a new cluster, sometimes the progress bar simply hangs and the dashboard never loads. > Looking at the console log, this is due to an Error 400: > { "status" : 400, "message" : "The properties [legacy_alerts/summary] specified in the request or predicate are not supported for the resource type Service."} > removing the legacy_alerts/summary query param from the request made in updateServices in update_controller.js appears to fix the problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)