summaryrefslogtreecommitdiff
path: root/releasenotes
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Add support for CentOS SUM files"HEADmasterZuul2023-05-091-0/+11
|\
| * Add support for CentOS SUM filesHarald Jensås2023-05-031-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The CentOS Stream SUM files uses format: # FILENAME: <size> bytes ALGORITHM (FILENAME) = CHECKSUM Compared to the more common format: CHECKSUM *FILE_A CHECKSUM FILE_B Use regular expressions to check for filename both in the middle with parentheses and at the end. Similarly look for valid checksums at beginning or end of line. Also look for know checsum patterns in case file only contain the checksum iteself. Change-Id: I9e49c1a6c66e51a7b884485f0bcaf7f1802bda33
* | Merge "Revert disabling MD5 checksums"Zuul2023-05-051-9/+2
|\ \
| * | Revert disabling MD5 checksumsDmitry Tantsur2023-05-041-9/+2
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | This was a significant breaking change that was landed despite explicit disagreement by some community members (myself included). It has already resulted in an accidental Ironic CI breakage, has broken Bifrost and has a potential of breaking Metal3. In case of Metal3, MD5 support is a part of its public API. While MD5 is a potential security hazard, I don't see the need to hurry this change without giving the community time to prepare. This change reverts the new option md5_enabled to True. Change-Id: I32b291ea162e8eb22429712c15cb5b225a6daafd
* | Add network interface speed to the inventoryDmitry Tantsur2023-05-031-0/+5
|/ | | | | | | This is another fact that Metal3's baremetal-operator is currently consuming from extra-hardware. Change-Id: I2ec9d5e9369f5508e7583a4e13c2083f5c8b28ba
* Merge "Disable MD5 image checksums"Zuul2023-05-021-0/+19
|\
| * Disable MD5 image checksumsJulia Kreger2023-04-241-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | MD5 image checksums have long been supersceeded by the use of a ``os_hash_algo`` and ``os_hash_value`` field as part of the properties of an image. In the process of doing this, we determined that checksum via URL usage was non-trivial and determined that an appropriate path was to allow the checksum type to be determined as needed. Change-Id: I26ba8f8c37d663096f558e83028ff463d31bd4e6
* | Merge "Deprecate LLDP in inventory in favour of a new collector"Zuul2023-04-271-0/+12
|\ \
| * | Deprecate LLDP in inventory in favour of a new collectorDmitry Tantsur2023-04-261-0/+12
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Binary LLDP data is bloating inventory causing us to disable its collection by default. For other similar low-level information, such as PCI devices or DMI data, we already use inspection collectors instead. Now that the inventory format is shared with out-of-band inspection, having LLDP there makes even less sense. This change adds a new collector ``lldp`` to replace the now-deprecated inventory field. Change-Id: I56be06a7d1db28407e1128c198c12bea0809d3a3
* | Fix UTF-16 result handling for efibootmgrJulia Kreger2023-04-171-0/+9
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | The tl;dr is that UEFI NVRAM is in encoded in UTF-16, and when we run the efibootmgr command, we can get unicode characters back. Except we previously were forcing everything to be treated as UTF-8 due to the way oslo.concurrency's processutils module works. This could be observed with UTF character 0x00FF which raises up a nice exception when we try to decode it. Anyhow! while fixing handling of this, we discovered we could get basically the cruft out of the NVRAM, by getting what was most likey a truncated string out of our own test VMs. As such, we need to also permit decoding to be tollerant of failures. This could be binary data or as simple as flipped bits which get interpretted invalid characters. As such, we have introduced such data into one of our tests involving UEFI record de-duplication. Closes-Bug: 2015602 Change-Id: I006535bf124379ed65443c7b283bc99ecc95568b
* Report system firmware information in the inventoryDmitry Tantsur2023-03-311-0/+5
| | | | Change-Id: I5b6ceb9cdcf4baa97a6f0482d1030d14f3f2ecff
* Update master for stable/2023.1OpenStack Release Bot2023-03-092-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/2023.1. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2023.1. Sem-Ver: feature Change-Id: Id58fd751e6ed8ed3d478a78a6895cad75667c9b1
* Merge "update NVIDIA NIC firmware images and settings by ironic-python-agent"9.4.0Zuul2023-01-311-0/+7
|\
| * update NVIDIA NIC firmware images and settings by ironic-python-agentwaleed mousa2023-01-111-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add "update_nvidia_nic_firmware_image" and "update_nvidia_nic_firmware_settings" clean steps to MellanoxDeviceHardwareManager. By adding those two steps, we can update the firmware image and firmware settings of NVIDIA NICs by ironic-python-agent using manual cleaning command The clean steps require mstflint package installed on the image. The "update_nvidia_nic_firmware_image" clean step requires to pass "images" parameter to the clean command The "images" parameter is a json blob contains a list of images, where each image contains a map of: * url: to firmware image (file://, http://) * checksum: checksum of the provided image * checksumType: md5/sha512/sha256 * componentFlavor: PSID of the nic * version: version of the FW The "update_nvidia_nic_firmware_settings" clean step requires to pass "settings" parameter to the clean command The "settings" parameter is a json blob contains a list of settings, where each settings contains a map of: * deviceID: device ID * globalConfig: global config * function0Config: function 0 config * function1Config: function 1 config Change-Id: Icfaffd7c58c3c73c3fa28cfc2a6c954d2c93c16e Story: 2010228 Task: 46016
* | Merge "Make logs collection a hardware manager call"9.3.0Zuul2023-01-261-0/+5
|\ \
| * | Make logs collection a hardware manager callDmitry Tantsur2023-01-251-0/+5
| |/ | | | | | | | | | | This allows hardware managers to collect additional logs. Change-Id: If082b921d4bf71c4cc41a5a72db6995b08637374
* | Make reno ignore bugfix eol tagsJay Faulkner2023-01-251-0/+2
|/ | | | | | | | | Reno was assuming all tags ending in -eol represented an old, EOL'd stable branch. That's not true for Ironic projects which have bugfix branches. Update the regexp to exclude those branches. Co-Authored-By: Adam McArthur <adam@mcaq.me> Change-Id: I265969ab40a98a02962c2fc8460b6519ab576f99
* Merge "prioritize lsblk as a source of device serials"Zuul2022-10-141-0/+8
|\
| * prioritize lsblk as a source of device serialsRozzii2022-10-101-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current way of prioritizing ID/DM_SERIAL_SHORT or ID/DM_SERIAL works in most cases but the udev values seem to be unreliable. Based on experience it looks like lsblk might be a better source of truth than udev in regerards to serial number information. This commit makes lsblk the default provider of block device serial number information. Story: 2010263 Task: 46161 Change-Id: I16039b46676f1a61b32ee7ca7e6d526e65829113
* | Merge "Update release versions for yoga"Zuul2022-10-141-3/+3
|\ \ | |/ |/|
| * Update release versions for yogaRiccardo Pittau2022-09-231-3/+3
| | | | | | | | Change-Id: I06d14bc499a7c081fe73b68de6c49e2f1bc51dc5
* | Update master for stable/zedOpenStack Release Bot2022-09-232-0/+7
|/ | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/zed. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/zed. Sem-Ver: feature Change-Id: Iff9b5efee0b436357d5cae3909a89cd09d5e6070
* SoftwareRAID: Enable skipping RAIDSJakub Jelinek2022-09-051-0/+6
| | | | | | | | | | | | | | Extend the ability to skip disks to RAID devices This allows users to specify the volume name of a logical device in the skip list which is then not cleaned or created again during the create/apply configuration phase The volume name can be specified in target raid config provided the change https://review.opendev.org/c/openstack/ironic-python-agent/+/853182/ passes Story: 2010233 Change-Id: Ib9290a97519bc48e585e1bafb0b60cc14e621e0f
* Merge "Create RAIDs with volume name"Zuul2022-09-021-0/+5
|\
| * Create RAIDs with volume nameJakub Jelinek2022-09-021-0/+5
| | | | | | | | | | | | | | | | Use 'volume_name' field from 'target_raid_config' to create logical disks if it is present Do not allow two logical disks to have the same volume name Change-Id: If3e4e9f8698ec3e0cb49717f8ed2087d2ba03f2c
* | Trivial: Fix reno for software raid fixJulia Kreger2022-08-251-1/+1
| | | | | | | | | | | | | | Fixes the release note for If721dfe1caa5915326482969e55fbf4697538231. Change-Id: I9971d12665f2c8a4fdfe82911c6173021d03ddc0
* | Merge "Fix software raid output poisoning"Zuul2022-08-251-0/+7
|\ \
| * | Fix software raid output poisoningJulia Kreger2022-08-241-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the event a device name is set to contain a raid device path, it is possible for the Name and Events field values of mdadm's detailed output to contain text which inadvertently gets captured and mapped as component data for the "holder" devices of the RAID set. This would cause invalid values to get passed to UEFI methods which would cause a deployment to fail under these circumstances. We now ignore the Name and Events fields in mdadm output. Change-Id: If721dfe1caa5915326482969e55fbf4697538231
* | | remove unicode prefix from codeniuke2022-08-231-8/+8
|/ / | | | | | | Change-Id: I70f0112f1ee3066ffd9316d10b84b9ea5b7fc306
* | Enable skipping disks for cleaningJakub Jelinek2022-08-111-0/+6
|/ | | | | | | | | | | | Introduce a field skip_block_devices in properties - this is a list of dictionaries Create a helper function list_block_devices_check_skip_list Update tests of erase_devices_express to use node when calling _list_erasable_devices Add tests covering various options of the skip list definition Use the helper function in get_os_install_device when node is cached Story: 2009914 Change-Id: I3bdad3cca8acb3e0a69ebb218216e8c8419e9d65
* Merge "Guard shared device/cluster filesystems"Zuul2022-07-201-0/+20
|\
| * Guard shared device/cluster filesystemsJulia Kreger2022-07-191-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Certain filesystems are sometimes used in specialty computing environments where a shared storage infrastructure or fabric exists. These filesystems allow for multi-host shared concurrent read/write access to the underlying block device by *not* locking the entire device for exclusive use. Generally ranges of the disk are reserved for each interacting node to write to, and locking schemes are used to prevent collissions. These filesystems are common for use cases where high availability is required or ability for individual computers to collaborate on a given workload is critical, such as a group of hypervisors supporting virtual machines because it can allow for nearly seamless transfer of workload from one machine to another. Similar technologies are also used for cluster quorum and cluster durable state sharing, however that is not specifically considered in scope. Where things get difficult is becuase the entire device is not exclusively locked with the storage fabrics, and in some cases locking is handled by a Distributed Lock Manager on the network, or via special sector interactions amongst the cluster members which understand and support the filesystem. As a reult of this IO/Interaction model, an Ironic-Python-Agent performing cleaning can effectively destroy the cluster just by attempting to clean storage which it percieves as attached locally. This is not IPA's fault, often this case occurs when a Storage Administrator forgot to update LUN masking or volume settings on a SAN as it relates to an individual host in the overall computing environment. The net result of one node cleaning the shared volume may include restoration from snapshot, backup storage, or may ultimately cause permenant data loss, depending on the environment and the usage of that environment. Included in this patch: - IBM GPFS - Can be used on a shared block device... apparently according to IBM's documentation. The standard use of GPFS is more Ceph like in design... however GPFS is also a specially licensed commercial offering, so it is a red flag if this is encountered, and should be investigated by the environment's systems operator. - Red Hat GFS2 - Is used with shared common block devices in clusters. - VMware VMFS - Is used with shared SAN block devices, as well as local block devices. With shared block devices, ranges of the disk are locked instead of the whole disk, and the ranges are mapped to virtual machine disk interfaces. It is unknown, due to lack of information, if this will detect and prevent erasure of VMFS logical extent volumes. Co-Authored-by: Jay Faulkner <jay@jvf.cc> Change-Id: Ic8cade008577516e696893fdbdabf70999c06a5b Story: 2009978 Task: 44985
* | Drop support for instance netbootDmitry Tantsur2022-07-071-0/+5
|/ | | | Change-Id: I2b4c543537dac8904028fdcdb590c1c214238e10
* Merge "Fix passing kwargs in clean steps"Zuul2022-07-041-0/+6
|\
| * Fix passing kwargs in clean stepswaleedm2022-07-011-0/+6
| | | | | | | | | | | | | | | | Pass kwargs to dispatch_to_managers method in execute_clean_step Change-Id: Ida4ed4646659b2ee3f8f92b0a4d73c0266dd5a99 Story: 2010123 Task: 45705
* | Merge "Gather details about bond interfaces if present"Zuul2022-07-021-0/+5
|\ \
| * | Gather details about bond interfaces if presentDerek Higgins2022-06-211-0/+5
| |/ | | | | | | | | | | | | | | | | If present gather information about bonded interfaces. Story: #2010093 Task: #45637 Change-Id: I394187640b4788ebec21c3391d33ed728fb72ffa
* | Merge "Collect udev properties in the ramdisk logs"Zuul2022-07-021-0/+5
|\ \
| * | Collect udev properties in the ramdisk logsDmitry Tantsur2022-06-171-0/+5
| |/ | | | | | | Change-Id: Ifcf3dfff00b604dec1e2f430369ab8053f50f137
* | Fix discovering WWN/serial for devicemapper devicesDmitry Tantsur2022-06-141-0/+4
|/ | | | | | | UDev prefix is DM_ not ID_ for them. On top of that, they don't have short serials (or at least don't always have). Change-Id: I5b6075fbff72201a2fd620f789978acceafc417b
* Multipath Hardware path handlingJulia Kreger2022-05-181-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removes multipath base devices from consideration by default, and instead allows the device-mapper device managed by multipath to be picked up and utilized instead. In effect, allowing us to ignore standby paths *and* leverage multiple concurrent IO paths if so offered via ALUA. In reality, anyone who has previously built IPA with multipath tooling might not have encountered issues previously because they used Active/Active SAN storage environments. They would have worked because the IO lock would have been exchanged between controllers and paths. However, Active/Passive environments will block passive paths from access, ultimately preventing new locks from being established without proper negotiation. Ultimately requiring multipathing *and* the agent to be smart enough to know to disqualify underlying paths to backend storage volumes. An additional benefit of this is active/active MPIO devices will, as long as ``multipath`` is present inside the ramdisk, no longer possibly result in duplicate IO wipes occuring accross numerous devices. Story: #2010003 Task: #45108 Resolves: rhbz#2076622 Resolves: rhbz#2070519 Change-Id: I0fd6356f036d5ff17510fb838eaf418164cdfc92
* Merge "Collect a full lsblk output in the ramdisk logs"Zuul2022-05-091-0/+5
|\
| * Collect a full lsblk output in the ramdisk logsDmitry Tantsur2022-04-291-0/+5
| | | | | | | | | | | | | | | | The existing lsblk call is very handy for an overview, but there a lot more useful pairs to collect. Collect them in a machine-readable format to be able to use in debugging and further development. Change-Id: Ib27843524421944ee93de975d275e93276a5597a
* | Merge "Do not try to guess EFI partition path by its number"8.6.0Zuul2022-05-051-0/+5
|\ \
| * | Do not try to guess EFI partition path by its numberDmitry Tantsur2022-05-041-0/+5
| |/ | | | | | | | | | | | | The logic of adding a partition number to the device path does not work for devicemapper devices (e.g. a multipath storage device). Change-Id: I9a445e847d282c50adfa4bad5e7136776861005d
* | Use a pre-defined partition UUID to detect configdrive on GPTDmitry Tantsur2022-04-291-0/+17
|/ | | | | | | | Using partition numbers is currently broken for devicemapper devices. Fortunately, GPT has partition UUIDs, so we can just generate one and use it for lookup. Change-Id: I41ffe4f8e4c6e43182090b5aa2a2b4b34f32efd5
* Update master for stable/yogaOpenStack Release Bot2022-03-232-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/yoga. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/yoga. Sem-Ver: feature Change-Id: Ib1aa5d02cc5dc32bc4eebf6982d3f00d44e703f3
* Merge "Improve efficiency of storage cleaning in mixed media envs"Zuul2022-03-151-0/+8
|\
| * Improve efficiency of storage cleaning in mixed media envsJacob Anders2022-03-151-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://storyboard.openstack.org/#!/story/2008290 added support for NVMe-native storage cleaning, greatly improving storage clean times on NVMe-based nodes as well as reducing device wear. This is a follow up change which aims to make further improvements to cleaning efficiency in mixed NVMe-HDD environments. This is achieved by combining NVMe-native cleaning methods on NVMe devices with traditional metadata clean on non-NVMe devices. Story: 2009264 Task: 43498 Change-Id: I445d8f4aaa6cd191d2e540032aed3148fdbff341
* | Merge "Create fstab entry with appropriate label"Zuul2022-03-111-0/+10
|\ \
View Lorry Controller Status