From 7cc486719fc1e1088de3d1b195d6f4bfe97d3803 Mon Sep 17 00:00:00 2001
From: Eugene Shatokhin <eugene.shatokhin@rosalab.ru>
Date: Wed, 22 Apr 2015 10:35:53 +0300
Subject: [PATCH] Always regenerate initrd

Even if it already exists. This may happen if kernel-<...>-devel is
installed first, triggers rebuild of DKMS modules and some of these
request remaking of initrd. The initrd that is created then will be
non-functional. But when the user installs kernel-<...> package, that
defunct initrd will be replaced with a working one here.
---
 kernel.spec | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/kernel.spec b/kernel.spec
index 6de57a7..7291a48 100644
--- a/kernel.spec
+++ b/kernel.spec
@@ -1487,14 +1487,16 @@ EOF
 %endif
 
 ### Create kernel Post script
+# We always regenerate initrd here, even if it already exists. This may
+# happen if kernel-<...>-devel is installed first, triggers rebuild of
+# DKMS modules and some of these request remaking of initrd. The initrd
+# that is created then will be non-functional. But when the user installs
+# kernel-<...> package, that defunct initrd will be replaced with a working
+# one here.
 cat > $kernel_files-post <<EOF
 INITRD=/boot/initrd-$KernelVer.img
+/sbin/dracut -f \${INITRD} $KernelVer
 
-if [ ! -e \${INITRD} ]; then
-	/sbin/dracut \${INITRD} $KernelVer
-else
-	printf "WARNING: Initrd image \${INITRD} already exists and will not be replaced.\n"
-fi
 /usr/sbin/update-grub2
 
 pushd /boot > /dev/null