LibvirtISCSIVolumeDriver cannot find volumes that include pci-* in the /dev/disk/by-path device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Anish Bhatt | ||
os-brick |
Fix Released
|
High
|
Anish Bhatt |
Bug Description
I am currently unable to attach iSCSI volumes to our system because the path that is expected by the LibvirtISCSIVol
2014-09-16 01:33:22.533 24304 DEBUG nova.openstack.
2014-09-16 01:33:22.534 24304 ERROR nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
2014-09-16 01:33:22.534 24304 TRACE nova.virt.
The paths that are being created, however, are of the following format:
[root@abba-n09 rules.d]# ll /dev/disk/by-path/
total 0
lrwxrwxrwx. 1 root root 9 Sep 16 10:56 pci-0000:
lrwxrwxrwx. 1 root root 9 Sep 16 10:56 pci-0000:
lrwxrwxrwx. 1 root root 9 Sep 16 10:56 pci-0000:
lrwxrwxrwx. 1 root root 9 Sep 16 10:56 pci-0000:
lrwxrwxrwx. 1 root root 9 Sep 10 18:46 pci-0000:
lrwxrwxrwx. 1 root root 10 Sep 10 18:46 pci-0000:
lrwxrwxrwx. 1 root root 10 Sep 10 18:46 pci-0000:
lrwxrwxrwx. 1 root root 10 Sep 10 18:46 pci-0000:
lrwxrwxrwx. 1 root root 10 Sep 10 18:46 pci-0000:
lrwxrwxrwx. 1 root root 9 Sep 10 18:46 pci-0000:
[root@abba-n09 rules.d]#
When the devices are created the physical location of the HBA is being included:
0c:00.2 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (be3) (rev 02)
Looking at the code, I see that theLibvirtISERV
def _get_host_
host_device = None
device = ("ip-%s-
if look_for_device:
return host_device
So, I was able to get the volume to mount properly by changing the nova.conf file with the following change:
volume_
Setting the iscsi driver, however, to use the iser driver seems suspicious to me. It seems like we still have a bug here somewhere.
The node where I am seeing this is using HBA's. So maybe the iser driver is the right option. Does this mean, however that the storwize_svc driver that is being used to create the volumes should have an iSER option?
Should the iSCSI driver be updated to do look_for_device = glob.glob(
tags: | added: volumes |
Changed in nova: | |
status: | New → Incomplete |
Changed in nova: | |
assignee: | nobody → Anish Bhatt (anish7) |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in os-brick: | |
assignee: | nobody → Anish Bhatt (anish7) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in nova: | |
milestone: | kilo-2 → 2015.1.0 |
Changed in os-brick: | |
status: | Triaged → Confirmed |
Changed in os-brick: | |
status: | Confirmed → In Progress |
Changed in os-brick: | |
milestone: | none → 0.4.0 |
status: | Fix Committed → Fix Released |
So, I'm honestly sort of surprised that HBA support is in there at all, as I didn't think that was the case.