Go to file
Iury Gregory Melo Ferreira 2411779ee8 Handle unresponsive BMC during Firmware Updates
When doing firmware updates for BMC, we saw cases where Ironic wouldn't
be able to contact the BMC, marking the node in a failed state because
of it.
This patch adds a configuration option that tell for how long ironic
should wait before proceeding with the reboot to finish the update.
We will attempt to improve the waiting time in a follow-up, trying
to identify when the bmc was unresponsive and when it was back.

Closes-Bug: #2092398

Change-Id: I53ffc8a06d5af8b0751553c3d4a9bb1c000027ae
Signed-off-by: Iury Gregory Melo Ferreira <imelofer@redhat.com>
2025-07-01 08:45:28 -03:00
2024-01-08 18:02:27 +01:00
2024-02-02 23:17:12 +09:00
2019-04-19 19:40:53 +00:00
2020-04-13 07:29:37 -07:00
2025-03-02 22:27:33 +00:00
2013-05-02 14:55:43 -04:00
2025-05-05 22:35:29 +00:00
2025-06-17 13:23:36 +00:00

Ironic

image

Overview

Ironic consists of an API and plug-ins for managing and provisioning physical machines in a security-aware and fault-tolerant manner. It can be used with nova as a hypervisor driver, or standalone service using bifrost. By default, it will use PXE and IPMI to interact with bare metal machines. Ironic also supports vendor-specific plug-ins which may implement additional functionality.

Ironic is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.

Project resources

Project status, bugs, and requests for feature enhancements (RFEs) are tracked in Launchpad: https://launchpad.net/ironic

For information on how to contribute to ironic, see https://docs.openstack.org/ironic/latest/contributor

Description
A service for managing and provisioning Bare Metal servers.
Readme 326 MiB
Languages
Python 97.8%
Shell 2%