tree 6bc77444311e85758ae8798ea50931b2d2d9a1f4
parent 2774c788571083327139baafc3e001c6690172ed
author Andrew Geissler <geissonator@yahoo.com> 1645201275 -0600
committer Andrew Geissler <andrew@geissonator.com> 1645817051 +0000

crit-service: check for bmc quiesce on startup

If the new bmc-bmc-service-quiesce target is entered, then change the
BMC state to Quiesced and do not allow it to change until the BMC is
rebooted out of the failure.

Tested:
- Installed new code on system and started target-monitor with new
  critical services json file as input. Verified that when a critical
  service was killed three times within quick succession, the service
  went into a failed state, the target-monitor detected it, and BMC went
  to Quiesced state.
- Restarted bmc-state manager application while BMC was in Quiesced
  state and verified it rediscovered that upon restart.

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