Windows Fibre Channel disk scan issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-brick |
Fix Released
|
Undecided
|
Lucian Petrut |
Bug Description
The Windows Fibre Channel connector has a few issues regarding disk scanning.
We're using the common hbaapi library in order to fetch FC disk mappings. Usually the disk mappings for a specific LUN are retrieved but do not contain the OS level disk path, even in case of already discovered and attached disks. For this reason, this operation is usually repeated quite a few times, involving a full disk rescan, which can be time consuming. This leads to poor overall performance, especially when having multiple simultaneous attachments (taking even more than 5 minutes to retrieve a disk, causing timeouts).
Also note that on some environments, the mappings contain the disk path only when exposed to the host as an "Online" disk, which is not an option when using passthrough disks.
At the same time, the Multipath-IO service can be troublesome. In some cases, a disk exposed over FC is discovered, exposed to the OS, gets a disk number/path assigned, the MPIO service claims it, re-exposes it to the OS using a different number/path. This can be really troublesome as os-brick may report an incorrect disk path. This is a potential security issue as the initial path may then point to a different tenant's volume.
Changed in os-brick: | |
status: | New → In Progress |
assignee: | nobody → Lucian Petrut (petrutlucian94) |
description: | updated |
Fix proposed to branch: master /review. openstack. org/490840
Review: https:/