[
https://issues.apache.org/jira/browse/AMBARI-18319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467597#comment-15467597
]
Hadoop QA commented on AMBARI-18319:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12827196/AMBARI-18319.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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8582//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8582//console
This message is automatically generated.
> Next button on Customize Services page is in invalid state after canceling
> move to next page
> --------------------------------------------------------------------------------------------
>
> Key: AMBARI-18319
> URL: https://issues.apache.org/jira/browse/AMBARI-18319
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18319.patch
>
>
> Steps:
> # Go to Customize Services page.
> # Select any custom DB fot Hive service and click Next.
> # Was appeared "Database Connectivity Warning", cancel moving to next step.
> Result: Customize Services page still opened, but Next button has loading
> spinner and is inactive. After page reload button works fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
