Juju doesn't handle HTTP 500 errors from the Nova API well
Bug #1887601 reported by
Barry Price
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Hi,
In situations where the underlying Openstack cloud is under high load, the Nova API endpoint can return an HTTP 500 error when queried by Juju.
The workers will restart on those errors, and then retry, get another 500 and loop - which can then further destabilise the cloud.
This was observed on 2.6.10 but I think it's still the case in the current codebase.
Adding an exponential backoff here should lessen the impact.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.8-next |
| importance: | Undecided → High |
| status: | New → Triaged |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | High → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
All related to bug 1690004