unclear-error-message-on-lp-create
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Solum |
Fix Released
|
High
|
Devdatta Kulkarni |
Bug Description
If a languagepack with a specific name already exists, then trying to create a new languagepack with that name fails as expected.
However, the error message on the CLI is not very informative.
Here is the stack trace from the api:
2015-09-23 14:43:36.728 6580 DEBUG oslo_db.
2015-09-23 14:43:36.744 6580 DEBUG wsme.api [-] Client-side error: The python resource already exists. format_exception /usr/local/
2015-09-23 14:43:36.745 6580 ERROR solum.common.
10.0.2.15 - - [23/Sep/2015 14:43:36] "POST /v1/language_packs HTTP/1.1" 409 375 0.187264
Here is the error message on the client:
vagrant@
solum languagepack create python https:/
ERROR: Your request could not be handled because of a problem in the server. Error Correlation id is: c600560c-
Changed in solum: | |
assignee: | nobody → Devdatta Kulkarni (devdatta-kulkarni) |
milestone: | none → 2015.1.2 |
Changed in solum: | |
milestone: | 2015.1.2 → 4.0.0 |
Changed in solum: | |
status: | Fix Committed → Fix Released |
Also, we are seeing following exception line in the solum-api log:
2015-09- 28_23:46: 10.33248 2015-09-28 23:46:10.332 25349 ERROR solum.common. exception [-] 28efb80a- ca8f-4d3f- 8b3b-511fc314b2 34:Unknown Error
This is happening because of incorrect exception wrapper that we are using to wrap solum controller methods.