[
https://issues.apache.org/jira/browse/AMBARI-15532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209982#comment-15209982
]
Hadoop QA commented on AMBARI-15532:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12794996/AMBARI-15532.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/5999//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5999//console
This message is automatically generated.
> ambari-web allows to delete a service that has running processes
> ----------------------------------------------------------------
>
> Key: AMBARI-15532
> URL: https://issues.apache.org/jira/browse/AMBARI-15532
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15532.patch
>
>
> # Navigate to Hive Service summary page
> # Stop Webhcat server
> # Delete Hive Service
> *Actual behavior:* As one master component of Hive is in installed state
> which brings hive service in installed state, ambari-web considers this to be
> a valid siatuation and executes delete API call on Hive service resource
> *Expected behavior:* Instead of relying on service state, state of all master
> and slave component of a service should be checked and if any of them is in
> started state then user should be asked to stop the master component first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
