phosphor: ensure host state sensors cleared on host quiesce
By design, nothing occurs in the obmc-host-quiesce target. The point is
to leave everything in its current state so external debug can occur.
The host states sensors should be reset though so other BMC software
knows the host is in an undefined state.
Tested:
- Verified sensors were reset when obmc-host-quiesce target was started
(From meta-phosphor rev: 1ac5d20b80688027c61b153e8ba46dc1e855b030)
Change-Id: Ib99b0261976335bbc0644e5572a131c4f3e25304
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/meta-phosphor/recipes-phosphor/state/phosphor-state-manager-systemd-links.inc b/meta-phosphor/recipes-phosphor/state/phosphor-state-manager-systemd-links.inc
index 4803cac..1ec65d2 100644
--- a/meta-phosphor/recipes-phosphor/state/phosphor-state-manager-systemd-links.inc
+++ b/meta-phosphor/recipes-phosphor/state/phosphor-state-manager-systemd-links.inc
@@ -36,6 +36,11 @@
TARGET="../phosphor-reset-sensor-states@.service"
ln -s $TARGET $LINK
+ mkdir -p $D$systemd_system_unitdir/obmc-host-quiesce@0.target.wants
+ LINK="$D$systemd_system_unitdir/obmc-host-quiesce@0.target.wants/phosphor-reset-sensor-states@0.service"
+ TARGET="../phosphor-reset-sensor-states@.service"
+ ln -s $TARGET $LINK
+
mkdir -p $D$systemd_system_unitdir/obmc-host-shutdown@0.target.requires
LINK="$D$systemd_system_unitdir/obmc-host-shutdown@0.target.requires/obmc-chassis-poweroff@0.target"
TARGET="../obmc-chassis-poweroff@.target"
@@ -97,6 +102,9 @@
LINK="$D$systemd_system_unitdir/obmc-host-stop@0.target.wants/phosphor-reset-sensor-states@0.service"
rm $LINK
+ LINK="$D$systemd_system_unitdir/obmc-host-quiesce@0.target.wants/phosphor-reset-sensor-states@0.service"
+ rm $LINK
+
LINK="$D$systemd_system_unitdir/obmc-host-reset@0.target.requires/phosphor-reset-host-running@0.service"
rm $LINK