summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | Do not try to guess EFI partition path by its numberDmitry Tantsur2022-05-045-58/+142
| |/ / | | | | | | | | | | | | | | | | | | 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-293-38/+55
|/ / | | | | | | | | | | | | | | 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
* | Use Werkzeug modern versionRiccardo Pittau2022-04-144-6/+4
| | | | | | | | | | | | | | | | | | | | Request class from Werkzeug now includes json capability by default. See [1] and [2] for more info. [1] https://github.com/pallets/werkzeug/commit/2cd4fa9484b5d55284a86ac200df603552ba2300 [2] https://github.com/pallets/werkzeug/commit/7b52ecd8f3a67e19df32467a832761f4f0d97c8b Change-Id: I3c74b26ef4aff07c371364203a5b39c658b552a7
* | Add Python3 zed unit testsOpenStack Release Bot2022-03-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for zed. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: I25719dcd3035816d934b806ae129051df322bf9c
* | 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 "Refactor efi_utils for easier maintaining and debugging"8.5.0Zuul2022-03-182-68/+161
|\ \ | |/ |/|
| * Refactor efi_utils for easier maintaining and debuggingDmitry Tantsur2022-02-142-68/+161
| | | | | | | | | | | | | | | | | | | | * Move irrelevant code from inside the giant try..except block * Do not bother removing the (empty) temporary mountpoint * Fix log messages according to the actual code * Fix some code duplication * Add missing unit tests for failure case Change-Id: Id7b557419d513375816d73901e2ab6f139d765ad
* | Merge "Improve efficiency of storage cleaning in mixed media envs"Zuul2022-03-153-16/+124
|\ \
| * | Improve efficiency of storage cleaning in mixed media envsJacob Anders2022-03-153-16/+124
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 "CI: be explicit that the jobs are using the DIB ramdisk"Zuul2022-03-121-0/+2
|\ \ \
| * | | CI: be explicit that the jobs are using the DIB ramdiskDmitry Tantsur2022-02-031-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently it requires tracing the jobs up to the ironic's devstack plugin. Be explicit. Change-Id: I19d0e680b0025bda22709c5a4fff9eacb5b4b1d0
* | | | Merge "Add non-voting dib CentOS Stream 9 job"Zuul2022-03-111-0/+2
|\ \ \ \
| * | | | Add non-voting dib CentOS Stream 9 jobRiccardo Pittau2022-03-101-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We recently enabled voting CS9 jobs in ipa-builder, let's also add the same check job here. Change-Id: Iaf2e56e0a1f6ca35272bcaedf3cb73273080b7ef
* | | | | Merge "Create fstab entry with appropriate label"Zuul2022-03-116-10/+135
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | Create fstab entry with appropriate labelJulia Kreger2022-03-106-10/+135
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 "Run partx in verbose mode to simplify debugging"Zuul2022-03-084-55/+55
|\ \ \ \ \
| * | | | | Run partx in verbose mode to simplify debuggingDmitry Tantsur2022-02-144-55/+55
| | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | Otherwise the actual failure cause is not recorded. Change-Id: If66ee97016ddf0e5c3f40ad9400ff3bc6fdebedc
* | | | | Merge "Add `mount` and `parted -l` to the collected commands"Zuul2022-03-082-4/+10
|\ \ \ \ \
| * | | | | Add `mount` and `parted -l` to the collected commandsDmitry Tantsur2022-02-142-4/+10
| |/ / / / | | | | | | | | | | | | | | | Change-Id: I1c759552220291890704d0002a62ea3f51701691
* | | | | Merge "Rescan device after filesystem creation"Zuul2022-03-073-4/+21
|\ \ \ \ \ | |_|_|_|/ |/| | | |
| * | | | Rescan device after filesystem creationVanou Ishii2022-02-113-4/+21
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Merge "Use utf-16-le if BOM not present"Zuul2022-03-022-2/+14
|\ \ \ \ | |_|/ / |/| | |
| * | | Use utf-16-le if BOM not presentRiccardo Pittau2022-02-222-2/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Stop defaulting the standalone job to netboot; use the correct boot modeDmitry Tantsur2022-02-211-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | Its configuration must match one in Ironic, and netboot does not work with whole disk images under UEFI. Fix the boot mode of the BIOS job: it was running in UEFI. Change-Id: Ia207e80bbfc30f8d2891e11bbeda7b2ab0d617c0
* | | Move prepare_boot_partitions_for_softraid to raid_utilsArne Wiebalck2022-02-146-332/+343
|/ / | | | | | | | | | | | | | | | | | | | | prepare_boot_partitions_for_softraid() is used in BIOS and UEFI modes to prepare the partitions for the bootloader. Move it from the image extensions to raid_utils to reflect this and avoid the import of an extension to efi_utils. Follow-up to 62c5674a600baeeef0af3b12baeab486870eb103. Change-Id: I9f5974fbbfea5e8cdfbb7e49bea375e5cbfdd145
* | Clean up release notes8.4.0Dmitry Tantsur2022-02-032-10/+11
|/ | | | Change-Id: I568d7edfe81e928e6d7f09bd4a7933ca72b8813a
* Make the standalone job voting againDmitry Tantsur2022-02-011-7/+2
| | | | | | | | We forgot to revert it. This job covers software RAID and manual cleaning, so it's very important to avoid regressions, even if it costs us some rechecks from time to time. Change-Id: I2446afeaca866ffc3131b5e9f266526f35fc5ed7
* Use canonical device name for RAID device for ESPDmitry Tantsur2022-02-014-17/+71
| | | | | | | | | | It seems like tinyIPA silently replaces /dev/md/esp with /dev/md127. Find the next free /dev/md device and use it instead. Also rescan the resulting device before copying files. Change-Id: Ie04f530be434c4b1561e75f387b9da679e4607e0 Depends-On: https://review.opendev.org/c/openstack/ironic/+/827129/
* SoftwareRAID: Use efibootmgr (and drop grub2-install)Arne Wiebalck2022-01-267-45/+172
| | | | | | | | | | | | | | | 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
* Merge "Burn-in: Dynamic network pairing"Zuul2022-01-206-16/+293
|\
| * Burn-in: Dynamic network pairingArne Wiebalck2022-01-106-16/+293
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | [trivial] Fix typo in __init__.pyArne Wiebalck2021-12-161-1/+1
| | | | | | | | Change-Id: I67810abbfb975c0d0ad0faf9807318c462580528
* | Re-add python 3.6/3.7 in classifierGhanshyam Mann2021-12-131-0/+2
|/ | | | | | | | | | | | | | | | | | We have updated the yoga testing runtime to keep the py36 testing. - https://review.opendev.org/c/openstack/governance/+/820195 Unit tests job template is also updated to keep python 3.6 as a voting job. So with the py3.6 and py3.9 testing as voting job template, we are keeping python 3.6, 3.7, 3.8, and 3.8 as tested versions in the Yoga cycle. - https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286 This commit re-add the python 3.6/3.7 versions in setup.cfg classifier. Change-Id: I0f03a7f5bb2aa07c2ec2aab1a8ebfddc0c70ca87
* Merge "Burn-in: Add options for named log files"8.3.0Zuul2021-12-093-21/+117
|\
| * Burn-in: Add options for named log filesArne Wiebalck2021-12-083-21/+117
| | | | | | | | | | | | | | | | | | | | | | | | 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 "Use only Yoga tests"Zuul2021-12-091-10/+0
|\ \
| * | Use only Yoga testsRiccardo Pittau2021-12-031-10/+0
| |/ | | | | | | | | | | | | | | | | TC has decided to keep support for Python 3.6 during the Yoga cycle. For more info see [1] [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026164.html Change-Id: Icfe518fafa2b012e034a2e8ff18c242843df0086
* | Merge "Instruct qemu-img to write image zeros to disk."Zuul2021-12-095-7/+15
|\ \
| * | Instruct qemu-img to write image zeros to disk.Derek Higgins2021-12-085-7/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-093-0/+168
|\ \ \
| * | | Burn-in: Add SMART self test to disk burn-inArne Wiebalck2021-12-063-0/+168
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Test python 3.6 for distributions compatibilityRiccardo Pittau2021-11-301-0/+10
| | | | | | | | | | | | | | | | | | | | | | As discussed during the ironic meeting on 29/11/2021, the community has decided to continue testing the code against Python 3.6 to keep compatibility with distributions that have native support for it, such as CentOS Stream 8, Ubuntu Bionic, Debian 10, and openSuse Leap, at least until it's possible and reasonable considering the support granted from other dependencies and libraries, and not beyond the Yoga cycle. Change-Id: I97ad7c4acdb278e2849a598c5a02a71fc67cc81a
* | Merge "Updating yoga tested python versions in classifier"Zuul2021-11-261-2/+1
|\ \
| * | Updating yoga tested python versions in classifierGhanshyam Mann2021-11-241-2/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | Yoga testing runtime has been updated with py38 and py39 as voting and removed the py36 testing. Unit tests update are handled by the job template change in openstack-zuul-job and you can see the updated jobs running in gate. - https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/818609 this commit updates the tested py versions in setup.cfg classifier. [1] https://governance.openstack.org/tc/reference/runtimes/yoga.html Change-Id: I47cd32e5690b55b983827c650efba4fd99e7be55
* | Get rid of lambda in RealFilePartitioningTestCaseIury Gregory Melo Ferreira2021-11-251-10/+14
|/ | | | | | | This commit changes the lambda usage in the RealFilePartitioningTestCase to autospec to avoid problems with unexpected args. Change-Id: I21356a7783f105dde9ff0d3777e2a06f3f28a786
* Merge "Trivial: split away efibootmgr helpers"Zuul2021-11-231-13/+44
|\
| * Trivial: split away efibootmgr helpersDmitry Tantsur2021-11-191-13/+44
| | | | | | | | | | | | These are very useful for downstream deploy steps, make them public. Change-Id: I26106a07049f751d3e3cc646431e2176001f4645
View Lorry Controller Status