6136c1
From ea425381a675a2ce4d9519d534fe27c1012ac92e Mon Sep 17 00:00:00 2001
6136c1
From: Franck Bui <fbui@suse.com>
6136c1
Date: Mon, 28 Jan 2019 12:07:37 +0100
6136c1
Subject: [PATCH] units: make sure initrd-cleanup.service terminates before
6136c1
 switching to rootfs
6136c1
6136c1
A follow-up for commit a8cb1dc3e0fa81aff.
6136c1
6136c1
Commit a8cb1dc3e0fa81aff made sure that initrd-cleanup.service won't be stopped
6136c1
when initrd-switch-root.target is isolated.
6136c1
6136c1
However even with this change, it might happen that initrd-cleanup.service
6136c1
survives the switch to rootfs (since it has no ordering constraints against
6136c1
initrd-switch-root.target) and is stopped right after when default.target is
6136c1
isolated. This led to initrd-cleanup.service entering in failed state as it
6136c1
happens when oneshot services are stopped.
6136c1
6136c1
This patch along with a8cb1dc3e0fa81aff should fix issue #4343.
6136c1
6136c1
Fixes: #4343
6136c1
(cherry picked from commit e2c7c94ea35fe7e669afb51bfc2251158b522ea5)
6136c1
6136c1
Related: #1657810
6136c1
---
6136c1
 units/initrd-switch-root.target | 2 +-
6136c1
 1 file changed, 1 insertion(+), 1 deletion(-)
6136c1
6136c1
diff --git a/units/initrd-switch-root.target b/units/initrd-switch-root.target
6136c1
index ad82245121..ea4f02618f 100644
6136c1
--- a/units/initrd-switch-root.target
6136c1
+++ b/units/initrd-switch-root.target
6136c1
@@ -15,4 +15,4 @@ Requires=initrd-switch-root.service
6136c1
 Before=initrd-switch-root.service
6136c1
 AllowIsolate=yes
6136c1
 Wants=initrd-udevadm-cleanup-db.service initrd-root-fs.target initrd-fs.target systemd-journald.service initrd-cleanup.service
6136c1
-After=initrd-udevadm-cleanup-db.service initrd-root-fs.target initrd-fs.target emergency.service emergency.target
6136c1
+After=initrd-udevadm-cleanup-db.service initrd-root-fs.target initrd-fs.target emergency.service emergency.target initrd-cleanup.service