BUGFIX: Handle nukedisks before the we start autoyast. This prevents …

…the situation where the installer hangs because it attempted to mount a disk and could not later nuke it.

common/src/stack/storage-config/bin/initialize-storage.py

@@ -147,6 +147,9 @@ def nukeDisk(disk):
 	else:
 		break
 
+notify_cmd = """/opt/stack/bin/smq-publish -chealth '{"state": "install initializing storage"}'"""
+subprocess.run(notify_cmd, shell=True)
+
 #
 # nuke LVM first
 #

sles/src/stack/images/common/sles-stacki.img-patches/usr/lib/YaST2/startup/First-Stage/F08-stacki

@@ -52,13 +52,24 @@ echo "tracker = ${FRONTEND}:3825" > /tmp/stack.conf
 
 /opt/stack/bin/python3 -E /opt/stack/bin/ludicrous-client.py --environment initrd --trackerfile='/tmp/stack.conf';
 
+# nuke the disks, if appropriate
+/opt/stack/bin/initialize-storage.py
+
 #
 # configure the hardware disk array controller first
 #
 /opt/stack/bin/configure-controllers.py
 
 udevadm settle --timeout=60
 
+# NOTE: we initialize storage twice in RHEL, so do the same thing here, too
+
+# need to call 'initialize-storage.py' again after reconfiguring the
+# hardware disk controller because it may have created new LUNs and the
+# master boot record on a LUN may be corrupted and require initialization.
+
+/opt/stack/bin/initialize-storage.py
+
 #
 # then configure the partitions
 #