mysql instance does not gets active in 400 seconds
Bug #1469989 reported by
Sushil Kumar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Sushil Kumar | ||
Bug Description
MySQL guest instance does not gets active in 400 seconds which is the value as suggested in https:/
As per integration tests log it ranges from 450 to 500 seconds, generally.
| Changed in trove: | |
| importance: | Undecided → Medium |
| milestone: | none → liberty-2 |
Revision history for this message
| Sushil Kumar (sushil-kumar2) wrote | #1 |
| Changed in trove: | |
| assignee: | nobody → Sushil Kumar (sushil-kumar2) |
| status: | New → In Progress |
| Changed in trove: | |
| milestone: | liberty-2 → liberty-3 |
| Changed in trove: | |
| status: | In Progress → Fix Committed |
| Changed in trove: | |
| status: | Fix Committed → Fix Released |
| Changed in trove: | |
| milestone: | liberty-3 → 4.0.0 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on trove (master) | #2 |
To post a comment you must log in.
Dealt with https:/