Closed rafabene closed 6 years ago
The Step https://github.com/redhat-developer-demos/istio-tutorial#http-error-503 also fails. You can check it running the Scenario https://www.katacoda.com/rafabene/courses/workshop/5-fault-injection
We're looking at changing this. For certain requests we want to have this behaviour (Openshift dashboard still loading), where as application errors we want to show the error.
We need the HTTP error code to be returned from the app as that is what Istio seems to be monitoring for things like circuit-breakers.
yes for Istio circuit breakers to work we need right error codes - in this case HTTP 5xx
We can change that
On 23 Jan 2018 11:33 am, "Kamesh Sampath" notifications@github.com wrote:
yes for Istio circuit breakers to work we need right error codes - in this case HTTP 5xx
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/redhat-developer-demos/istio-tutorial/issues/16#issuecomment-359763027, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFCtmrJ8qokInnqzLSg-08ts5EYbAcdks5tNcN0gaJpZM4Rlknw .
@BenHall Giving this discussion and how Istio handles circuit breakers, we need to change that. What's the procedure? Should I report that somewhere?
@BenHall Do you have any updates on this? Thank you
Solved in Katacoda. Reference: https://trello.com/c/AjTJfVNc/48-application-error-avoids-katacoda-to-show-its-message
When the exception is propagated to Customer, it impacts Katacoda as any HTTP response that is not 20x will cause Katacoda to say that the application is not available, thus the steps https://github.com/redhat-developer-demos/istio-tutorial#deploy-customer and https://github.com/redhat-developer-demos/istio-tutorial#deploy-preferences will fail. You can check this behaviour by running the Katacoda scenario https://www.katacoda.com/rafabene/courses/workshop/2-deploy-microservices