summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix CIbugfix/8.3Riccardo Pittau2023-01-313-2/+14
| | | | | | | | | | - Remove reno job, it does not make sense to run it on bugfix branches. - Cap tox to version lower than 4 as it is for all stable branches. - Run tests on focal for all except bionic with python 3.6 Change-Id: I290041b1b4a145bb9f06d62122da340794fbc076
* CI: Zuul no longer respects queue paramJay Faulkner2022-10-031-1/+0
| | | | Change-Id: I1e7a3b3c9ded13b10002bb47e98d4a7b486e1dd4
* Fix software raid output poisoningJulia Kreger2022-09-124-1/+42
| | | | | | | | | | | | | | | | | 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 (cherry picked from commit f3e3de8097f05cc830768da7d3f3e9eae04b40a1) (cherry picked from commit 6660e01e1f8a6e7a40b798eea5215b1eddcbe0c3) (cherry picked from commit 5751f60353f3a4bf325a8c9335d743eec45fbcd1)
* Gather details about bond interfaces if presentDerek Higgins2022-07-073-11/+66
| | | | | | | | | | If present gather information about bonded interfaces. Story: #2010093 Task: #45637 Change-Id: I394187640b4788ebec21c3391d33ed728fb72ffa (cherry picked from commit 7e4fe3bf6a2ae41656b7923796f9c2d056a2ed04)
* Fix discovering WWN/serial for devicemapper devicesDmitry Tantsur2022-06-273-16/+31
| | | | | | | | 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 (cherry picked from commit 69e22545033f544d628f9c4ecd5a665ba0b5b85e)
* Remove swift stable/yoga pinRiccardo Pittau2022-06-271-2/+2
| | | | | | | | | | It's already fixed in ironic bugfix/19.0 Also add explicit pin to stable-yoga for neutron in the metalsmith job Depends-On: I255dbac75a47395991be69ff36e32bb3af311e42 Change-Id: Ic6cc72561480f56ef6efa4b6e3a9f973d94970b5
* Multipath Hardware path handlingJulia Kreger2022-06-058-57/+732
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 (cherry picked from commit 014d37743a3b5694e0e2a3cabfafe885417172d5) (cherry picked from commit 2c95ee45339dc910a6b29cb5e0f24a1f48898165)
* Add `mount` and `parted -l` to the collected commandsDmitry Tantsur2022-06-052-4/+22
| | | | | | | | Conflicts: ironic_python_agent/tests/unit/test_utils.py Change-Id: I1c759552220291890704d0002a62ea3f51701691 (cherry picked from commit f1ee454a0ee9a8f18fbfd504d081ce3aeeb0ffa3)
* Collect a full lsblk output in the ramdisk logsDmitry Tantsur2022-06-053-12/+10
| | | | | | | | | | 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 (cherry picked from commit 424e649bed3db5d1129b18b7ea4dfba88d552537) (cherry picked from commit bc74df8bfe89f703880f8a545ce939e9b1cd8651)
* Create fstab entry with appropriate labelJulia Kreger2022-06-056-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 (cherry picked from commit 99ca1086dbfc7b6e41cf800b0bd899565e2e8922)
* Merge "Do not try to guess EFI partition path by its number" into bugfix/8.3Zuul2022-06-055-58/+142
|\
| * Do not try to guess EFI partition path by its numberDmitry Tantsur2022-06-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). Conflicts: ironic_python_agent/efi_utils.py Change-Id: I9a445e847d282c50adfa4bad5e7136776861005d (cherry picked from commit f09f6c9f1a09c7062d0450b3e0a4d3164fd53f7f) (cherry picked from commit 0ab9abd449c0438bfead7bece150df871c5ed95a)
* | Merge "Refactor efi_utils for easier maintaining and debugging" into bugfix/8.3Zuul2022-06-042-68/+161
|\ \ | |/
| * Refactor efi_utils for easier maintaining and debuggingDmitry Tantsur2022-06-022-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 (cherry picked from commit 3d3df17e5ac2f7446ba447ebf9b30047ce0d35e5)
* | Merge "Use canonical device name for RAID device for ESP" into bugfix/8.3Zuul2022-06-044-17/+71
|\ \
| * | Use canonical device name for RAID device for ESPDmitry Tantsur2022-06-024-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/ (cherry picked from commit 6ebf0417044d7266cdd8a6c7458f094bc29023fb)
* | Merge "Fix CI" into bugfix/8.3Zuul2022-06-031-0/+2
|\ \
| * | Fix CIIury Gregory Melo Ferreira2022-06-031-0/+2
| |/ | | | | | | | | | | | | Since bugfix/8.3 is based on stable/yoga pinning swift to that branch to make it compatible again. Change-Id: Ia1bbd6ac2ac2246c0f49f9404772666207881f5f
* | Re-add python 3.6/3.7 in classifierGhanshyam Mann2022-06-021-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 (cherry picked from commit bdf735c662801f6cc262032c9e17c08b7dd83115)
* Merge "Make the standalone job voting again" into bugfix/8.3Zuul2022-05-311-7/+2
|\
| * 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
* | Merge "Fix bugfix/8.3" into bugfix/8.3Zuul2022-05-311-3/+7
|\ \
| * | Fix bugfix/8.3Iury Gregory Melo Ferreira2022-05-301-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | Use the right stable branches in the job config Depends-On: https://review.opendev.org/c/openstack/ironic/+/843822 Change-Id: I261207ee5c06381d128793c34e285ba3ff662814
* | | Merge "Use a pre-defined partition UUID to detect configdrive on GPT" into ↵Zuul2022-05-183-38/+55
|\ \ \ | | | | | | | | | | | | bugfix/8.3
| * | | Use a pre-defined partition UUID to detect configdrive on GPTDmitry Tantsur2022-05-043-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 (cherry picked from commit 65c4de903a2d8059b1520b0102235b6700287f87)
* | | | Merge "SoftwareRAID: Use efibootmgr (and drop grub2-install)" into bugfix/8.3Zuul2022-05-187-45/+172
|\ \ \ \ | |_|/ / |/| | |
| * | | SoftwareRAID: Use efibootmgr (and drop grub2-install)Arne Wiebalck2022-01-287-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 (cherry picked from commit 62c5674a600baeeef0af3b12baeab486870eb103)
* | | Use Yoga constraints for bugfix/8.3Dmitry Tantsur2022-05-173-13/+68
| |/ |/| | | | | Change-Id: I5e95fae1f2846a19c859b5d61e224ad198c1a8c5
* | Merge "Use utf-16-le if BOM not present" into bugfix/8.3Zuul2022-03-112-2/+14
|\ \
| * | Use utf-16-le if BOM not presentRiccardo Pittau2022-03-032-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 (cherry picked from commit 697fa6f3b6db10408eaadd57450456de87f13519)
* | Stop defaulting the standalone job to netboot; use the correct boot modeDmitry Tantsur2022-02-221-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
* Configure CI for bugfix/8.3Dmitry Tantsur2021-12-201-2/+18
| | | | Change-Id: Ia7bf15e98f3e036bdf30dbb55d252a67faf9832d
* Update .gitreview for bugfix/8.3OpenStack Release Bot2021-12-091-0/+1
| | | | Change-Id: I19479ed8b11db6ec4655b711a1a62adf35f30519
* 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