[
https://issues.apache.org/jira/browse/AMBARI-11393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559728#comment-14559728
]
Hadoop QA commented on AMBARI-11393:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735364/AMBARI-11393.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/2868//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2868//console
This message is automatically generated.
> Posting a Blueprint with an Invalid Stack version number throws incorrect
> error
> -------------------------------------------------------------------------------
>
> Key: AMBARI-11393
> URL: https://issues.apache.org/jira/browse/AMBARI-11393
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Fix For: 2.1.0
>
> Attachments: AMBARI-11393.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Attempting to post a Blueprint with an invalid version number (Example, HDP
> Stack version "99.99") currently results in a "500 Server Error" being thrown
> back to the client, with no information on the cause of the error. The
> ambari-server log shows that an internal exception is thrown, since the
> invalid stack error is not properly propagated back to the calling client.
> The Blueprint processing code needs to throw a more reasonable error back to
> the caller, a "400" status error, with a meaningful error message when an
> invalid stack is referenced in a Blueprint.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
