[PATCH 07/11] Post-custom sanity check determines storage spoke completeness. (#868925)

David Lehman dlehman at redhat.com
Fri Nov 9 21:09:17 UTC 2012


If the storage spoke was completed prior to entering the custom spoke
and that visit introduced errors, the storage spoke status wasn't
getting updated accordingly, allowing users with faulty configurations
to proceed with a doomed install.
---
 pyanaconda/ui/gui/spokes/custom.py |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/pyanaconda/ui/gui/spokes/custom.py b/pyanaconda/ui/gui/spokes/custom.py
index 7a33352..ed1a0d1 100644
--- a/pyanaconda/ui/gui/spokes/custom.py
+++ b/pyanaconda/ui/gui/spokes/custom.py
@@ -70,6 +70,7 @@ from pyanaconda.storage.devicelibs import mdraid
 from pyanaconda.storage.devices import LUKSDevice
 
 from pyanaconda.ui.gui import GUIObject
+from pyanaconda.ui.gui import communication
 from pyanaconda.ui.gui.spokes import NormalSpoke
 from pyanaconda.ui.gui.spokes.storage import StorageChecker
 from pyanaconda.ui.gui.spokes.lib.cart import SelectedDisksDialog
@@ -390,7 +391,10 @@ class CustomPartitioningSpoke(NormalSpoke, StorageChecker):
 
         # set up bootloader and check the configuration
         self.storage.setUpBootLoader()
+
+        StorageChecker.errors = []
         StorageChecker.run(self)
+        communication.send_ready("StorageSpoke", justUpdate=True)
 
     @property
     def indirect(self):
-- 
1.7.7.6



More information about the anaconda-patches mailing list