Host watchdog needs to conflict with quiesce target
If the server enters the quiesce target, the BMC needs
to stop the host watchdog. This is so the BMC does not
log a second error (one for whatever caused quiesce
and one for the host watchdog timeout).
If the host watchdog timeout is the reason for entering
the quiesce target, then it's error will be logged
prior to entering the quiesce target.
Resolves openbmc/openbmc#2282
Change-Id: I43fe484049587cc579ec04fd399a4ae78134031c
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
diff --git a/meta-phosphor/common/recipes-phosphor/watchdog/phosphor-watchdog/poweron.conf b/meta-phosphor/common/recipes-phosphor/watchdog/phosphor-watchdog/poweron.conf
index 93e74e3..b253249 100644
--- a/meta-phosphor/common/recipes-phosphor/watchdog/phosphor-watchdog/poweron.conf
+++ b/meta-phosphor/common/recipes-phosphor/watchdog/phosphor-watchdog/poweron.conf
@@ -1,3 +1,4 @@
[Unit]
Conflicts=obmc-host-stop@0.target
Conflicts=obmc-chassis-poweroff@0.target
+Conflicts=obmc-host-quiesce@0.target