tree 3005f8f0529ebe87c29ec3e22ef5c475d7334f82
parent f441dba2f686a182af7014983c3d066fa2115a00
author Andrew Geissler <geissonator@yahoo.com> 1607551416 -0600
committer Andrew Geissler <geissonator@yahoo.com> 1608174476 -0600

run soft off in quiesce

When the obmc-host-quiesce@.target was initially created the idea was to
leave the system in the state it was in. In most cases the host had
crashed.

As OpenBMC has grown, the use cases for the quiesce target have grown.
For example the Quiesce On Hardware Error design:
https://github.com/openbmc/docs/blob/master/designs/fail-boot-on-hw-error.md

When the QuiesceOnHwError setting is enabled, the host will be put in a
Quiesce state to indicate that an error has occurred. In a lot of cases
though the host actually can (and does) continue to boot. This causes a
lot of confusion for the user (host state shows Quiesce but host is
still booting).

This commit adds the pldmSoftPowerOff.service to the quiesce target to
ensure the host is given a chance (if it's running) to gracefully shut
itself down. If the host does not respond then the soft off service will
follow it's timeout flow and exit without error.

Tested:
- Verified when quiesce error is injected that the PLDM soft off service
was called

(From meta-phosphor rev: dfa2d6beb496b2265402950caf524c7f79850c46)

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ie6d07011a5ac5f6964435364ff6e332a77e5a3d4
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>