[
https://issues.apache.org/jira/browse/AMBARI-21859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148845#comment-16148845
]
Hadoop QA commented on AMBARI-21859:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884654/AMBARI-21859_trunk.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 2 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12116//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12116//console
This message is automatically generated.
> Pre-upgrade check option well before starting upgrade process
> -------------------------------------------------------------
>
> Key: AMBARI-21859
> URL: https://issues.apache.org/jira/browse/AMBARI-21859
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-web
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21859_trunk.patch, Screen Shot 2017-08-28 at
> 4.22.28 PM.png
>
>
> Currently Ambari does pre-ugprade checks once user clicks on the Upgrade.
> some times these pre-upgrade check resolution is taking lot of time because
> of many different issues.
> providing pre-check (may be drop down) option will be useful for the
> customers to perform checks well before the down time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
