openstack/kayobe-config-dev
Code Issues Proposed changes

ironic: use ipmitool retries

Browse Source 
In Ubuntu baremetal CI testing, we saw issues with IPMI commands
failing, resuling in job failures:

  Error setting Chassis Boot Parameter 5

A metal3.io commit [1] was found that fixes the issue by moving IPMI
retries from ironic to ipmitool, which has a side-effect of increasing
the timeout. This change applies the same configuration.

[1] 6bc1499d8b

Change-Id: Ib4fce74cebebe85c31049eafe2eeb6b28dfab041
This commit is contained in:
Mark Goddard 2022-02-14 09:11:29 +00:00
parent da6623c084
commit 8b618b7e5a
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
etc/kayobe/kolla/config/ironic.conf
View File

@ -4,3 +4,25 @@ minimum_required_memory = 256
[deploy] [deploy]
# Use bios boot mode until Tenks supports UEFI # Use bios boot mode until Tenks supports UEFI
default_boot_mode = bios default_boot_mode = bios
# This IPMI configuration has been taken from the metal3.io ironic-image
# project. It is necessary to make IPMI reliable in Kayobe Ubuntu CI jobs.
# Without this, we saw the following error:
# Error setting Chassis Boot Parameter 5
# https://github.com/metal3-io/ironic-image/commit/6bc1499d8bb04c2c859b970b3739c3a8ed66ae2a
[ipmi]
# use_ipmitool_retries transfers the responsibility of retrying to ipmitool
# when supported. If set to false, then ipmitool is called as follows :
# $ipmitool -R 1 -N 1 ...
# and Ironic handles the retry loop.
use_ipmitool_retries = true
# The following parameters are the defaults in Ironic. They are used in the
# following way if use_ipmitool_retries is set to true:
# $ipmitool -R <X> -N <Y> ...
# where :
# X = command_retry_timeout / min_command_interval
# Y = min_command_interval
# If use_ipmitool_retries is false, then ironic retries X times, with an
# interval of Y in between each tries.
min_command_interval = 5
command_retry_timeout = 60