recipes-phosphor: Fix systemd unit dependences of ipmid, mboxd
With the implementation of DBus and IPMI transports for the HIOMAP
protocol, mboxd now depends on ipmid being alive in its shutdown
sequence in order to propagate BMC status events to the host firmware.
Mark phosphor-ipmi-host.service as depending on
org.openbmc.HostIpmi.service and mboxd as depending on
phosphor-ipmi-host.service to ensure the mboxd state update
event on SIGTERM is propagated to the host before the services are torn
down.
(From meta-phosphor rev: e66105318af187ba5d4bdbf53668f309785df4f3)
Change-Id: Ia9ff24d0d3376d239b56840d666275d20821c7e6
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
diff --git a/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-host/phosphor-ipmi-host.service b/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-host/phosphor-ipmi-host.service
index ef24bd0..74f8218 100644
--- a/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-host/phosphor-ipmi-host.service
+++ b/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-host/phosphor-ipmi-host.service
@@ -11,6 +11,8 @@
After=mapper-wait@-xyz-openbmc_project-control-host0-restriction_mode.service
Wants=clear-once.service
After=clear-once.service
+Requires=org.openbmc.HostIpmi.service
+After=org.openbmc.HostIpmi.service
[Service]
Restart=always