block-boot: define interface for d-bus object
Per the following design:
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/29603
This commit defines the D-Bus interface which will be a part
of the D-Bus object associated with the phosphor-logging event
preventing the boot of the system.
Change-Id: Ie2bc9c46f0e6db88dce2d5e6ac70eb71194af204
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/xyz/openbmc_project/Logging/ErrorBlocksTransition.interface.yaml b/xyz/openbmc_project/Logging/ErrorBlocksTransition.interface.yaml
new file mode 100644
index 0000000..656c75a
--- /dev/null
+++ b/xyz/openbmc_project/Logging/ErrorBlocksTransition.interface.yaml
@@ -0,0 +1,13 @@
+description: >
+ Empty interface to indicate that the associated `Logging.Entry` should
+ prevent a state transition of the associated managed element while the
+ `Logging.Entry` is not `Resolved` or been deleted.
+
+ The specific state transition(s) to prevent are left to the implementation.
+ A typical use of this would be to prevent the power-on of a
+ managed host while a critical error is open. The managed host, via
+ systemd transitions, might start the power-on sequence and then wait for
+ any object with this `ErrorBlocksTransition` interface to no longer be
+ instantiated. Causal ordering of D-Bus operations can prove that
+ no critical error needs servicing and the power-on sequence may safely
+ continue.