no free nbd devices while spawning many instances per node, injecting data fails
Bug #726244 reported by
Christian Berendt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
High
|
Michael Still | ||
Bug Description
While spawning more instances then max_nbd_devices (or 16 per default) I got the error "2011-02-27 22:45:22,370 WARNING nova.virt.
". I think there sould be some logic to handle this case.
| Changed in nova: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Revision history for this message
| Mark McLoughlin (markmc) wrote | #1 |
Revision history for this message
| Mark McLoughlin (markmc) wrote | #3 |
| tags: | added: ops |
| Changed in nova: | |
| importance: | Low → High |
| status: | Confirmed → Triaged |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #4 |
| Changed in nova: | |
| assignee: | nobody → Michael Still (mikalstill) |
| status: | Triaged → In Progress |
| summary: |
- no free nbd devices while spawning to many instances per node, injecting + no free nbd devices while spawning many instances per node, injecting data fails |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #5 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → grizzly-2 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | grizzly-2 → 2013.1 |
Revision history for this message
| Stanislaw Pitucha (stanislaw-pitucha) wrote | #6 |
To post a comment you must log in.
I guess the thing to do here would be to wait until an NBD device frees up
Or is this the race condition that Pádraig talks about here:
https:/