[PATCH 1/5] Reset vg blacklist when initializing storage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This avoids the following problem:
1) take a system with duplicate vgs
2) select atleast 1 disk belonging to either vg in the filter UI
3) next
4) Choose to ignore the duplicate vgs the vg name they share now gets
   added to the vg blacklist
5) realize you got this question because you selected the wrong disks
6) go back to the filter ui, select disks of 1 vg only
7) next
8) the vg name is still in the vg blacklist
---
 storage/__init__.py |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/storage/__init__.py b/storage/__init__.py
index a5366b0..abe5e0f 100644
--- a/storage/__init__.py
+++ b/storage/__init__.py
@@ -95,6 +95,7 @@ def storageInitialize(anaconda):
 
     anaconda.intf.resetInitializeDiskQuestion()
     anaconda.intf.resetReinitInconsistentLVMQuestion()
+    lvm.lvm_vg_blacklist = []
 
     # Set up the protected partitions list now.
     if anaconda.protected:
-- 
1.7.0.1

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux