[
https://issues.apache.org/jira/browse/AMBARI-14360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055209#comment-15055209
]
Hadoop QA commented on AMBARI-14360:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12777365/AMBARI-14360.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 1 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/4587//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4587//console
This message is automatically generated.
> Ambari API: request tasks are not returned via API
> --------------------------------------------------
>
> Key: AMBARI-14360
> URL: https://issues.apache.org/jira/browse/AMBARI-14360
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Priority: Critical
> Fix For: 2.2.1
>
> Attachments: AMBARI-14360.patch
>
>
> In case of provisioning a cluster via Blueprints API, tasks are not returned
> for Topology Logical Request.
> In the below example, you can see that the request specifies that there are
> 40 tasks and 40 completed tasks but there are no task sub-resources returned.
> {code}
> GET http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1
> {code}
> returns
> {code}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1";,
> "Requests" : {
> "aborted_task_count" : 0,
> "cluster_name" : "c1",
> "completed_task_count" : 40,
> "create_time" : 1448413081566,
> "end_time" : -1,
> "exclusive" : false,
> "failed_task_count" : 0,
> "id" : 1,
> "inputs" : null,
> "operation_level" : null,
> "progress_percent" : 100.0,
> "queued_task_count" : 0,
> "request_context" : "Logical Request: Provision Cluster 'c1'",
> "request_schedule" : null,
> "request_status" : "COMPLETED",
> "resource_filters" : null,
> "start_time" : -1,
> "task_count" : 40,
> "timed_out_task_count" : 0,
> "type" : null
> },
> "stages" : [
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1/stages/1";,
> "Stage" : {
> "cluster_name" : "c1",
> "request_id" : 1,
> "stage_id" : 1
> }
> }
> ],
> "tasks" : [ ]
> }
> {code}
> When asking specifically for the tasks resource, it returns an empty set even
> though there are actually 40 tasks associated with the request.
> {code}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/requests/1/tasks";,
> "items" : [ ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
