Resending (plain text): [DISCUSSION] Policy for handling ObjectMapper stop: reboot BMC and refuse manual stop

[Eric Yang]

Apologies for missing Reply-All earlier — resending.

> Hmm.  Don't we already have phosphor-systemd-target-monitor that
> identifies critical services, collects a BMC crashdump if they fail, and
> then enters a "Quiesced" state?  If someone wants the BMC to restart, as
> optional policy, can't they just insert that as a dependency on the
> Quiesced target?

I’ll look into phosphor-systemd-target-monitor and work on marking
ObjectMapper as a critical unit so that failures trigger a BMC dump
and a transition to obmc-quiesce.target. It looks like both the
optional reboot tied to Quiesced and the manual-stop blocking policy
belong in meta-phosphor.

> I don't want to see a one-off event for "object manager crashed".  I
> think that it would be more reasonable to have an event for "BMC went
> into Quiesced state" and the reason why, which isn't really interesting
> for anyone except BMC developers, can be figured out from the
> corresponding BMC crashdump.

Understood. I’ll check whether we already emit an event when the BMC
enters Quiesced and whether it can capture a coredump-derived cause;
if not, I’ll try to add one.

Best regards,
Eric Yang