[
https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934400#comment-14934400
]
Hadoop QA commented on AMBARI-13238:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12764106/AMBARI-13238.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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3872//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3872//console
This message is automatically generated.
> MySQL service check needs to be more robust
> -------------------------------------------
>
> Key: AMBARI-13238
> URL: https://issues.apache.org/jira/browse/AMBARI-13238
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0, 2.1.0
> Reporter: Thomas Friedrich
> Assignee: Thomas Friedrich
> Priority: Minor
> Attachments: AMBARI-13238.patch
>
>
> The mysql service check in mysql_service.py simply checks for the existence
> of a mysqld process. If an unrelated mysqld service is running on the same
> node and Hive is configured to run with a MySQL db, the Hive start action
> won't start the MySQL server instance and the metastore connection fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
