Yoga Series (19.0.0 - 20.1.x) Release Notes¶
Modify iRMC driver to use ironic.conf [deploy] default_boot_mode to determine default boot_mode.
sha512as supported SNMPv3 authentication protocols to iRMC driver.
Fixes Ironic integration with Cinder because of changes which resulted as part of the recent Security related fix in bug 2004555. The work in Ironic to track this fix was logged in bug 2019892. Ironic now sends a service token to Cinder, which allows for access restrictions added as part of the original CVE-2023-2088 fix to be appropriately bypassed. Ironic was not vulnerable, but the restrictions added as a result did impact Ironic’s usage. This is because Ironic volume attachments are not on a shared “compute node”, but instead mapped to the physical machines and Ironic handles the attachment life-cycle after initial attachment.
When aborting cleaning, the
last_errorfield is no longer initially empty. It is now populated on the state transition to
When cleaning or deployment fails, the
last_errorfield is no longer temporary set to
Nonewhile the power off action is running.
Fixes an issue where if selinux is enabled and enforcing, and the published image is a hardlink, the source selinux context is preserved, causing access denied when retrieving the image using hardlink URL.
Fixes bug of iRMC driver in parse_driver_info where, if FIPS is enabled, SNMP version is always required to be version 3 even though iRMC driver’s xxx_interface doesn’t use SNMP actually.
'NoneType' object is not iterablein conductor logs for
idrac-redfishRAID clean and deploy steps. The message should no longer appear. For affected nodes re-create the node or delete
Fixes an issue in the online upgrade logic where database models for Node Traits and BIOS Settings resulted in an error when performing the online data migration. This was because these tables were originally created as extensions of the Nodes database table, and the schema of the database was slightly different enough to result in an error if there was data to migrate in these tables upon upgrade, which would have occured if an early BIOS Setting adopter had data in the database prior to upgrading to the Yoga release of Ironic.
The online upgrade parameter now subsitutes an alternate primary key name name when applicable.
Fixes SNMPv3 message authentication and encryption functionality of iRMC driver. The SNMPv3 authentication between iRMC driver and iRMC was only by the security name with no passwords and encryption. To increase security, the following parameters are now added to the node’s
driver_info, and can be used for authentication:
irmc_snmp_auth_proto(Optional, defaults to
irmc_snmp_priv_proto(Optional, defaults to
irmc_snmp_securitywill be ignored if
irmc_snmp_priv_protocan also be set through the following options in the
Fixes a race condition in PXE initialization where logic to retry what we suspect as potentially failed PXE boot operations was not consulting if an
agent tokenhad been established, which is the very first step in agent initialization.
Fixes an issue where an agent token was being orphaned if a baremetal node timed out during cleaning operations, leading to issues where the node would not be able to establish a new token with Ironic upon future in some cases. We now always wipe the token in this case.
Updates the minimum version of
jsonschema4.0.0 or newer, make sure to include a proper
$schemafield in your custom network data or RAID schemas.
irmchardware type to include a capability to control enforcement of HTTPS certificate verification. By default this is enforced. python-scciclient version must be one of >=0.8.2,<0.9.0, >=0.9.4,<0.10.0, >=0.10.1,<0.11.0, >=0.11.3,<0.12.0 or >=0.12.0,<0.13.0 Or certificate verification will not occur.
Fixes detecting of allowable values for a BIOS settings enumeration in the
redfishBIOS interface when only
ironicexecutable now starts the API only after the built-in conductor starts. This avoids error 500 on requests while the conductor is starting.
Fixes an issue where a conductor would attempt local takeover. In case of heartbeat failure due to resource starvation, the current conductor was detected as offline when querying the database. In this scenario the conductor would forcibly remove reservations of it’s own and initiate takeover. Current conductor is now excluded from the list of offline conductors, so that local takeover does not occur for this case. A warning is logged to highlight the potential resource starvation issue. See bug: 2010016.
Fixes rebooting into the agent after changing BIOS settings in fast-track mode with the
redfish-virtual-mediaboot interface. Previously, the ISO would not be configured.
OSError: [Errno 36] File name too longwhen building a virtual media ISO from a long kernel, ramdisk or ESP URL.
delete_configurationclean and deploy steps to update node’s
raid_configfield at the end of the steps.
bootinterface to allow it with iDRAC firmware from 6.00.00.00 (released June 2022) as it has virtual media boot issue fixed that prevented iDRAC firmware to work with
redfish-virtual-mediabefore. Consider upgrading iDRAC firmware if not done already, otherwise will still get an error when trying to use
driver_info/irmc_verify_caoption to specify certification file. Default value of driver_info/irmc_verify_ca is True.
Fix a bug when configuring RAID caused by not converting the port value to int type when the node managed by the irmc hardware type.
Fixes API error messages with jsonschema>=4.8. A possible root cause is now detected for generic schema errors.
Fixes compatibility with
jsonschemapackage version 4.0.0 or newer by providing a proper schema version (Draft-07 currently).
ramdiskdeploy interface is used and automated cleaning is disabled, the
redfish-virtual-mediaboot interfaces no longer require a deploy kernel/ramdisk to be provided.
Fixes an issue where the Redfish session cache would continue using an old session when a password for a Redfish BMC was changed. Now the old session will not be found in this case, and a new session will be created with the latest credential information available.
Resolved clear_job_queue and reset_idrac verify step failures which occur when the functionality is not supported by the iDRAC. When this condition is detected, the code in the step handles the exception and logs a warning and completes successfully in case of verification steps but fails in case of cleaning steps.
Known issue when using iDRAC with Swift to stage firmware update files in Management interface
firmware_updateclean step of
idrachardware type has been fixed in iDRAC firmware 6.00.00.00. Upgrade when possible or use HTTP service to stage firmware files for iDRAC.
The Ironic community is pleased to announce the release of Ironic 20.1.
During the Yoga cycle, we had forty-three contributors. They are responsible for more than 35,000 lines of code and more than twenty new features that will improve the experience of our end-users! Please reach out to our community if you have any questions or feedback!
firmware_updateclean step adds Swift, HTTP service and file system support to serve and Ironic’s HTTP and Swift service to stage files. Also adds mandatory parameter
checksumfor file checksum verification.
Adds support for
idrac-wsmanRAID, BIOS and management clean steps to be run without IPA when disabling ramdisk during cleaning.
Supports listening on a Unix socket instead of a normal TCP socket. This is useful with an HTTP server such as nginx in proxy mode.
When using iDRAC with Swift to stage firmware update files in Management interface
firmware_updateclean step of
idrachardware type, the cleaning fails with error “An internal error occurred. Unable to complete the specified operation.” in iDRAC job. Until this is fixed, use HTTP service to stage firmware files for iDRAC.
firmware_updateclean step there is now mandatory
checksumparameter necessary. Update existing clean steps to include it, otherwise clean step will fail with error “‘checksum’ is a required property”.
Booting final instances via network (as opposed to via a local bootloader) is now deprecated, except for the cases of booting from volume or the ramdisk deploy interface.
Network boot for whole disk images only works reliable for legacy (BIOS) boot. In case of partition images, there is no way to update the kernel, which makes this approach insecure.
Users of partition images must ensure that they either contain the
grub-installbinary, enough EFI artifacts to boot the operating system or a legacy boot partition.
The anaconda deploy interface was treating the config drive as a dict, whereas it could be a dict or in iso6600 format, gzipped and base64-encoded. This has been fixed.
The anaconda deploy interface was adding commands that deal with the config drive, to the end of the kickstart config file. Which means that they are handled after an ironic API request is sent (to the conductor) to indicate that the node has been provisioned and is ready to be rebooted. Which means that there is a possible race condition wrt these commands being completed before the node is powered off. A sync is added to ensure that all modifications have been written to disk, before the API request is sent – as the last thing.
Extra newlines (’n’) were incorrectly added to the user data content. This broke the content-type decoding and cloud-init was unable to proces them. The extra newlines have been removed.
Fixes the logic for the anaconda deploy interface. If the ironic node’s instance_info doesn’t have both ‘stage2’ and ‘ks_template’ specified, we weren’t using the instance_info at all. This has been fixed to use the instance_info if it was specified. Otherwise, ‘stage2’ is taken from the image’s properties (assumed that it is set there). ‘ks_template’ value is from the image properties if specified there (since it is optional); else we use the config setting ‘[anaconda] default_ks_template’.
For the anaconda deploy interface, the ‘stage2’ directory was incorrectly being created using the full path of the stage2 file; this has been fixed.
The anaconda deploy interface expects the node’s instance_info to be populated with the ‘image_url’; this is now populated (via PXEAnacondaDeploy’s prepare() method).
For the anaconda deploy interface, when the deploy was finished and the bm node was being rebooted, the node’s provision state was incorrectly being set to ‘active’ – the provisioning state-machine mechanism now handles that.
For the anaconda deploy interface, the code that was doing the validation of the kickstart file was incorrect and resulted in errors; this has been addressed.
For the anaconda deploy interface, the ‘%traceback’ section in the packaged ‘ks.cfg.template’ file is deprecated and fails validation, so it has been removed.
The anaconda deploy interface was saving internal information in the node’s
instance_info, in the user-facing
ks_templatefields. This broke rebuilds using a different image with different
stage2or template specified in the image properties. This has been fixed by saving the information in the node’s
redfishhardware type RAID device creation and deletion when creating or deleting more than 1 logical disk on RAID controllers that require rebooting and do not allow more than 1 running task per RAID controller. Before this fix 2nd logical disk would fail to be created or deleted. With this change it is now possible to use
raidinterface on iDRAC systems.