Conflict with host-stop target vs. host-shutdown
The obmc-host-stop@.target will always be called on host shutdowns
but the inverse is not always true. This commit ensures everything
conflicts with the target that is always called in this path.
Change-Id: Ic680ef96b1d6e2aec844a9c619928b7014fe7450
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
diff --git a/common/recipes-phosphor/state/files/phosphor-reset-host-check@.service b/common/recipes-phosphor/state/files/phosphor-reset-host-check@.service
index ba4f0c0..f480cc5 100644
--- a/common/recipes-phosphor/state/files/phosphor-reset-host-check@.service
+++ b/common/recipes-phosphor/state/files/phosphor-reset-host-check@.service
@@ -6,7 +6,7 @@
Before=obmc-host-reset-running@%i.target
Wants=op-reset-chassis-on@%i.service
After=op-reset-chassis-on@%i.service
-Conflicts=obmc-host-shutdown@%i.target
+Conflicts=obmc-host-stop@%i.target
ConditionPathExists=/run/openbmc/chassis@%i-on
[Service]