tree a15152f3d705ba55d9b23c914cbc68d8ec909563
parent c568ac1a7a58381b77622f0fdd991fcd6f0291be
author Andrew Geissler <geissonator@yahoo.com> 1704288585 -0600
committer Andrew Geissler <geissonator@yahoo.com> 1704484554 -0600

scheduled-host: handle bmc-not-ready error

The BMC Ready feature introduced a new d-bus error when a power on
request is made and the BMC is not at a Ready state.

If someone were to utilize the scheduled transition feature in a way
where they set it to some time in the future, powered their BMC off, and
then powered back on at some later time past the scheduled time, then
the scheduling function will try and start a power on immediately.

This power on would occur prior to the BMC being at Ready, resulting in
the error being returned and the scheduling service failing. Handle the
error during the initialization phase of the service by rescheduling the
operation 60s into the future.

Tested:
- Verified that when BMC was not at Ready state that error was handled
  correctly, 60s delay was added on to power on request, and 60s later
  it worked successfully.

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