xref: /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ErrorBlocksTransition.interface.yaml (revision a1347418307d31a94bd21f22897aa508df938dcf)
  • Home
  • History
  • Annotate Annotate
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1b1b4d261SWilliam A. Kennington IIIdescription: >
2b1b4d261SWilliam A. Kennington III    Empty interface to indicate that the associated `Logging.Entry` should
3b1b4d261SWilliam A. Kennington III    prevent a state transition of the associated managed element while the
4b1b4d261SWilliam A. Kennington III    `Logging.Entry` is not `Resolved` or been deleted.
5b1b4d261SWilliam A. Kennington III
6b1b4d261SWilliam A. Kennington III    The specific state transition(s) to prevent are left to the implementation.
7*a1347418SPatrick Williams    A typical use of this would be to prevent the power-on of a managed host
8*a1347418SPatrick Williams    while a critical error is open.  The managed host, via systemd transitions,
9*a1347418SPatrick Williams    might start the power-on sequence and then wait for any object with this
10*a1347418SPatrick Williams    `ErrorBlocksTransition` interface to no longer be instantiated.  Causal
11*a1347418SPatrick Williams    ordering of D-Bus operations can prove that no critical error needs
12*a1347418SPatrick Williams    servicing and the power-on sequence may safely continue.
13

served by {OpenGrok

Last Index Update: Sun May 18 03:01:11 CDT 2025