summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Merge "Gather details about bond interfaces if present"Zuul2022-07-023-11/+66
|\ \ \
| * | | Gather details about bond interfaces if presentDerek Higgins2022-06-213-11/+66
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | If present gather information about bonded interfaces. Story: #2010093 Task: #45637 Change-Id: I394187640b4788ebec21c3391d33ed728fb72ffa
* | | Merge "Remove oslo.serialization dependency"Zuul2022-07-027-27/+33
|\ \ \
| * | | Remove oslo.serialization dependencyRiccardo Pittau2022-06-177-27/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use pure json instead of jsonutils. Borrow encode function from oslo.serialization to be used in the utils module. Change-Id: Ied9a2259a4329a86b4f0853bd1fb187563c0a036
* | | | Merge "Collect udev properties in the ramdisk logs"Zuul2022-07-023-4/+89
|\ \ \ \
| * | | | Collect udev properties in the ramdisk logsDmitry Tantsur2022-06-173-4/+89
| | |/ / | |/| | | | | | | | | | Change-Id: Ifcf3dfff00b604dec1e2f430369ab8053f50f137
* | | | Merge "Use json for lsblk output"Zuul2022-06-304-201/+226
|\ \ \ \ | | |/ / | |/| |
| * | | Use json for lsblk outputRiccardo Pittau2022-06-144-201/+226
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge "Warn when smartctl not found"Zuul2022-06-271-1/+2
|\ \ \
| * | | Warn when smartctl not foundMark Goddard2022-06-241-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Merge "Add ipa-tox-examples job to gate"Zuul2022-06-251-0/+1
|\ \ \ \
| * | | | Add ipa-tox-examples job to gateRiccardo Pittau2022-05-311-0/+1
| | |/ / | |/| | | | | | | | | | | | | | | | | | The ipa-tox-examples job is voting but it's missing from gate Change-Id: Ie47066084172d8e06eb1f6f097b0354b3b800612
* | | | Merge "Remove importlib-metadata from requirements"Zuul2022-06-242-7/+1
|\ \ \ \
| * | | | Remove importlib-metadata from requirementsRiccardo Pittau2022-06-212-7/+1
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Merge "Drop support for Python 3.6 and 3.7"Zuul2022-06-231-3/+1
|\ \ \ \
| * | | | Drop support for Python 3.6 and 3.7Riccardo Pittau2022-05-311-3/+1
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Fix discovering WWN/serial for devicemapper devicesDmitry Tantsur2022-06-143-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
* | | Merge "Add a metalsmith job with legacy boot"Zuul2022-05-302-2/+16
|\ \ \
| * | | Add a metalsmith job with legacy bootDmitry Tantsur2022-05-172-2/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Update oslo.log requirement to 4.6.1Julia Kreger2022-05-241-1/+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
* | | | Multipath Hardware path handlingJulia Kreger2022-05-188-57/+748
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 "Remove support for distributions with Python 3.6"Zuul2022-05-171-3/+1
|\ \ \ | |/ /
| * | Remove support for distributions with Python 3.6Dmitry Tantsur2022-05-121-3/+1
| | | | | | | | | | | | | | | | | | | | | 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
* | | Merge "Drop lower-constraints.txt and its testing"Zuul2022-05-163-35/+0
|\ \ \
| * | | Drop lower-constraints.txt and its testingRiccardo Pittau2022-05-103-35/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Merge "Revert "The Python 3.6 and Python 3.7Support has been dropped since ↵Zuul2022-05-161-1/+3
|\ \ \ \ | |_|/ / |/| | | | | | | yaga""
| * | | Revert "The Python 3.6 and Python 3.7Support has been dropped since yaga"Dmitry Tantsur2022-05-161-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit c4d2851a13910cc36c46034ba87e6775f8c2b20b. Reason for revert: 3.6 is not broken yet, except that this change breaks it. Let us revert until we fully switch to Stream 9. Change-Id: Ia2870135a90128f744afb9c45524ab003878843f
* | | | Merge "The Python 3.6 and Python 3.7Support has been dropped since yaga"Zuul2022-05-111-3/+1
|\ \ \ \ | |/ / / | | / / | |/ / |/| |
| * | The Python 3.6 and Python 3.7Support has been dropped since yagalikui2022-05-091-3/+1
| | | | | | | | | | | | | | | | | | [1] https://governance.openstack.org/tc/reference/runtimes/zed.html Change-Id: Ifeec26e57dd2b2908da4f161032b37edf99cb8b8
* | | Merge "Collect a full lsblk output in the ramdisk logs"Zuul2022-05-093-16/+10
|\ \ \ | |/ / |/| |
| * | Collect a full lsblk output in the ramdisk logsDmitry Tantsur2022-04-293-16/+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
* | | Merge "Do not try to guess EFI partition path by its number"8.6.0Zuul2022-05-055-58/+142
|\ \ \
| * | | 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
|\ \ \ \ \
View Lorry Controller Status