We joyfully announce the release of: ironic 21.1.2: OpenStack Bare Metal Provisioning This release is part of the zed stable release series. The source is available from: https://opendev.org/openstack/ironic Download the package from: https://tarballs.openstack.org/ironic/ Please report issues through: https://storyboard.openstack.org/#!/project/943 For more details, please see below. 21.1.2 ^^^^^^ Upgrade Notes ************* * Adds "sha256", "sha384" and "sha512" as supported SNMPv3 authentication protocols to iRMC driver. * "ipxe" boot_interface will be preferred to "irmc-pxe" by default with the "irmc" hardware type during the new baremetal node creation. This change doesn't affect to the existing baremetal nodes. Operators who want to continue to use "irmc-pxe" as default boot interface need to specify it in "[DEFAULT]default_boot_interface" setting in "ironic.conf". Bug Fixes ********* * Fixes bug in iRMC driver, where *irmc* power_interface sets and updates *irmc_ipmi_succeed* flag which is used by rest of iRMC driver code to deal with iRMC firmware's IPMI incompatibility but *ipmitool* power_interface doesn't set nor update *irmc_ipmi_succeed* flag and rest of iRMC driver code fail to handle iRMC firmware's IPMI incompatibility correctly. * Fixes an issue where a System Scoped user could not trigger a node into a "manageable" state with cleaning enabled, as the Neutron client would attempt to utilize their user's token to create the Neutron port for the cleaning operation, as designed. This is because with requests made in the "system" scope, there is no associated project and the request fails. Ironic now checks if the request has been made with a "system" scope, and if so it utilizes the internal credential configuration to communicate with Neutron. * Fixes the default boot interface order for the "irmc" hardware type where previously it would prefer "irmc-pxe" over "ipxe". This created inconsistencies for operators using multiple hardware types, where both interfaces were enabled in the deployment. Because the fix is backported on this point of releasae of Zed, operators who will update their environment beyond this release have to check the related upgrade note and take necessary action even though their update will be done in Zed release. * Fixes issues with Lenovo hardware where the system firmware may display a blue "Boot Option Restoration" screen after the agent writes an image to the host in UEFI boot mode, requiring manual intervention before the deployed node boots. This issue is rooted in multiple changes being made to the underlying NVRAM configuration of the node. Lenovo engineers have suggested to *only* change the UEFI NVRAM and not perform any further changes via the BMC to configure the next boot. Ironic now does such on Lenovo hardware. More information and background on this issue can be discovered in bug 2053064 (https://bugs.launchpad.net/ironic/+bug/2053064). Changes in ironic 21.1.1..21.1.2 -------------------------------- d853407fd CI: Lock Zed CI to Zed IPA 55330d372 stable only/ci: pin CI to dnsmasq 2.85/pin proliantutils/scciclient 47308caff Special case lenovo UEFI boot setup d4c3d0ad9 Fix system scoped manageable node network failure aae565bdc [iRMC] Fix IPMI incompatibility handling error cfddd47b1 Add support auth protocols for iRMC 8fd5268c1 Fix anaconda stage2_id loading from image properties e4d8c362f Change boot_interface order of iRMC driver Diffstat (except docs and test files) ------------------------------------- devstack/lib/ironic | 20 ++++++++++++---- devstack/plugin.sh | 1 + driver-requirements.txt | 7 ++++-- ironic/common/neutron.py | 6 ++++- ironic/common/pxe_utils.py | 3 ++- ironic/conf/irmc.py | 15 ++++++++++-- ironic/drivers/irmc.py | 4 ++-- ironic/drivers/modules/agent_base.py | 21 +++++++++++++++-- ironic/drivers/modules/irmc/common.py | 7 ++++-- ironic/drivers/modules/irmc/inspect.py | 12 +++++++--- ironic/drivers/modules/irmc/management.py | 18 ++++++++++----- ironic/drivers/modules/irmc/power.py | 7 ++++-- ironic/drivers/modules/pxe_base.py | 13 +++++++++++ ...atibility-patch-situation-c246d2b59b2e8a78.yaml | 8 +++++++ ...tem-scope-triggered-clean-22ada9b920c08365.yaml | 12 ++++++++++ ...c-add-snmp-auth-protocols-3ff7597cea7ef9dd.yaml | 5 ++++ ...ange-boot-interface-order-e76f5018da116a90.yaml | 19 +++++++++++++++ ...boot-to-disk-calls-lenovo-39763bfc98f602d8.yaml | 13 +++++++++++ zuul.d/project.yaml | 22 ++++++++++++++---- 23 files changed, 232 insertions(+), 35 deletions(-) Requirements updates -------------------- diff --git a/driver-requirements.txt b/driver-requirements.txt index 876e817cb..5c667388f 100644 --- a/driver-requirements.txt +++ b/driver-requirements.txt @@ -7 +7,4 @@ -proliantutils>=2.14.0 +# NOTE(TheJulia): Proliantutils 2.16.0 moves to pysnmp-lextudio +# however that breaks on imports and with testing due to collission +# with pysnmp. +proliantutils>=2.14.0,<2.16.0 @@ -9 +12 @@ pysnmp>=4.3.0,<5.0.0 -python-scciclient>=0.12.2 +python-scciclient>=0.12.2,<0.13.0