)]}'
{"releasenotes/notes/bmc-stability-validation-after-bmc-only-f42394895246e4ec.yaml":[{"author":{"_account_id":32177,"name":"Jacob Anders","email":"jacob-anders-dev@proton.me","username":"janders"},"change_message_id":"5cf1ca3816532ba2c95801a54a8276a0232768a0","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The BMC resource stability validation that follows a Redfish firmware"},{"line_number":5,"context_line":"    update -- repeated reads of ``System``, ``Manager`` and the chassis"},{"line_number":6,"context_line":"    ``NetworkAdapters`` until"},{"line_number":7,"context_line":"    ``[redfish]firmware_update_required_successes`` consecutive reads"},{"line_number":8,"context_line":"    succeed -- now runs only after a BMC firmware update, the case it was"},{"line_number":9,"context_line":"    written for, where the BMC\u0027s own web service can answer and then drop"},{"line_number":10,"context_line":"    out again while the new image comes up. After a reboot applying any"},{"line_number":11,"context_line":"    other firmware the BMC never reset, and the Lifecycle Controller job"},{"line_number":12,"context_line":"    and ``BootProgress`` checks gating that reboot have just read from it,"},{"line_number":13,"context_line":"    so the validation added its full duration -- by default three"},{"line_number":14,"context_line":"    successful rounds at ``[redfish]firmware_update_validation_interval``"},{"line_number":15,"context_line":"    apart, about a minute -- to every such update without proving"},{"line_number":16,"context_line":"    anything new."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"4c421f67_00326eea","line":16,"range":{"start_line":2,"start_character":0,"end_line":16,"end_character":17},"updated":"2026-09-17 04:55:18.000000000","message":"simplify, bring in line with existing release notes","commit_id":"1278219d76e714477ddaada16f0464391f95a321"},{"author":{"_account_id":32177,"name":"Jacob Anders","email":"jacob-anders-dev@proton.me","username":"janders"},"change_message_id":"fc6dfaf631b7dc77c10f94063f9f9569b4a29df1","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"fixes:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The BMC resource stability validation that follows a Redfish firmware"},{"line_number":5,"context_line":"    update -- repeated reads of ``System``, ``Manager`` and the chassis"},{"line_number":6,"context_line":"    ``NetworkAdapters`` until"},{"line_number":7,"context_line":"    ``[redfish]firmware_update_required_successes`` consecutive reads"},{"line_number":8,"context_line":"    succeed -- now runs only after a BMC firmware update, the case it was"},{"line_number":9,"context_line":"    written for, where the BMC\u0027s own web service can answer and then drop"},{"line_number":10,"context_line":"    out again while the new image comes up. After a reboot applying any"},{"line_number":11,"context_line":"    other firmware the BMC never reset, and the Lifecycle Controller job"},{"line_number":12,"context_line":"    and ``BootProgress`` checks gating that reboot have just read from it,"},{"line_number":13,"context_line":"    so the validation added its full duration -- by default three"},{"line_number":14,"context_line":"    successful rounds at ``[redfish]firmware_update_validation_interval``"},{"line_number":15,"context_line":"    apart, about a minute -- to every such update without proving"},{"line_number":16,"context_line":"    anything new."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"858f4b13_98a69949","line":16,"range":{"start_line":2,"start_character":0,"end_line":16,"end_character":17},"in_reply_to":"4c421f67_00326eea","updated":"2026-09-17 06:33:49.000000000","message":"Done","commit_id":"1278219d76e714477ddaada16f0464391f95a321"}]}