[ 
https://issues.apache.org/jira/browse/AMBARI-12547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642486#comment-14642486
 ] 

Hadoop QA commented on AMBARI-12547:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12747295/AMBARI-12547.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 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/3475//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3475//console

This message is automatically generated.

> There's no easy way to start all host components on a host via the API
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-12547
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12547
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-12547.patch
>
>
> While issuing the API to try to start all host components on c6401:
> {code}
> curl --user admin:admin  -H  "X-Requested-By: ambari" -i -X PUT -d 
> '{"HostRoles":{"state":"STARTED"}}' http://`hostname 
> -f`:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org/host_components
> {code}
> *Response*
> {code}
> {
>   "status" : 400,
>   "message" : "java.lang.IllegalArgumentException: Invalid desired state for 
> a client component"
> }
> {code}
> *Note:* There was no serviceComponent name specified but the API treats this 
> scenario as start request has been made on client component
> Currently, you have to explicitly specify all the host components that you 
> wish to start.  This is very cumbersome and not user friendly.
> We also cannot do something like 
> /api/v1/clusters/c1/hosts/c6401.ambari.apache.org/host_components?HostRoles/is_client!=true



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to