From a29d100ca368c513bed04af178b65d1462418a02 Mon Sep 17 00:00:00 2001 From: Vojtech Trefny Date: Wed, 16 Oct 2024 14:35:25 +0200 Subject: [PATCH] Fix checking whether a disk can be cleared during autopart One more issue related to the device ID change. This does not happen with "normal" disks because we use name as device ID for them so this is triggered on a system with a BIOS RAID array. Cherry-picked from master a3d56af01828488c17e878039abb4c0a6f331810 Resolves: rhbz#2317287 --- .../modules/storage/disk_initialization/configuration.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pyanaconda/modules/storage/disk_initialization/configuration.py b/pyanaconda/modules/storage/disk_initialization/configuration.py index c21204ee8a0..e80971805cd 100644 --- a/pyanaconda/modules/storage/disk_initialization/configuration.py +++ b/pyanaconda/modules/storage/disk_initialization/configuration.py @@ -50,7 +50,7 @@ def can_remove(self, storage, device): for disk in device.disks: # this will not include disks with hidden formats like multipath # and firmware raid member disks - if self.drives_to_clear and disk.name not in self.drives_to_clear: + if self.drives_to_clear and disk.device_id not in self.drives_to_clear: return False if not self.clear_non_existent: @@ -113,7 +113,7 @@ def can_remove(self, storage, device): return False if self.initialization_mode == CLEAR_PARTITIONS_LIST and \ - device.name not in self.devices_to_clear: + device.device_id not in self.devices_to_clear: return False return True