Drop start up check on Ironic availability
Bug #1462993 reported by
Dmitry Tantsur
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic Inspector |
Fix Released
|
High
|
Sam Betts | ||
Bug Description
I got reports from users that often inspector fails to start due to Ironic and Keystone starting much later. We need to increase wait timeout by default at least twice (bumping to 6 * 10 sounds fine).
| description: | updated |
Revision history for this message
| Ben Nemec (bnemec) wrote | #1 |
Revision history for this message
| Dmitry Tantsur (divius) wrote | #2 |
| summary: |
- Start-up retry time is too low for real life cases + Drop start up check on Ironic availability |
| Changed in ironic-inspector: | |
| assignee: | nobody → Sam Betts (sambetts) |
| Changed in ironic-inspector: | |
| status: | Triaged → Fix Committed |
| Changed in ironic-inspector: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Is there any particular reason inspector has to time out at all? Given that it has dependencies on services that may be running on a completely separate system it seems like any reasonable length timeout could cause similar issues.