[
https://issues.apache.org/jira/browse/AMBARI-12687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679932#comment-14679932
]
Hadoop QA commented on AMBARI-12687:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749559/AMBARI-12687.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3553//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3553//console
This message is automatically generated.
> Incorrect behavior of paging on Alerts page
> -------------------------------------------
>
> Key: AMBARI-12687
> URL: https://issues.apache.org/jira/browse/AMBARI-12687
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.1
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 2.2.0
>
> Attachments: AMBARI-12687.patch
>
>
> Steps:
> # Was deployed cluster with almost all services. Alerts page contains 71
> alerts. Paging is 10 by default.
> # Go to second page. (alerts 11-21).
> # Choose paging 100.
> Result: are displayed alerts 10-71, although can be displayed all alerts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
