Cinder volumes will start and look active when it's not
Bug #1460136 reported by
Ryan Hallisey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla |
Fix Released
|
Medium
|
Ryan Hallisey | ||
Bug Description
CInder volumes doesn't become active until it has completed its database work and talked to rabbitMQ. Cinder volumes will show as active within 30 seconds, but volume creation won't work until about 2 minutes later.
Make sure the Cinder volume container isn't active until is ready to be used.
| Changed in kolla: | |
| assignee: | nobody → Ryan Hallisey (rthall14) |
| importance: | Undecided → High |
| Changed in kolla: | |
| status: | New → Confirmed |
| importance: | High → Medium |
Revision history for this message
| Ryan Hallisey (rthall14) wrote | #1 |
| Changed in kolla: | |
| status: | Confirmed → In Progress |
| Changed in kolla: | |
| milestone: | none → liberty-1 |
| Changed in kolla: | |
| status: | In Progress → Fix Committed |
| Changed in kolla: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
supervisord was slowing down the container becoming active. Removing that fixed the problem.