tripleclient fails to retry when it gets a 504 from heat/haproxy
Bug #1833452 reported by
Alex Schultz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Alex Schultz |
Bug Description
While we wait for a stack to become ready, we may get a 504 from haproxy/heat indicating that the service is busy and the request timed out. We should retry rather than straight out failing because the action may eventually complete.
Changed in tripleo: | |
importance: | Medium → High |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/666429
Review: https:/