[jira] [Commented] (AMBARI-15330) Bubble up errors during RU/EU
[
https://issues.apache.org/jira/browse/AMBARI-15330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190747#comment-15190747
]
Hadoop QA commented on AMBARI-15330:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12792599/AMBARI-15330.trunk.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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5828//console
This message is automatically generated.
> 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)
[jira] [Commented] (AMBARI-15330) Bubble up errors during RU/EU
[
https://issues.apache.org/jira/browse/AMBARI-15330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15187422#comment-15187422
]
Hadoop QA commented on AMBARI-15330:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12792188/AMBARI-15330.trunk.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/5782//console
This message is automatically generated.
> 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)
[jira] [Commented] (AMBARI-15330) Bubble up errors during RU/EU
[
https://issues.apache.org/jira/browse/AMBARI-15330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184568#comment-15184568
]
Hadoop QA commented on AMBARI-15330:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791932/AMBARI-15330.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5764//console
This message is automatically generated.
> 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)
