We are satisfied to announce the release of: ironic 11.1.1: OpenStack Bare Metal Provisioning This release is part of the rocky stable release series. The source is available from: https://git.openstack.org/cgit/openstack/ironic Download the package from: https://tarballs.openstack.org/ironic/ Please report issues through launchpad: https://storyboard.openstack.org/#!/project/943 For more details, please see below. 11.1.1 ^^^^^^ New Features ************ * Setting these configuration options to 0 will disable the periodic tasks: * [conductor]sync_power_state_interval: sync power states for the nodes * [conductor]check_provision_state_interval: * check deployments and time out if the deployment takes too long * check the status of cleaning a node and time out if it takes too long * check the status of inspecting a node and time out if it takes too long * check for and handle nodes that are taken over by new conductors (if an old conductor disappeared) * [conductor]send_sensor_data_interval: send sensor data to ceilometer * [conductor]sync_local_state_interval: refresh a conductor's copy of the consistent hash ring. If any mappings have changed, determines which, if any, nodes need to be "taken over". The ensuing actions could include preparing a PXE environment, updating the DHCP server, and so on. * [oneview]periodic_check_interval: * check for nodes taken over by OneView users * check for nodes freed by OneView users Known Issues ************ * Building RAID1 is known to not work with Dell BOSS cards using **python-dracclient** 1.4.0 or earlier. Upgrade to **python- dracclient** 1.5.0 to use this feature. Upgrade Notes ************* * The "hash_ring_reset_interval" configuration option was changed from 180 to 15 seconds. Previously, this option was essentially ignored on the API side, becase the hash ring was reset on each API access. The lower value minimizes the probability of a request routed to a wrong conductor when the ring needs rebalancing. * If you are doing a minor version upgrade, please re-run the "ironic- dbsync online_data_migrations" command to properly update the versions of the Objects in the database. Otherwise, the next major upgrade may fail. Critical Issues *************** * The "ironic-dbsync online_data_migrations" command was not updating the objects to their latest versions, which could prevent upgrades from working (i.e. when running the next release's "ironic- dbsync upgrade"). Objects are updated to their latest versions now when running that command. See story 2004174 (https://storyboard.openstack.org/#!/story/2004174) for more information. Bug Fixes ********* * Fixes an issue with a baremetal node that times out during cleaning. The ironic-conductor was attempting to change the node's provision state to 'clean failed' twice, resulting in the node's "last_error" being set incorrectly. This no longer happens. For more information, see story 2004299 (https://storyboard.openstack.org/#!/story/2004299). * Fixes an issue where setting these configuration options to 0 caused a ValueError exception to be raised. You can now set them to 0 to disable the associated periodic tasks. (For more information, see story 2002059 (https://storyboard.openstack.org/#!/story/2002059).): * [conductor]sync_power_state_interval: sync power states for the nodes * [conductor]check_provision_state_interval: * check deployments and time out if the deployment takes too long * check the status of cleaning a node and time out if it takes too long * check the status of inspecting a node and time out if it takes too long * check for and handle nodes that are taken over by new conductors (if an old conductor disappeared) * [conductor]send_sensor_data_interval: send sensor data to ceilometer * [conductor]sync_local_state_interval: refresh a conductor's copy of the consistent hash ring. If any mappings have changed, determines which, if any, nodes need to be "taken over". The ensuing actions could include preparing a PXE environment, updating the DHCP server, and so on. * [oneview]periodic_check_interval: * check for nodes taken over by OneView users * check for nodes freed by OneView users * Fixes an issue where Neutron ports would be left with a baremetal MAC address associated after an instance is deleted from a baremetal host. This caused problems with MAC address conflicts in follow up deployments to the same baremetal host. bug 2004428 (https://storyboard.openstack.org/#!/story/2004428). * Fixes an issue where a flat Neutron port would be left with a host ID associated with it after an instance is deleted from a baremetal host. This caused problems with reusing the same port for a new instance as it is already bound to the old instance. * Fixes a bug where the number of CPU sockets was being returned by the "idrac" hardware type during introspection, instead of the number of virtual CPUs. See bug 2004155 (https://storyboard.openstack.org/#!/story/2004155) for details. * Fixes a race condition in the hash ring implementation that could cause an internal server error on any request. See story 2003966 (https://storyboard.openstack.org/#!/story/2003966) for details. * Properly reports an error when the image cache and the image HTTP or TFTP location are on different file system, causing hard link to fail. * Fixes an issue where iSCSI based deployments fail if the "cpu_arch" property is not specified on a node. * Fixes "redfish" hardware type to reuse HTTP session tokens when talking to BMC using session authentication. Prior to this fix "redfish" hardware type never tried to reuse session token given out by BMC during previous connection what may sometimes lead to session pool exhaustion with some BMC implementations. * Fixes an issue wherein provisioning fails if ironic node is configured with "ramdisk" deploy interface. See bug 2003532 (https://storyboard.openstack.org/#!/story/2003532) for more details. * The IPMI hardware type unconditionally instructed the BMC to not automatically clear boot flag valid bit if Chassis Control command not received within 60-second timeout (countdown restarts when a Chassis Control command is received). Some BMCs do not support setting this; if sent it causes the boot to be aborted instead. For IPMI hardware type a new driver option "node['driver_info']['ipmi_disable_boot_timeout']" can be specified. It is "True" by default; set it to "False" to bypass sending this command. See story 2004266 (https://storyboard.openstack.org/#!/story/2004266) for additional information. Changes in ironic 11.1.0..11.1.1 -------------------------------- f55ae7e [Stable Only] rename ipmi_disable_timeout to ipmi_disable_boot_timeout ff62296 Cap the maximum microversion for stable/rocky bf05501 Avoid cpu_arch None values in iscsi deployments 357375f Ensure we unbind flat network ports and clear BM mac addresses 1980d32 Add ipmi_disable_timeout to avoid problematic IPMI command 6550d48 Don't fail when node is in CLEANFAIL state d156ad3 Increase RAM for the ironic node in UEFI job 6ff4419 Improve logs when hard linking images fails 2fbe323 Reuse Redfish sessions b389cb4 Fix CPU count returned by introspection in Ironic iDRAC driver 47fc51d Migration step to update objects to latest version 4763762 Fixes a race condition in the hash ring code 931e97b Disable periodic tasks if interval set to 0 021e631 Add admin documentation for rescue mode in iLO driver 4167083 Add admin documentation for rescue interface 9b0d5fe Remove wrong install-guide-jobs in zuul setup f1e7f95 Add a more detailed release note for Dell BOSS RAID1 fix 65ab326 Fix provisioning failure with `ramdisk` deploy interface 377a4ab import zuul job settings from project-config 068e23e Update UPPER_CONSTRAINTS_FILE for stable/rocky a0686d5 Update .gitreview for stable/rocky Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + .../source/samples/driver-property-response.json | 1 + devstack/lib/ironic | 2 +- ironic/cmd/dbsync.py | 5 + ironic/common/hash_ring.py | 34 +++++- ironic/common/neutron.py | 35 ++++++- ironic/conductor/manager.py | 34 ++++-- ironic/conductor/rpcapi.py | 13 ++- ironic/conductor/utils.py | 8 +- ironic/conf/conductor.py | 10 +- ironic/conf/default.py | 6 +- ironic/conf/drac.py | 1 + ironic/db/api.py | 15 +++ ironic/db/sqlalchemy/api.py | 80 ++++++++++++++ ironic/drivers/modules/drac/inspect.py | 15 ++- ironic/drivers/modules/image_cache.py | 11 ++ ironic/drivers/modules/ipmitool.py | 35 +++++-- ironic/drivers/modules/iscsi_deploy.py | 7 +- ironic/drivers/modules/network/common.py | 1 + ironic/drivers/modules/network/flat.py | 67 ++++++++++-- ironic/drivers/modules/oneview/deploy.py | 6 +- ironic/drivers/modules/pxe.py | 69 ++++++------ ironic/drivers/modules/redfish/utils.py | 57 ++++++++-- .../unit/drivers/modules/drac/test_inspect.py | 24 ++++- .../unit/drivers/modules/network/test_flat.py | 81 +++++++++++--- .../unit/drivers/modules/network/test_neutron.py | 10 +- .../unit/drivers/modules/redfish/test_utils.py | 64 +++++++++++- .../unit/drivers/modules/test_agent_base_vendor.py | 17 +-- .../unit/drivers/modules/test_iscsi_deploy.py | 9 ++ .../cleanwait_timeout_fail-4323ba7d4d4da3e6.yaml | 8 ++ .../notes/dell-boss-raid1-ec33e5b9c59d4021.yaml | 6 ++ .../disable_periodic_tasks-0ea39fa7a8a108c6.yaml | 49 +++++++++ ...-flat-vifs-and-clear-macs-34eec149618e5964.yaml | 13 +++ .../notes/fix-cpu-count-8904a4e1a24456f4.yaml | 7 ++ .../notes/hash-ring-race-da0d584de1f46788.yaml | 13 +++ ...invalid_cross_device_link-7ecf3543a8ada09f.yaml | 5 + .../iscsi-optional-cpu-arch-ebf6a90dde34172c.yaml | 6 ++ ...migration_update_versions-ea03aff12d9c036f.yaml | 13 +++ .../persist-redfish-sessions-d521a0846fa45c40.yaml | 8 ++ .../notes/ramdisk-boot-fails-4e8286e6a4e0dfb6.yaml | 7 ++ .../notes/story-2004266-4725d327900850bf.yaml | 13 +++ tox.ini | 10 +- zuul.d/ironic-jobs.yaml | 1 + zuul.d/project.yaml | 12 +++ 57 files changed, 1217 insertions(+), 167 deletions(-)