[
https://issues.apache.org/jira/browse/AMBARI-11393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560072#comment-14560072
]
Hudson commented on AMBARI-11393:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2716 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2716/])
AMBARI-11393. Posting a Blueprint with an Invalid Stack version number throws
incorrect error. (rnettleton) (rnettleton:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8ac6583078e3c181455423910de353cb8d01525a)
*
ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintFactory.java
*
ambari-server/src/test/java/org/apache/ambari/server/topology/BlueprintFactoryTest.java
> 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)
