Return-Path: X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1259D18EF0 for ; Wed, 9 Mar 2016 04:46:41 +0000 (UTC) Received: (qmail 536 invoked by uid 500); 9 Mar 2016 04:46:41 -0000 Delivered-To: apmail-ambari-issues-archive@ambari.apache.org Received: (qmail 507 invoked by uid 500); 9 Mar 2016 04:46:40 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 490 invoked by uid 99); 9 Mar 2016 04:46:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Mar 2016 04:46:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C192C2C044E for ; Wed, 9 Mar 2016 04:46:40 +0000 (UTC) Date: Wed, 9 Mar 2016 04:46:40 +0000 (UTC) From: "Alejandro Fernandez (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-15330) Bubble up errors during RU/EU MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-15330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-15330: ----------------------------------------- Attachment: (was: AMBARI-15330.trunk.patch) > Bubble up errors during RU/EU > ----------------------------- > > Key: AMBARI-15330 > URL: https://issues.apache.org/jira/browse/AMBARI-15330 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Alejandro Fernandez > Assignee: Alejandro Fernandez > Fix For: 2.4.0 > > Attachments: AMBARI-15330.trunk.patch > > > During RU/EU, need a way to bubble up an error of the current item that failed. This is useful to quickly get a human-readable error that others UIs can quickly retrieve. > It can print a human-readable error, plus stdout and stderr. > This would become part of the upgrade endpoint. e.g, > api/v1/clusters/$name/upgrade_summary/$request_id > {code} > { > attempt_cnt: 1, > cluster_name: "c1", > request_id: 1, > fail_reason: "Failed calling RESTART ZOOKEEPER/ZOOKEEPER_SERVER on host c6401.ambari.apache.org", > // Notice that the rest are inherited from the failed task if it exists. > command: "CUSTOM_COMMAND", > command_detail: "RESTART ZOOKEEPER/ZOOKEEPER_SERVER", > custom_command_name: "RESTART", > end_time: -1, > error_log: "/var/lib/ambari-agent/data/errors-1234.txt", > exit_code: 1, > host_name: "c6401.ambari.apache.org", > id: 1234, > output_log: "/var/lib/ambari-agent/data/output-1234.txt", > role: "ZOOKEEPER_SERVER", > stage_id: 1, > start_time: 123456789, > status: "HOLDING_FAILED", > stdout: "", > stderr: "" > } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)