phosphor-discover-system-state: set after multi-user.target

Set the phosphor-discover-system-state service to run after
multi-user.target to ensure the operation is successful.
Avoid setting the Pow

phosphor-discover-system-state: set after multi-user.target

Set the phosphor-discover-system-state service to run after
multi-user.target to ensure the operation is successful.
Avoid setting the PowerRestoreDelay time still meet BMC not
being ready.
This is particularly important when facing network instability,
which can delay the activation of multi-user.target.

Test Log:
```
....
May 09 18:18:49 bmc phosphor-bmc-state-manager[903]: BMC_READY
May 09 18:18:49 bmc phosphor-bmc-state-manager[903]: Setting the BMCState field to xyz.openbmc_project.State.BMC.BMCState.Ready
May 09 18:18:49 bmc systemd[1]: Started Reboot Host 1 If Enabled.
May 09 18:18:49 bmc systemd[1]: Started Reboot Host 2 If Enabled.
May 09 18:18:49 bmc systemd[1]: Started Reboot Host 3 If Enabled.
May 09 18:18:49 bmc systemd[1]: Started Reboot Host 4 If Enabled.
May 09 18:18:49 bmc systemd[1]: Started Reboot Host 5 If Enabled.
May 09 18:18:49 bmc phosphor-discover-system-state[1206]: The LastbootCause is a watchdog. Power policy execution is currently allowed
May 09 18:18:49 bmc systemd[1]: Started Reboot Host 6 If Enabled.
May 09 18:18:49 bmc phosphor-discover-system-state[1207]: The LastbootCause is a watchdog. Power policy execution is currently allowed
May 09 18:18:49 bmc phosphor-discover-system-state[1206]: One time not set, check user setting of power policy
May 09 18:18:49 bmc phosphor-discover-system-state[1206]: Host power is off, processing power policy xyz.openbmc_project.Control.Power.RestorePolicy.Policy.AlwaysOn
May 09 18:18:49 bmc phosphor-discover-system-state[1206]: power_policy=ALWAYS_POWER_ON, powering host on (0s delay)
May 09 18:18:49 bmc phosphor-discover-system-state[1207]: One time not set, check user setting of power policy
May 09 18:18:50 bmc phosphor-discover-system-state[1208]: The LastbootCause is a watchdog. Power policy execution is currently allowed
May 09 18:18:50 bmc systemd[1]: Started Reboot Host 7 If Enabled.
May 09 18:18:50 bmc phosphor-discover-system-state[1207]: Host power is off, processing power policy xyz.openbmc_project.Control.Power.RestorePolicy.Policy.AlwaysOn
May 09 18:18:50 bmc phosphor-discover-system-state[1207]: power_policy=ALWAYS_POWER_ON, powering host on (0s delay)
May 09 18:18:50 bmc phosphor-discover-system-state[1209]: The LastbootCause is a watchdog. Power policy execution is currently allowed
May 09 18:18:50 bmc phosphor-discover-system-state[1208]: One time not set, check user setting of power policy
May 09 18:18:50 bmc phosphor-host-state-manager[994]: Host state transition request of xyz.openbmc_project.State.Host.Transition.On
....

```

Change-Id: Ic97c331d41af6b3ca5673e711107d475362c72c3
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

show more ...

phosphor-discover-system-state: improve service description

A multi-host system currently starts 8 instances of this service
with less than useful service descriptions. Improve the description
to i

phosphor-discover-system-state: improve service description

A multi-host system currently starts 8 instances of this service
with less than useful service descriptions. Improve the description
to include the host in question.

```
[ OK ] Started Reboot If Enabled.
[ OK ] Started Reboot If Enabled.
[ OK ] Started Reboot If Enabled.
[ OK ] Started Reboot If Enabled.
[ OK ] Started Reboot If Enabled.
[ OK ] Started Reboot If Enabled.
[ OK ] Started Reboot If Enabled.
[ OK ] Started Reboot If Enabled.
```

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

show more ...

bmc-ready: auto power restart function update

This service is responsible for executing the auto power restart logic
for the system. Prior to this change, it would run as a oneshot service
during th

bmc-ready: auto power restart function update

This service is responsible for executing the auto power restart logic
for the system. Prior to this change, it would run as a oneshot service
during the multi-user.target. This meant the BMC would not achieve
"Ready" state until after this service has completed.

With the recent changes to support not allowing a power on of the system
until the BMC is "Ready", we need to change this service so it is not
holding up that state change.

Systems that enable this new feature to only allow a power on when the
BMC is in a "Ready" state will need to ensure they have a non-zero
PowerRestoreDelay set for their system. This allows the service in this
commit to start, the BMC to get to "Ready" and then the power on request
to be made (if needed).

If in the future there's a need to enable this new feature and also have
a 0s delay, then this service will need to be enhanced to wait for BMC
"Ready".

Tested:
- Set policy to AlwaysOn, confirmed service started, BMC hit "Ready",
service waited 30s, and then issued power on without issue.

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

show more ...

update service file deps in accordance with recent refactoring

As noted in the following mailing list thread:
https://lists.ozlabs.org/pipermail/openbmc/2022-November/032457.html

and implemented vi

update service file deps in accordance with recent refactoring

As noted in the following mailing list thread:
https://lists.ozlabs.org/pipermail/openbmc/2022-November/032457.html

and implemented via this series of commits:
https://gerrit.openbmc.org/q/topic:op-power-control-ref

Some systemd services had their names changed. Update this service file
to reflect this.

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

show more ...

service-deps: add missing discover system state dep

The discover system state software makes d-bus calls to the settings
service and does not handle it missing in a graceful manner. Ensure the
setti

service-deps: add missing discover system state dep

The discover system state software makes d-bus calls to the settings
service and does not handle it missing in a graceful manner. Ensure the
setting service is running before starting this service.

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

show more ...

discover-system-state: add multi-host support

Add HostObjects class to fetch paths of settings d-bus objects under
/xyz/openbmc_project/control/hostX .

Signed-off-by: Potin Lai <potin.lai@quantatw.

discover-system-state: add multi-host support

Add HostObjects class to fetch paths of settings d-bus objects under
/xyz/openbmc_project/control/hostX .

Signed-off-by: Potin Lai <potin.lai@quantatw.com>
Change-Id: I1dc55ec389e94e6c85aa7031b304f8c4ed15dc71

show more ...

pinhole: no power restore policy on pinhole reset

If the user initiated a BMC reboot via the pinhole reset then do not run
the power restore policy. The pinhole reset is mostly used in debug
situati

pinhole: no power restore policy on pinhole reset

If the user initiated a BMC reboot via the pinhole reset then do not run
the power restore policy. The pinhole reset is mostly used in debug
situations where a system is having issues. Disabling the power restore
logic helps keep debug simpler.

Tested:
- The overall pinhole reset logic has not been tested on hardware.
- A variety of tests were done within simulation to validate the
different paths in this series of patches
- Full end to end testing will occur once all function is in place due
to the complexities of physically toggling the pinhole reset

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

show more ...

oneshot: discover-system-state: remain after exit

This service should only ever run once, after a BMC has first booted.
Ensure this is the case by setting RemainAfterExit to yes.

Signed-off-by: And

oneshot: discover-system-state: remain after exit

This service should only ever run once, after a BMC has first booted.
Ensure this is the case by setting RemainAfterExit to yes.

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

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 ...