summaryrefslogtreecommitdiff
path: root/releasenotes
Commit message (Collapse)AuthorAgeFilesLines
* 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
|\ \
| * | Create fstab entry with appropriate labelJulia Kreger2022-03-101-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Depending on the how the stars align with partition images being written to a remote system, we *may* end up with *either* a Partition UUID value, or a Partition's UUID value. Which are distinctly different. This is becasue the value, when collected as a result of writing an image to disk *falls* back and passes the value to enable partition discovery and matching. Later on, when we realized we ought to create an fstab entry, we blindly re-used the value thinking it was, indeed, always a Partition's UUID and not the Partition UUID. Obviously, the label type is quite explicit, either UUID or PARTUUID respectively, when initial ramdisk utilities such as dracut are searching and mounting filesystems. Adds capability to identify the correct label to utilize based upon the current state of the block devices on disk. Granted, we are likely only exposed to this because of IO race conditions under high concurrecy load operations. Normally this would only be seen on test VMs, but systems being backed by a Storage Area Network *can* exibit the same IO race conditions as virtual machines. Change-Id: I953c936cbf8fad889108cbf4e50b1a15f511b38c Resolves: rhbz#2058717 Story: #2009881 Task: 44623
* | | Merge "Rescan device after filesystem creation"Zuul2022-03-071-0/+5
|\ \ \ | |_|/ |/| |
| * | Rescan device after filesystem creationVanou Ishii2022-02-111-0/+5
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | In work_on_disk function, IPA runs mkfs commands without following device rescan operation. This leads to incorrect content of uuids_to_return to be returned. These mkfs commands modify partition label but IPA fails to catch such changes because of no following device rescan operation. This commit adds call of device rescan function before uuids_to_return construction. Change-Id: I4e8b30deb5e2247f51ce8f10bd3271f64a264089
* | Use utf-16-le if BOM not presentRiccardo Pittau2022-02-221-0/+6
|/ | | | | | | In case no BOM is present in the CSV file the utf-16 codec won't work. We fail over to utf-16-le as Little Endian is commonly used. Change-Id: I3e25ce4997f5dd3df87caba753daced65838f85a
* Clean up release notes8.4.0Dmitry Tantsur2022-02-032-10/+11
| | | | Change-Id: I568d7edfe81e928e6d7f09bd4a7933ca72b8813a
* SoftwareRAID: Use efibootmgr (and drop grub2-install)Arne Wiebalck2022-01-261-0/+7
| | | | | | | | | | | | | | | Move the software RAID code path from grub2-install to efibootmgr: - remove the UEFI efibootmgr exception for software RAID - create and populate the ESPs on the holder disks - update the NVRAM with all ESPs (the component devices of the ESP mirror, use unique labels to avoid unintentional deduplication of entries in the NVRAM) Story: #2009794 Change-Id: I7ed34e595215194a589c2f1cd0b39ff0336da8f1
* Burn-in: Dynamic network pairingArne Wiebalck2022-01-101-0/+17
| | | | | | | | | | | | | Pair nodes dynamically via a distributed coordination backend for network burn-in. The algorithm uses a group to pair nodes: after acquiring a lock, a first node joins the group, releases the lock, waits for a second node, then they both leave, and release the lock for the next pair. Story: #2007523 Task: #42796 Change-Id: I572093b144bc90a49cd76929c7e8685ed45d9f6e
* Merge "Burn-in: Add options for named log files"8.3.0Zuul2021-12-091-0/+7
|\
| * Burn-in: Add options for named log filesArne Wiebalck2021-12-081-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | In order to ease logging of the various burn-in steps, this patch proposes options to define the outpout files for all burn-in steps: {'agent_burnin_cpu', 'agent_burnin_vm', 'agent_burnin_fio_network', 'agent_burnin_fio_disk'}_outputfile via a node's driver-info. Story: #2007523 Task: #44102 Change-Id: I327cae5949d38e738d3c535487b3795d00ad8f1e
* | Merge "Instruct qemu-img to write image zeros to disk."Zuul2021-12-091-0/+6
|\ \
| * | Instruct qemu-img to write image zeros to disk.Derek Higgins2021-12-081-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Doing this will cause it not to zero out the entire block device which can be very costly on a slow HDD. Story: 2009227 Task: 43315 Change-Id: I62ba2afc037d9844387e6b0984fe5008779d95d2
* | | Merge "Burn-in: Add SMART self test to disk burn-in"Zuul2021-12-091-0/+7
|\ \ \
| * | | Burn-in: Add SMART self test to disk burn-inArne Wiebalck2021-12-061-0/+7
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add the option to run a SMART self test right after the disk burn-in. The disk burn-in step will fail if the SMART test on any of the disk fails. Story: #2007523 Task: #43383 Change-Id: I1312d5b71bedd044581a136af0b4c43769d21877
* | | Merge "Prepare for bugfix release"Zuul2021-12-081-2/+2
|\ \ \ | |_|/ |/| |
| * | Prepare for bugfix releaseRiccardo Pittau2021-12-071-2/+2
| |/ | | | | | | Change-Id: Ic9437c6d55879db45aa1aa3dc548ea62ed5ca10d
* | [trivial] Fix Xena release notes versionsRiccardo Pittau2021-12-061-3/+3
|/ | | | Change-Id: Iaf511e6aeae59409ac6d1ba4543d297c5bb2ec01
* Re-read the partition table with partx -a, part 2Riccardo Pittau2021-11-091-0/+7
| | | | | | | | | | | | Use add instead of update to re-read the partition table with partx. See [1] for more details. Co-authored-by: Arne Wiebalck <arne.wiebalck@cern.ch> [1] https: //opendev.org/openstack/ironic-python-agent/commit/dc8c1f16f9a00e2bff21612d1a9cf0ea0f3addf0 Change-Id: I2336e22dadc790cfbde87904612fcaa3b8c501db
* Re-read the partition table with partx -aArne Wiebalck2021-11-061-0/+5
| | | | | | | | | | | Re-read the partition table with 'partx -a', rather than 'partx -u'. This should fix an timing issue where the bootloader installation fails to mount the EFI partition from a whole disk image since it is not yet aware of the new partitions (observed with both, the iscsi and the direct deploy interface). Change-Id: If5da3075e813ae01df3decf8f0647aba111b0515
* Merge "Fix UEFI record regex"Zuul2021-11-051-0/+7
|\
| * Fix UEFI record regexJulia Kreger2021-11-041-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | I accidently put colons on the test data and remembered taking the colon character out of the regex I was working on, but apparently left it in, and accounted for the active entry indicator flag which appears to have inconsistent support across vendors. The regex has been fixed, and a test added from a Lenovo SR650 which has some additional string entry data in the UEFI output which may separate entries. Change-Id: I1f67b0fb1f645fa82e98bd7c7bba3ffc7755cc74
* | Merge "Always include the oslo_log log file in ramdisk logs"Zuul2021-11-041-0/+5
|\ \ | |/ |/|
| * Always include the oslo_log log file in ramdisk logsDmitry Tantsur2021-10-281-0/+5
| | | | | | | | | | | | | | Even if journald is present, there is no guarantee that IPA logs there (this is the case in container-based ramdisks). Change-Id: Iceeab0010827728711e19e5b031ccac55fe1efde
* | Delete EFI boot entry duplicate labels firstJulia Kreger2021-11-011-0/+6
|/ | | | | | | | | | | | | | | | | | | | | | | Some firmware seems to take an objection with EFI nvram entries being deleted after one is added, resulting in the entire entry table being reset to the last known good state. This is problematic, as ultimately deployments can time out if we previously booted with Networking, and the machine, while commanded to do other wise, reboots back to networking regardless. We will now delete entries first, before proceeding. Additionally, for general use, this pattern may serve the community better by avoiding cases where we would have previously just relied upon efibootmgr[0] to warn us of duplicate entries. [0]: https://github.com/rhboot/efibootmgr/blob/103aa22ece98f09fe3ea2a0c83988f0ee2d0e5a8/src/efibootmgr.c#L228 Change-Id: Ib61a7100a059e79a8b0901fd8f46b9bc41d657dc Story: 2009649 Task: 43808
* Respect global parameters when downloading a configdriveDmitry Tantsur2021-10-201-0/+12
| | | | | | | | * Use the same TLS parameters as everything else * Respect image_download_connection_timeout * Do not ignore HTTP errors Change-Id: I84f8021f731186d82e44ac3d4ef2d12df13f830a
* Assert EFI part UUID is not None before editing fstabArne Wiebalck2021-10-081-0/+6
| | | | | | | | | | The EFI partition UUID may be None and this will break the fstab editing. While this is not necessarily fatal when instantiating a node, it creates an exception at the end of bootloader installation, so only attempt to add a line to fstab when the UUID is not None. Change-Id: I68799980e67c05afe4ca68ca9733605dd166d54d
* Software RAID: Call udev_settle before creationArne Wiebalck2021-10-051-0/+7
| | | | | | | | | | | | This patch fixes a race during software RAID creation: we create the partition with parted, the kernel then notifies udev, but we need to wait for udevd to create the device files before calling mdadm to create the md device. Credits to jcosmao for finding this. Change-Id: I642f28acc351cf50263e37dfbc8468bf59de2cc5
* Update master for stable/xenaOpenStack Release Bot2021-09-222-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/xena. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/xena. Sem-Ver: feature Change-Id: If28b1df9c76469062e6d9ce28edcf3026fdbfbaa
* Merge "Expose BMC MAC address in inventory data"Zuul2021-08-081-0/+6
|\
| * Expose BMC MAC address in inventory dataJonas Schäfer2021-08-061-0/+6
| | | | | | | | | | | | | | | | | | | | This exposes the MAC address of the first LAN channel with an assigned IP address in the inventory data. This is useful for inventory processes where the asset number is not discoverable from the software side: the BMC MAC is going to be unique (at least within an organization). Change-Id: I8a4bee0c25743befd7f2033e4e0cba26895c8926
View Lorry Controller Status