ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7596) Failure handling of downloading client configs
Date Wed, 08 Oct 2014 18:47:35 GMT

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

Hudson commented on AMBARI-7596:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #517 (See [https://builds.apache.org/job/Ambari-trunk-Commit/517/])
AMBARI-7596. Failure handling of downloading client configs (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=eb563008d33c8da0fbf2289123b2daee07269ed0)
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProviderTest.java


> Failure handling of downloading client configs
> ----------------------------------------------
>
>                 Key: AMBARI-7596
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7596
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.0.0
>
>
> We should log output of the executed python commands, also stderr, and check
> the return code of them.
> If it's not 0 we should throw exception, or warning message to the server
> logs, which would contain the reason of failure (the python expection message
> without stack trace).
> In that case we should return like 500 error code. Not to give malformed
> configs to the customers, and to do early failing which is helpful.



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

Mime
View raw message