Netapp E-Series Driver should not use LUN ID 0
Bug #1457995 reported by
Rushil Chugh
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Fix Released
|
Undecided
|
Rushil Chugh | ||
Bug Description
lun-0 is a special lun number (a well-known lun) and should be avoided and not assigned. Currently E-Series is picking lun ids in order starting at 0.
| Changed in cinder: | |
| assignee: | nobody → Rushil Chugh (rushil) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cinder (master) | #1 |
| Changed in cinder: | |
| status: | In Progress → Fix Committed |
| Changed in cinder: | |
| milestone: | none → liberty-1 |
| status: | Fix Committed → Fix Released |
| Changed in cinder: | |
| milestone: | liberty-1 → 7.0.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit c4909c606f3e5c5
Author: Rushil Chugh <email address hidden>
Date: Wed Apr 22 18:40:18 2015 -0400
Avoid LUN ID collisions in NetApp iSCSI drivers
Previously, the logic to calculate the LUN ID only considered a single attached
host. Because multiple hosts can be attached to a LUN, the logic needs to
consider multiple hosts. This patchset proposes to choose non-conflicting
LUN IDs across the whole array. This patch first checks for an empty LUN ID
across the array. If it doesn't find one, then it looks for the least used
LUN ID across the whole array.
The value of MAX_LUNS_PER_HOST has been changed here as the range function
iterates from 0 to n-1 LUN IDs. With Eseries backend, a maximum of 256 LUN_IDS
are supported, thus a value of 256 MAX_LUNS_PER_HOST is required.
Closes-bug: 1433825
Closes-bug: 1457995
Change-Id: I033368c12c90d7