docs/designs/fail-boot-on-hw-error.md

52   - The chassis/host instance pair will not be allowed to power on until the log
54     - A BMC reset will clear this power on prevention
57   - These causes will be defined within the extensions documentation
60 **Special Note:** Initially the associated host and chassis will be hard coded
69 called QuiesceOnHwError. This property will be hosted under the
72 Define a new D-Bus interface which will indicate an error has been created which
73 will prevent the boot of a chassis/host instance:
76 This interface will be hosted under a instance based D-Bus object
80 When an error is created via a phosphor-logging interface, the software will
81 check to see if the error has a callout, and if so it will check the new
83 phosphor-logging will create a `/xyz/openbmc_project/logging/blockX` D-Bus
86 will be created. The corresponding host instance will be put in quiesce by
96 A new `obmc-host-graceful-quiesce@.target` systemd target will be started. This
97 new target will ensure a graceful shutdown of the host is initated and then
98 start the `obmc-host-quiesce@.target` which will stop the host and move the host
101 obmcutil will be enhanced to look for these block interfaces and notify the user
128 This will require some additional checking on reported logs but should have
131 There will be no changes to system behavior unless a user turns on this new
136 Unit tests will be run to ensure logic to detect errors with logs and verify
139 Test cases will need to look for this new blocking D-Bus object and handle