b2ec08a15e63f6f68b50e637a1a6e45465a3b4b8
2550 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
Zuul
|
2d486d9061 | Merge "Remove importlib-metadata from requirements" | ||
|
Mark Goddard
|
b68fa6b2e1 |
Warn when smartctl not found
Currently, if smartctl is not found by IPA, it will silently skip ATA secure erase and proceed to shred (if enabled). This is supposedly for backwards compatibility, but is quite hard to diagnose. This change adds a warning message to make it more obvious what is happening. TrivialFix Change-Id: I03a381e99de79f201ec7e9a388777c3d48457e93 |
||
|
Zuul
|
180c1351fb | Merge "Drop support for Python 3.6 and 3.7" | ||
|
Riccardo Pittau
|
1356157ec8 |
Remove importlib-metadata from requirements
We don't need it anymore as we don't support python < 3.8 Also it was removed from global requirements so it breaks the requirements check. Change-Id: Ia12cbef3515f823fdd627a36020cf7801bf6d734 |
||
|
Derek Higgins
|
7e4fe3bf6a |
Gather details about bond interfaces if present
If present gather information about bonded interfaces. Story: #2010093 Task: #45637 Change-Id: I394187640b4788ebec21c3391d33ed728fb72ffa |
||
|
Dmitry Tantsur
|
a98675890f |
Collect udev properties in the ramdisk logs
Change-Id: Ifcf3dfff00b604dec1e2f430369ab8053f50f137 |
||
|
Riccardo Pittau
|
64ffd2ee80 |
Remove oslo.serialization dependency
Use pure json instead of jsonutils. Borrow encode function from oslo.serialization to be used in the utils module. Change-Id: Ied9a2259a4329a86b4f0853bd1fb187563c0a036 |
||
|
Dmitry Tantsur
|
69e2254503 |
Fix discovering WWN/serial for devicemapper devices
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 |
||
|
Riccardo Pittau
|
09ea41c83d |
Use json for lsblk output
The lsblk output is available in json format since version 2.27 of util-linux [1] https: //mirrors.edge.kernel.org/pub/linux/utils/util-linux/v2.27/v2.27-ReleaseNotes Change-Id: I0c5812736b7a320cc4ecc333f80db70eb78cc76d |
||
|
Riccardo Pittau
|
39d40d5bd2 |
Drop support for Python 3.6 and 3.7
It has been removed from Zed and we're now testing with Python 3.9 in tinyipa and Python 3.8 in CentOS Stream 9 Change-Id: I028121d593b910e585f44e464c7fcb3e635420e8 |
||
|
Riccardo Pittau
|
b8d01d31a2 |
Add ipa-tox-examples job to gate
The ipa-tox-examples job is voting but it's missing from gate Change-Id: Ie47066084172d8e06eb1f6f097b0354b3b800612 |
||
|
Zuul
|
9dca97736f | Merge "Add a metalsmith job with legacy boot" | ||
|
Julia Kreger
|
16a38600a8 |
Update oslo.log requirement to 4.6.1
Previously IPA was set to enforce a minimum version of 3.36.0 which was a Python2 version build which does did not support more recent versions of python. Given that relationship is realistically impossible moving the minimum to something released a bit more recently, in this case 4.6.1. Change-Id: Ibfbcc1196eb9f583ba9d79bae7988d64de514f6d |
||
|
Julia Kreger
|
be5d1463bb |
CI: Removing ironic job queue
Please see: https://zuul-ci.org/docs/zuul/latest/releasenotes.html#relnotes-4-1-0-deprecation-notes Change-Id: I341b8a2220a49c5a7c3f78fed3a1baa0f0638cde |
||
|
Julia Kreger
|
014d37743a |
Multipath Hardware path handling
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 |
||
|
Zuul
|
2c22e60b45 | Merge "Remove support for distributions with Python 3.6" | ||
|
Dmitry Tantsur
|
21b075cd3f |
Add a metalsmith job with legacy boot
With netboot removal, this will be the only job that tests local legacy boot with partition images. Depends-On: https://review.opendev.org/c/openstack/metalsmith/+/841911 Change-Id: Id3f165286cfc47dcf45c042115a63804a0c671e8 |
||
|
Zuul
|
7beb35445b | Merge "Drop lower-constraints.txt and its testing" | ||
|
Zuul
|
ec01ed109f | Merge "Revert "The Python 3.6 and Python 3.7Support has been dropped since yaga"" | ||
|
Dmitry Tantsur
|
2294db5126 |
Revert "The Python 3.6 and Python 3.7Support has been dropped since yaga"
This reverts commit
|
||
|
Dmitry Tantsur
|
5916e7af21 |
Remove support for distributions with Python 3.6
IPA can no longer be installed on them, other projects will follow. Change-Id: I945520d912564be610cee3990bad827549747904 Depends-On: https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/841562 |
||
|
Zuul
|
c2bbcd7dc3 | Merge "The Python 3.6 and Python 3.7Support has been dropped since yaga" | ||
|
Riccardo Pittau
|
f1d45a60e7 |
Drop lower-constraints.txt and its testing
As discussed in TC PTG[1] and TC resolution[2], we are dropping the lower-constraints.txt file and its testing. We will keep lower bounds in the requirements.txt file but with a note that these are not tested lower bounds and we try our best to keep them updated. [1] https://etherpad.opendev.org/p/tc-zed-ptg#L326 [2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal Change-Id: I16ea0a61c018d03d6c23e0b0736295a36b6dd367 |
||
|
Zuul
|
6b8f387498 | Merge "Collect a full lsblk output in the ramdisk logs" | ||
|
likui
|
c4d2851a13 |
The Python 3.6 and Python 3.7Support has been dropped since yaga
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html Change-Id: Ifeec26e57dd2b2908da4f161032b37edf99cb8b8 |
||
|
Zuul
|
979eea621e | Merge "Do not try to guess EFI partition path by its number" 8.6.0 | ||
|
Dmitry Tantsur
|
f09f6c9f1a |
Do not try to guess EFI partition path by its number
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 |
||
|
Dmitry Tantsur
|
65c4de903a |
Use a pre-defined partition UUID to detect configdrive on GPT
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 |
||
|
Dmitry Tantsur
|
424e649bed |
Collect a full lsblk output in the ramdisk logs
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 |
||
|
Riccardo Pittau
|
8111475eb0 |
Use Werkzeug modern version
Request class from Werkzeug now includes json capability by default. See [1] and [2] for more info. [1] |
||
| f9a7871ea0 |
Add Python3 zed unit tests
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 |
|||
| cbdb4dd8f3 |
Update master for stable/yoga
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 |
|||
|
Zuul
|
a247fbcc8c | Merge "Refactor efi_utils for easier maintaining and debugging" 8.5.0 | ||
|
Zuul
|
f08f70134d | Merge "Improve efficiency of storage cleaning in mixed media envs" | ||
|
Jacob Anders
|
c5f7f18bcb |
Improve efficiency of storage cleaning in mixed media envs
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 |
||
|
Zuul
|
db981d07a4 | Merge "CI: be explicit that the jobs are using the DIB ramdisk" | ||
|
Zuul
|
6ddcf4895d | Merge "Add non-voting dib CentOS Stream 9 job" | ||
|
Zuul
|
de28b7bfdc | Merge "Create fstab entry with appropriate label" | ||
|
Julia Kreger
|
99ca1086db |
Create fstab entry with appropriate label
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 |
||
|
Riccardo Pittau
|
96673b1829 |
Add non-voting dib CentOS Stream 9 job
We recently enabled voting CS9 jobs in ipa-builder, let's also add the same check job here. Change-Id: Iaf2e56e0a1f6ca35272bcaedf3cb73273080b7ef |
||
|
Zuul
|
59c02f48cc | Merge "Run partx in verbose mode to simplify debugging" | ||
|
Zuul
|
63171c7f38 |
Merge "Add mount and parted -l to the collected commands"
|
||
|
Zuul
|
bcd5d11d9a | Merge "Rescan device after filesystem creation" | ||
|
Zuul
|
cf46443120 | Merge "Use utf-16-le if BOM not present" | ||
|
Riccardo Pittau
|
697fa6f3b6 |
Use utf-16-le if BOM not present
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 |
||
|
Dmitry Tantsur
|
48f30ab528 |
Stop defaulting the standalone job to netboot; use the correct boot mode
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 |
||
|
Dmitry Tantsur
|
f1ee454a0e |
Add mount and parted -l to the collected commands
Change-Id: I1c759552220291890704d0002a62ea3f51701691 |
||
|
Dmitry Tantsur
|
3d3df17e5a |
Refactor efi_utils for easier maintaining and debugging
* 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 |
||
|
Dmitry Tantsur
|
4d16ea413f |
Run partx in verbose mode to simplify debugging
Otherwise the actual failure cause is not recorded. Change-Id: If66ee97016ddf0e5c3f40ad9400ff3bc6fdebedc |
||
|
Arne Wiebalck
|
a83f38479e |
Move prepare_boot_partitions_for_softraid to raid_utils
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
|