c540731aee
ATARAID is functionally a version of software RAID where the setup is managed by the controller and the Operating System takes over managing the RAID after boot. Most commonly this is found for mirrored boot devices. Prior to this patch, we were looking for non-dependent items (i.e. base block devices), with a type of disk. Now we will permit the "disk" to be added to the list if lsblk indicates that it is a type containing "raid". The lsblk results should not change as we explicitly look for disk objects. Change-Id: Ia4a03b33cc06ce42e1bc33026683c28b31901cb7 Story: #2003445 Task: #24647
19 lines
769 B
YAML
19 lines
769 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue where devices offered via ATARAID
|
|
(or even software RAID setup by a hardware manager)
|
|
were excluded from the list as they are not returned
|
|
as type disk, even though they should be considered
|
|
both disks and block devices.
|
|
See `story <https://storyboard.openstack.org/#!/story/2003445>`_
|
|
for more details.
|
|
upgrade:
|
|
- |
|
|
Operators with custom hardware managers to support software RAID
|
|
may wish to ensure that they have removed the software RAID prior
|
|
to any stock cleaning step for erasing block devices executes.
|
|
As a result of a bug fix, such devices may now be picked up in
|
|
the list of possible devices to delete, which may extend cleaning
|
|
depending on the deployment configuration.
|