Use different timeouts for instance create, and instance restore
Bug #1356645 reported by
Nikhil Manchanda
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Fix Released
|
High
|
Nikhil Manchanda | ||
Bug Description
Currently we only have a single timeout (usage_timeout: default 400s) after which any instance in BUILD status is automatically put in error state.
However, if we're trying to restore an instance from backup, this can and will likely take longer than 400s, so we should have a different and larger timeout for this scenario.
| Changed in trove: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → juno-3 |
| assignee: | nobody → Nikhil Manchanda (slicknik) |
Revision history for this message
| Denis M. (dmakogon) wrote | #1 |
| Changed in trove: | |
| importance: | Medium → High |
| milestone: | juno-3 → ongoing |
| Changed in trove: | |
| milestone: | ongoing → juno-rc1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to trove (master) | #2 |
| Changed in trove: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to trove (master) | #3 |
| Changed in trove: | |
| status: | In Progress → Fix Committed |
| Changed in trove: | |
| status: | Fix Committed → Fix Released |
| Changed in trove: | |
| milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
as already said, restore timeout should be dependent on data size and network latency