ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13064) Provide Summary Of Skipped Failures During Upgrade
Date Fri, 11 Sep 2015 03:24:45 GMT

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

Hadoop QA commented on AMBARI-13064:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12755238/AMBARI-13064.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3766//console

This message is automatically generated.

> Provide Summary Of Skipped Failures During Upgrade
> --------------------------------------------------
>
>                 Key: AMBARI-13064
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13064
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-13064.patch
>
>
> There should be a new server-side action created which will be inserted into the upgrade
orchestration after core slaves has completed. This action will be marked "COMPLETED" automatically
if there are no failures detected. In the event of 1 or more failures, this action will transition
into the HOLDING state. 
> Each of the failures will be displayed in the SKIPPED_FAILED state along with their host
name, standard output and standard error. The only option presented to the user in this state
should be to ignore and proceed which would mark the summary task as COMPLETED. 
> Example Summary:
> {code}
> {
>   "href": "http://localhost:8080/api/v1/clusters/c1/upgrades/12/upgrade_groups/4/upgrade_items/11/tasks/215",
>   "Tasks": {
>     "attempt_cnt": 1,
>     "cluster_name": "c1",
>     "command": "EXECUTE",
>     "command_detail": "Verifying Skipped Failures",
>     "custom_command_name": "org.apache.ambari.server.serveraction.upgrades.AutoSkipFailedSummaryAction",
>     "end_time": -1,
>     "error_log": "errors-215.txt",
>     "exit_code": 0,
>     "host_name": null,
>     "id": 215,
>     "output_log": "output-215.txt",
>     "request_id": 12,
>     "role": "AMBARI_SERVER_ACTION",
>     "stage_id": 11,
>     "start_time": 1441907533753,
>     "status": "HOLDING",
>     "stderr": "The following steps failed and were automatically skipped:\nZOOKEEPER_CLIENT
on c6403.ambari.apache.org: RESTART ZOOKEEPER/ZOOKEEPER_CLIENT\n",
>     "stdout": "There were 1 skipped failure(s) that must be addressed before you can
proceed. Please resolve each failure before continuing with the upgrade.",
>     "structured_out": {
>       "c6403.ambari.apache.org": {
>         "error_log": "/var/lib/ambari-agent/data/errors-214.txt",
>         "exit_code": 1,
>         "id": 214,
>         "output_log": "/var/lib/ambari-agent/data/output-214.txt",
>         "stderr": "some stderr",
>         "stdout": "some stdout"
>       }
>     }
>   }
> }
> {code}



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

Mime
View raw message