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 6181D186D0 for ; Mon, 11 Jan 2016 21:32:40 +0000 (UTC) Received: (qmail 81970 invoked by uid 500); 11 Jan 2016 21:32:40 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 81927 invoked by uid 500); 11 Jan 2016 21:32:40 -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 81795 invoked by uid 99); 11 Jan 2016 21:32:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2016 21:32:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EF0E62C1F58 for ; Mon, 11 Jan 2016 21:32:39 +0000 (UTC) Date: Mon, 11 Jan 2016 21:32:39 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-14617) Alerts sorting on status column in ascending order does not work properly sometimes 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-14617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092719#comment-15092719 ] Hadoop QA commented on AMBARI-14617: ------------------------------------ {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12781641/AMBARI-14617.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {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-web. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/4852//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4852//console This message is automatically generated. > Alerts sorting on status column in ascending order does not work properly sometimes > ----------------------------------------------------------------------------------- > > Key: AMBARI-14617 > URL: https://issues.apache.org/jira/browse/AMBARI-14617 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.2.1 > Reporter: Aleksandr Kovalenko > Assignee: Aleksandr Kovalenko > Priority: Critical > Fix For: 2.2.1 > > Attachments: AMBARI-14617.patch > > > 1. Deploy ambari cluster with all services > 2. stop some services to have some critical alerts > 3. Go to alerts page and sort status column in descending order. verify order is correct > 4. Sort status column in ascending order . Verify order is correct. > Expected: Alerts should be in correct order > Actual: Alerts are not in proper order. > NOTE: this issue happens intermittently but has been seen quite frequently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)