host-reboot: move to PSM subdir

Per the project anti-patterns[1], scripts are suppose to be installed
in a package-named subdirectory within libexec. Move appropriately
and update the service file.

host-reboot: move to PSM subdir

Per the project anti-patterns[1], scripts are suppose to be installed
in a package-named subdirectory within libexec. Move appropriately
and update the service file.

[1]: https://github.com/openbmc/docs/blob/master/anti-patterns.md#background-4

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie62e032707f374da4af20c38bbf358a8c442d690

show more ...

host-reboot: enforce host boot count on host crash

The host reboot path can be triggered via paths outside of the normal
RequestedHostTransition property set. For example, if the host crashes,
it ju

host-reboot: enforce host boot count on host crash

The host reboot path can be triggered via paths outside of the normal
RequestedHostTransition property set. For example, if the host crashes,
it just triggers an automatic reboot using the systemd targets, which
means the check to prevent continuous host reboots is not run.

This commit ensures we decrement the reboot counter when a host crash
occurs, and it also ensures we check that count when deciding if a
reboot should occur.

While testing, it was found when we end in the host Quiesce state (after
all reboot attempts have expired), the host stayed in Quiesce, even
after issuing a power off. The fix for that was to ensure the
obmc-host-quiesce@.target conflicted with obmc-host-stop@.target to
ensure it would properly run on the power off request and update the
host state to Off.

Tested:
- Verified that AttemptsLeft was properly decremented on host crashes
- Verified that when AttempsLeft reached 0, the reboot was halted
and the host state was moved to Quiesced
- Verified that once in Quiesced, system could be powered off, and a
boot worked fine (and AttempsLeft was back to 3)

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

show more ...

ensure reboot service runs after host stopped

OpenBMC has two types of targets, action and synchronization.
obmc-host-stop is an action target. You put services in it that you want
run when the targ

ensure reboot service runs after host stopped

OpenBMC has two types of targets, action and synchronization.
obmc-host-stop is an action target. You put services in it that you want
run when the target is started. obmc-host-stopped is a synchronization
target. You use it to ensure your service runs at the correct time. As a
part of the warm-reboot work, it was found that in certain conditions
this reboot service would run before the host was fully stopped due to
the way the obmc-host-stop action target is setup. Add the
synchronization target Wants/After in here to ensure this service is
only run after the host is stopped.

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

show more ...

move state manager service files into its repo

OpenBMC is moving towards individual repos hosting and maintaining their
own service files. This allows the corresponding maintainer more control
over

move state manager service files into its repo

OpenBMC is moving towards individual repos hosting and maintaining their
own service files. This allows the corresponding maintainer more control
over their service file and removes the meta-* layer maintainer from
needing to be involved.

Once this is merged, its bump will need to be combined with a change in
the meta-phosphor layer that removes the service files.

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

show more ...