Rocky Series (3.3.0 - 3.3.x) Release Notes

3.3.2-3

Bug Fixes

  • The lshw output no longer pollutes the debug logging. Instead, it’s stored as part of the ramdisk logs.

3.3.2

Bug Fixes

  • From IPMI specification v2.0, channel number 1-Bh(1-11) can be used for various types of communications channels. The respectively available channels depend on the specific IPMI implementation for a specific server system.

  • Mounts /run into chroot when installing grub to prevent timeouts.

  • Fixes an issue with retrieving all available physical memory. For more details see: story 2005308 <https://storyboard.openstack.org/#!/story/2005308>

3.3.1

Bug Fixes

  • Fixes detection of IPMI address in CoreOS-based images, by ensuring that parsing of ipmitool output is compatible with the bundled implementation of awk (mawk).

3.3.0

New Features

  • Adds the ability for the Bare Metal service conductor service to explicitly choose to disable ATA Secure Erase from being executed.

  • If a PReP boot partition is created, and the machine being deployed to is of ppc64le architecture, the grub2 bootloader will be installed directly there. This enables booting partition images locally on ppc64* hardware.

    Using this feature requires ironic-lib version 2.14 as support to create the PReP partition was introduced there.

Bug Fixes

  • Adds an additional check if the smartctl utility is present from the smartmontools package, which performs an ATA disk specific check that should prevent ATA Secure Erase from being performed if a pass-thru device is detected that requires a non-ATA command signling sequence. Devices such as these can be smart disk interfaces such as RAID controllers and USB disk adapters, which can cause failures when attempting to Secure Erase, which may render the disk unreachable.

  • Fixes the ATA Secure Erase logic to attempt an immediate unlock in the event of a failed attempt to Secure Erase. This is required to permit fallback to make use of the shred disk utility.

    In the event that an ATA Secure Erase operation fails during cleaning, the disk will be write locked. In this case, the disk must be explicitly unlocked.

    This should also prevent failures where an ATA Secure Erase operation fails with a pass-through disk controller, which may prevent the disk from being available after a reboot operation. For additional information, please see story 2002546.

  • Fixes an issue where the secure erase cleaning step would fail if a drive was left in the security-enabled state. This could occur if a previous attempt to perform a secure erase had failed e.g if there was a power failure mid-way through the cleaning proccess. See Story 2001762 and Story 2001763 for details.

  • Adds support to collect the default IPv6 address for interfaces. With different networking environment, the address could be a link-local address, ULA or something else.

  • Fixes bug where TinyIPA fails to acquire IP address when in RESCUE state and in multi-tenant environment.