[
https://issues.apache.org/jira/browse/AMBARI-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14637907#comment-14637907
]
Hadoop QA commented on AMBARI-12506:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746625/AMBARI-12506.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 4 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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3448//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3448//console
This message is automatically generated.
> Server Side stages and tasks should not need server name
> --------------------------------------------------------
>
> Key: AMBARI-12506
> URL: https://issues.apache.org/jira/browse/AMBARI-12506
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Nate Cole
> Assignee: Nate Cole
> Fix For: 2.2.0
>
> Attachments: AMBARI-12506.patch
>
>
> Server side actions in general are assigned to the current Ambari host. This
> fails when the server is NOT installed on a host in the cluster due to the FK
> of host_role_command to host.
> Issue discovered while trying to work in the development environment when
> creating server side actions. The hackaround was to pick a cluster host
> which is VERY wrong (but is working).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
