tree d57f9961850bada1a00e563ff64bd1dc2a47a852
parent c0895627ee171360ad6737634ebd05894d263453
author Andrew Geissler <geissonator@yahoo.com> 1647879763 -0500
committer Andrew Geissler <andrew@geissonator.com> 1648133555 +0000

ensure bmc-state-manager stays in quiesce state

Unsubscribing from systemd signals only prevents signals if no other
service within OpenBMC is subscribed. This is never going to be the case
in OpenBMC so along with unsubscribing, also reset the object
responsible for the callbacks within bmc-state-manager.

This is to ensure that once bmc-state-manager enters Quiesced, it never
exits from it. Have seen on a few systems that the multi-user.target
generates some events during different boot tests, causing
bmc-state-manager to reset the state to Ready.

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