Stein Series (8.1.0 - 8.2.x) Release Notes¶
Makes the way ironic-inspector creates an ironic client compatible with future (post-Stein) versions of ironicclient.
No longer fails introspection if memory or CPU information is not provided in the inventory. These are no longer required for scheduling, introspection should not require them either.
Fixes an issue when extra_hardware plugin failed to save extra hardware information to Swift, the collected information is not processed and consumed.
Fixes an issue while mapping port InfiniBand MAC address to EthernetOverInfiniBand MAC. Prior to this fix, it will fail to map and raise an exception.
Fixes insufficient input filtering when looking up a node by information from the introspection data. It could potentially allow SQL injections via the
/v1/continueAPI endpoint. See story 2005678 for details.
The Stein release of ironic-inspector features support of storing introspection data in the database instead of the Object Store service, as well as fixes for IPv6.
Adds the support to store introspection data in ironic-inspector database. Set the option
databaseto use this feature.
Adds a migration tool
ironic-inspector-migrate-datato facilitate the introspection data migration between supported introspection data storage backends. Currently the available introspection data storage backends are:
swift. For example, to migrate existing introspection data stored in the swift to database, execute following command:
$ ironic-inspector-migrate-data --from swift --to database --config-file /etc/ironic-inspector/inspector.conf
Storage backends involved in the migration should have been properly configured in the ironic inspector configuration file. Before the introspection data migration can be started. The ironic inspector database should be upgraded to have the latest schema.
Adds support to use
latestas the microversion value in the request to the ironic-inspector API.
set-attributeaction now automatically sets
Trueif the driver is updated. If it’s not desired, set it explicitly to
Deprecates the configuration option
[processing]store_data_location. The introspection data can be retrieved from the ironic-inspector API, there is no need to keep an extra link in ironic.
Fixes inspection of nodes with IPv6 BMC address. Inspection could not be initiated because an IPv6 address was treated as a hostname, which could not be resolved.
Remove debug logging for PXE filter driver which tends to fill up inspector logs when debug is enabled.
Fixes updating a driver with the
set-attributeintrospection rule action by providing
Adds a configuration option
[iptables]ip_versionto specify the desired ip version for the iptables pxe filter, possible values are
6, the default value is
4. When set to
6, the iptables pxe filter will use
ip6tablescommand to manage rules for the DHCPv6 port
Adds new introspection rules actions to add or remove traits on nodes:
The deprecated configuration option
Adds rpc related configuration options for the communication between ironic-inspector API and worker. It needs to be configured properly during upgrade. Set
fake://if a rpc backend is not available or not desired.
[DEFAULT]ssl_key_pathare deprecated for ironic-inspector now uses oslo.service as underlying HTTP service instead of Werkzeug. Please use
A new rootwrap filter is now included to allow control of the systemd dnsmasq service used by ironic-inspector. This fixes a permission issue when systemctl commands are used as
dnsmasq_stop_commandin the configuration for the dnsmasq pxe filter. See bug 2002818.
The filter uses the systemd service name used by the RDO distribution (
Fixes issue that can result in introspection failure when a network switch sends incomplete information for LLDP switch_id or port_id. The validation expects these fields when a port is updated, this fix now handles the validation exception.
set-attributeintrospection rule action to accept
Noneas value for a property.
Fixes the issue that ports were not collected when there were only IPv6 addresses (no IPv4), and the configuration option
[processing]add_portswas not set to
all. Inspector will report “No suitable interfaces found” if no interface is collected. For more information see Story 1744073