Comment 1 for bug 1655681

I did some testing with diskimage-builder, to start using dracut instead of busybox, as this element claims. I saw that lvm and crypt modules were properly added to the ramdisk (had to install cryptsetup and lvm2 packages as well) . But the problem i see with that, is that this elements generates an independent ramdisk file, instead of updating the ramdisk used in the /boot directory.
We cannot use it in TripleO like that, because we extract initrd and vmlinuz from boot directory (or use whole disk images, just consuming the qcow2) . So that extra generated file is not consumed by TripleO, and the modules are not loaded.