iSCSI targets are not restored following a reboot
Bug #1001088 reported by
Paul Collins
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
High
|
Unassigned | ||
| nova (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
When using nova-volume (with the flag "--iscsi_
| summary: |
- iSCSi targets are not restored following a reboot + iSCSI targets are not restored following a reboot |
| Changed in nova (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| Changed in nova: | |
| status: | New → Confirmed |
| tags: | added: volume |
| Changed in nova: | |
| importance: | Undecided → High |
Revision history for this message
| Dan Smith (danms) wrote | #1 |
| Changed in nova: | |
| status: | Confirmed → Fix Committed |
| Changed in nova (Ubuntu): | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (stable/essex) | #2 |
| Changed in nova: | |
| milestone: | none → folsom-3 |
| status: | Fix Committed → Fix Released |
| Changed in nova (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | folsom-3 → 2012.2 |
To post a comment you must log in.
I'm not able to reproduce this in current nova. There is code to recreate the iscsi volumes, and as far as I can tell, it seems to work as expected.