| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
If the BMC was rebooted while the chassis power was on
then we want the BMC to update it's targets to reflect
this and leave the system as-is. This also applies if
the host is running.
Resolves openbmc/openbmc#2180
Change-Id: Ib9c067d79368db749fd65d050132d15ad793fdbf
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit enables patches from the /usr/local path by replacing
absolute paths to /usr/sbin or /usr/bin in every service file with
"/usr/bin/env ". Additionally, SyslogIdentifier is added to each
file to ensure that journal entries are still distinct.
In two cases, service files also had to change due to references
to ${{PATH}}, which doesn't work with /usr/bin/env. These
references - and the corresponding definitions - were changed to
${{DEVPATH}}.
Resolves openbmc/openbmc#2149
Change-Id: I12c5c6e5101eef6820b985a563313836250ff2c7
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a BMC reboot occurs with the host running, need
to ensure the reset targets and services run before
we start other application that depend on whether
the host is running
Specifically, don't start phosphor-host-state-manager until
it's been determined if the host is up. Don't start
phosphor-discover-system-state until the state of the
chassis is known.
Change-Id: I458fa78802cd9ecca99c54834512bfebf04b5012
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The state management code on the BMC is designed to
utilize systemd targets as much as possible. The host
reboot was always the odd duck that had some special
code written to support it. This special code would
basically issue a power off, look for it to complete
and then issue a power on. This is very error prone
code and has resulted in a few issues.
Moving to a single systemd target (the new reboot target)
defined here will allow the host reboots to occur
solely through a single systemd target now.
openbmc/openbmc#2032 is one of those bugs being
addressed with this change.
Change-Id: If33454aa4f15580e45f888a9b1602dec24a46fca
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
| |
|
|
|
| |
Change-Id: I0e7e84f191f6a466b0f84c6d4f490816331f141f
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
|
| |
|
|
|
|
|
|
|
| |
The obmc-host-stop@.target will always be called on host shutdowns
but the inverse is not always true. This commit ensures everything
conflicts with the target that is always called in this path.
Change-Id: Ic680ef96b1d6e2aec844a9c619928b7014fe7450
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
| |
|
|
|
|
|
|
| |
This application and services will be used by the host reset service
to determine if the host is running after a BMC has been rebooted
Change-Id: I8299546b0f275ebbb46aa775ab7b0633cc3fd5e0
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This recipe will add the new program phosphor-discover-system-state
to new builds. Additionally, the old Python state manager is
removed from the build since discover_system_state.py was the last
thing in it.
Resolves openbmc/openbmc#773
Change-Id: I99ba0f1f0264cedebc5a9a7e5fa5dbaba0b79502
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
|
| |
|
|
|
| |
Change-Id: I4c013d98e03703b1328d85ae00cebb8500ffa205
Signed-off-by: Josh King <jdking@us.ibm.com>
|
|
|
The phosphor-state-manager repository builds [at least] two executables:
* phosphor-host-state-manager
* phosphor-chassis-state-manager
phosphor-host-state-manager.bb and phosphor-chassis-state-manager.bb
were effectively the exact same file and had no assignment of
executables to files. The result was that both packages installed both
daemons and caused an installation collision.
Combine the two recipes into a single recipe with the correct package
relationship for each executable.
Change-Id: I76a1e598bebc5090ae374271bbd5e8e32967cb43
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
