You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Robert Nettleton (JIRA)" <ji...@apache.org> on 2015/05/26 19:45:17 UTC

[jira] [Created] (AMBARI-11393) Posting a Blueprint with an Invalid Stack version number throws incorrect error

Robert Nettleton created AMBARI-11393:
-----------------------------------------

             Summary: 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


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)