It happens that the order in which kickstart schedules actions when
a new device is encrypted relies on there being a format create
action for the underlying block device.
---
pyanaconda/storage/__init__.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/pyanaconda/storage/__init__.py b/pyanaconda/storage/__init__.py
index 5317c1b..0ea0304 100644
--- a/pyanaconda/storage/__init__.py
+++ b/pyanaconda/storage/__init__.py
@@ -971,7 +971,7 @@ class Storage(object):
available raid minor if one isn't already set.
"""
self.devicetree.registerAction(ActionCreateDevice(device))
- if device.format.type and device.format.type != "btrfs":
+ if device.format.type:
self.devicetree.registerAction(ActionCreateFormat(device))
def destroyDevice(self, device):
--
1.7.7.6
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
