Queens Series (3.0.0 - 3.2.x) Release Notes

Queens Series (3.0.0 - 3.2.x) Release Notes

3.2.2-5

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.

3.2.2

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.2.0

New Features

  • Switched to lshw for memory configuration and system information collection when using the default hardware manager. This information can now be retrieved on both DMI capable and OpenFirmware capable systems. dmidecode is no longer used by the default hardware manager.

  • Adds DHCP network support for TinyIPA. This support is required for rescue feature when used with TinyIPA.

Upgrade Notes

  • lshw is now a dependency of the default hardware manager.

Bug Fixes

  • The default hardware manager is now capable of collecting memory configuration and system information on OpenFirmware (PowerPC) capable systems, in addition to the already supported DMI (x86 and ARM) capable systems.

3.1.0

New Features

  • Adds an extension to support rescue mode for a CoreOS-based ramdisk using DHCP for the tenant network.

  • Now passes an agent_version field to the Bare Metal service as part of the heartbeat request if the Bare Metal API version is 1.36 or higher. This provides the Bare Metal service with the information required to determine what agent features are available, so that the Bare Metal service can be upgraded to a new version before the agent is upgraded, whilst ensuring the Bare Metal service only requests the agent features that are available to it.

Bug Fixes

  • Fixes a bug in the LLDP discovery code that prevented reporting any LLDP information if an LLDP discovery raised an exception for one of the network interfaces. This could happen, for example, if a network interface incorrectly indicated its readiness for reading. See bug 1665025 for details.

  • Now correctly returns root_uuid as part of command status when provisioning a whole disk image using the direct deploy interface. See bug 1713916 for details.

  • Fixes the issue where link-local IP addresses were sometimes used as part of the callback URL given to ironic. The routable address is used instead. See bug 1732692 for more details.

3.0.0

New Features

  • Adds the new field by_path to disks in the inventory. Its value is the full device path, in the form /dev/disk/by-path/<rest-of-path>. With ironic-lib version 2.11 or newer it is possible to use this field in root device hints.

Upgrade Notes

  • Support for setting IPMI credentials during inspection was removed. This feature is not supported by ironic-inspector since the Pike release.

  • The ipmi_address field is no longer sent as part of the inspection process. The inventory[bmc_address] field should be used instead.

Bug Fixes

  • Uses the PATH environment variable to get the grub2 binary location instead of assuming it to be /usr/sbin. This fixes installing a boot loader when the grub2 binary is located somewhere else.

  • Fixes incorrect assumption that a valid channel cannot follow an invalid one in IPMI (bug 1714944).

  • If root device hints are provided on the node, wait for the root device instead of the first disk. This fixes deployment when the target disk takes time to load.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.