DescriptionYadnyawalk Tale
2018-08-06 20:18:38 UTC
Created attachment 1473731[details]
issue_5.9.4.2.png
Description of problem:
400 bad requests : Cannot create migration plan anymore - name already been taken
Version-Release number of selected component (if applicable):
5.9.4.2
How reproducible:
100%
Steps to Reproduce:
You must cause an API error. this is an improvement to the handling of an unexpected API error.
It would also be reproducible by altering the API code to force an error when POSTing a new migration plan. Tricky one, since it's the handling of an unexpected error.
Actual results:
400 bad request pop up
Expected results:
Error should not appear
Additional info:
Comment 2Sudhir Mallamprabhakara
2018-08-08 14:07:33 UTC
The problem was that we have fixed most of the things that were leading to API errors. But we still wanted to be prepared with a good response in case there is an API error in the future, due to some API change perhaps.
You will see earlire "We're sorry, something went wrong, please try again" with a Retry button that does nothing.
The bug was - the Retry button that does nothing, and the unhelpful error message. Mike's fix patches this behavior, it replaces "we're sorry" with the actual API error message and replaces Retry with Close.
Verified on: 5.10.0.17.20180927011235_1b5cf54
Thanks!
Created attachment 1473731 [details] issue_5.9.4.2.png Description of problem: 400 bad requests : Cannot create migration plan anymore - name already been taken Version-Release number of selected component (if applicable): 5.9.4.2 How reproducible: 100% Steps to Reproduce: You must cause an API error. this is an improvement to the handling of an unexpected API error. It would also be reproducible by altering the API code to force an error when POSTing a new migration plan. Tricky one, since it's the handling of an unexpected error. Actual results: 400 bad request pop up Expected results: Error should not appear Additional info: