service status are not set for the instance when a cluster times out
Bug #1507053 reported by
Sushil Kumar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
In Progress
|
Low
|
Craig Vyvial | ||
Bug Description
only the instance status is set and not the service status for the instances in cluster which gets timed out and the taskmanager log shows that the fetching of service status keeps on continuing for those kind of instance until the service status gets updated on instance level usage_timeout.
| Changed in trove: | |
| status: | New → In Progress |
| assignee: | nobody → Sushil Kumar (sushil-kumar2) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to trove (master) | #1 |
| Changed in trove: | |
| assignee: | Sushil Kumar (sushil-kumar2) → Craig Vyvial (cp16net) |
| Changed in trove: | |
| importance: | Undecided → Low |
| milestone: | none → newton-1 |
| Changed in trove: | |
| assignee: | Craig Vyvial (cp16net) → Amrith (amrith) |
| Changed in trove: | |
| assignee: | Amrith (amrith) → Craig Vyvial (cp16net) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on trove (master) | #2 |
| Changed in trove: | |
| milestone: | newton-1 → ongoing |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/