summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Add support for CentOS SUM files"HEADmasterZuul2023-05-093-6/+180
|\
| * Add support for CentOS SUM filesHarald Jensås2023-05-033-6/+180
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The CentOS Stream SUM files uses format: # FILENAME: <size> bytes ALGORITHM (FILENAME) = CHECKSUM Compared to the more common format: CHECKSUM *FILE_A CHECKSUM FILE_B Use regular expressions to check for filename both in the middle with parentheses and at the end. Similarly look for valid checksums at beginning or end of line. Also look for know checsum patterns in case file only contain the checksum iteself. Change-Id: I9e49c1a6c66e51a7b884485f0bcaf7f1802bda33
* | Merge "Revert disabling MD5 checksums"Zuul2023-05-053-11/+6
|\ \
| * | Revert disabling MD5 checksumsDmitry Tantsur2023-05-043-11/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was a significant breaking change that was landed despite explicit disagreement by some community members (myself included). It has already resulted in an accidental Ironic CI breakage, has broken Bifrost and has a potential of breaking Metal3. In case of Metal3, MD5 support is a part of its public API. While MD5 is a potential security hazard, I don't see the need to hurry this change without giving the community time to prepare. This change reverts the new option md5_enabled to True. Change-Id: I32b291ea162e8eb22429712c15cb5b225a6daafd
* | | Merge "Add network interface speed to the inventory"Zuul2023-05-046-543/+614
|\ \ \ | |/ / |/| |
| * | Add network interface speed to the inventoryDmitry Tantsur2023-05-036-543/+614
| |/ | | | | | | | | | | | | This is another fact that Metal3's baremetal-operator is currently consuming from extra-hardware. Change-Id: I2ec9d5e9369f5508e7583a4e13c2083f5c8b28ba
* | Fix checksum validation logicJulia Kreger2023-05-022-2/+22
|/ | | | | | | | | | | The checksum validation logic, which was updated early on in the whole process of deprecating md5, didn't account for a URL *or* a longer checksum (i.e. sha256/sha512) which was decided while the overall approach was being decided. Fixes the logic, and adds additional tests. Change-Id: Ic4053776e131fc02ace295a1e69e9f9faab47f42
* Merge "Disable MD5 image checksums"Zuul2023-05-026-77/+456
|\
| * Disable MD5 image checksumsJulia Kreger2023-04-246-77/+456
| | | | | | | | | | | | | | | | | | | | | | | | MD5 image checksums have long been supersceeded by the use of a ``os_hash_algo`` and ``os_hash_value`` field as part of the properties of an image. In the process of doing this, we determined that checksum via URL usage was non-trivial and determined that an appropriate path was to allow the checksum type to be determined as needed. Change-Id: I26ba8f8c37d663096f558e83028ff463d31bd4e6
* | Merge "Deprecate LLDP in inventory in favour of a new collector"Zuul2023-04-277-32/+72
|\ \
| * | Deprecate LLDP in inventory in favour of a new collectorDmitry Tantsur2023-04-267-32/+72
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Binary LLDP data is bloating inventory causing us to disable its collection by default. For other similar low-level information, such as PCI devices or DMI data, we already use inspection collectors instead. Now that the inventory format is shared with out-of-band inspection, having LLDP there makes even less sense. This change adds a new collector ``lldp`` to replace the now-deprecated inventory field. Change-Id: I56be06a7d1db28407e1128c198c12bea0809d3a3
* | Merge "Fix UTF-16 result handling for efibootmgr"Zuul2023-04-274-63/+91
|\ \
| * | Fix UTF-16 result handling for efibootmgrJulia Kreger2023-04-174-63/+91
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tl;dr is that UEFI NVRAM is in encoded in UTF-16, and when we run the efibootmgr command, we can get unicode characters back. Except we previously were forcing everything to be treated as UTF-8 due to the way oslo.concurrency's processutils module works. This could be observed with UTF character 0x00FF which raises up a nice exception when we try to decode it. Anyhow! while fixing handling of this, we discovered we could get basically the cruft out of the NVRAM, by getting what was most likey a truncated string out of our own test VMs. As such, we need to also permit decoding to be tollerant of failures. This could be binary data or as simple as flipped bits which get interpretted invalid characters. As such, we have introduced such data into one of our tests involving UEFI record de-duplication. Closes-Bug: 2015602 Change-Id: I006535bf124379ed65443c7b283bc99ecc95568b
* | Upgrade to latest hacking - v6Jay Faulkner2023-04-211-1/+1
|/ | | | | | No code changes needed to comply with newest flake. Change-Id: I256397efe0fbb3e307d808b0eda2e4d72d83f9b0
* Report system firmware information in the inventoryDmitry Tantsur2023-03-316-20/+90
| | | | Change-Id: I5b6ceb9cdcf4baa97a6f0482d1030d14f3f2ecff
* Trivial: formatting issue in the inventory docsDmitry Tantsur2023-03-301-1/+1
| | | | | | Double ticks don't work if followed by a symbol without space. Change-Id: Ia455650b5e601dadb2b0ab91f71e1d9286d26071
* [Trivial] Fix typo in efi_utilsArne Wiebalck2023-03-151-1/+1
| | | | Change-Id: I692e045e6bc8683038a2e85a6a132687d2b30f18
* Update master for stable/2023.1OpenStack Release Bot2023-03-092-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/2023.1. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2023.1. Sem-Ver: feature Change-Id: Id58fd751e6ed8ed3d478a78a6895cad75667c9b1
* Merge "update NVIDIA NIC firmware images and settings by ironic-python-agent"9.4.0Zuul2023-01-316-0/+2159
|\
| * update NVIDIA NIC firmware images and settings by ironic-python-agentwaleed mousa2023-01-116-0/+2159
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add "update_nvidia_nic_firmware_image" and "update_nvidia_nic_firmware_settings" clean steps to MellanoxDeviceHardwareManager. By adding those two steps, we can update the firmware image and firmware settings of NVIDIA NICs by ironic-python-agent using manual cleaning command The clean steps require mstflint package installed on the image. The "update_nvidia_nic_firmware_image" clean step requires to pass "images" parameter to the clean command The "images" parameter is a json blob contains a list of images, where each image contains a map of: * url: to firmware image (file://, http://) * checksum: checksum of the provided image * checksumType: md5/sha512/sha256 * componentFlavor: PSID of the nic * version: version of the FW The "update_nvidia_nic_firmware_settings" clean step requires to pass "settings" parameter to the clean command The "settings" parameter is a json blob contains a list of settings, where each settings contains a map of: * deviceID: device ID * globalConfig: global config * function0Config: function 0 config * function1Config: function 1 config Change-Id: Icfaffd7c58c3c73c3fa28cfc2a6c954d2c93c16e Story: 2010228 Task: 46016
* | Merge "Make logs collection a hardware manager call"9.3.0Zuul2023-01-265-156/+161
|\ \
| * | Make logs collection a hardware manager callDmitry Tantsur2023-01-255-156/+161
| |/ | | | | | | | | | | This allows hardware managers to collect additional logs. Change-Id: If082b921d4bf71c4cc41a5a72db6995b08637374
* | Merge "Readd usedevelop true to tox.ini"Zuul2023-01-261-0/+1
|\ \
| * | Readd usedevelop true to tox.iniRiccardo Pittau2023-01-251-0/+1
| |/ | | | | | | | | | | This avoid using sdist, which is the wanted behavior Change-Id: Ibfb867ee0ff8274130a19538aa7ff9b9296dc4e1
* | Make reno ignore bugfix eol tagsJay Faulkner2023-01-251-0/+2
|/ | | | | | | | | Reno was assuming all tags ending in -eol represented an old, EOL'd stable branch. That's not true for Ironic projects which have bugfix branches. Update the regexp to exclude those branches. Co-Authored-By: Adam McArthur <adam@mcaq.me> Change-Id: I265969ab40a98a02962c2fc8460b6519ab576f99
* Merge "modify error word node"Zuul2023-01-041-1/+1
|\
| * modify error word nodeliuyuanfeng2022-12-301-1/+1
| | | | | | | | Change-Id: Ie5c9fa7489eb891ef1bbe57c7d51ecb64e1c0db8
* | Remove old, unused proxy.sh fileJay Faulkner2023-01-031-6/+0
| | | | | | | | | | | | This should've been removed with the rest of the contents of imagebuild/ Change-Id: I2ce3ad155d2963352daa5ea8d983d35e8f41eb19
* | Fix for tox4 and setuptoolsRiccardo Pittau2023-01-023-1/+2
|/ | | | | | | | | | | | - Disable auto discovery in setuptools This is to avoid issues with latest setuptools after version 61.0 For more info see [1] - add bash script to allowlist in tox.ini - use default size for vm memory [1] https://github.com/pypa/setuptools/issues/3197 Change-Id: Iae24917add1aae6b1ed46dba0d2c270b39c5698c
* Merge "Fix create configuration unit tests"Zuul2022-12-161-0/+2
|\
| * Fix create configuration unit testsRiccardo Pittau2022-12-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | The unit tests for create_configuration give different result if ran on a bios or uefi booted machine because they get the partition table type value based on the utils function get_node_boot_mode. Let's mock the boot_mode as we do in other tests to get an independent result. Change-Id: Ic0e7daea7ec4ce0806cd126c27166f84690c5d9e
* | Fixes for tox 4.0Jay Faulkner2022-12-151-7/+8
|/ | | | | | | - passenv needed better structure - usedevelop no longer allowed alongside skipsdist Change-Id: I22dae3b1e4cca2dc328c21e889acf7fe98a80e0b
* Merge "Fix failure of bind mount in _install_grub2"9.2.0bugfix/9.2Zuul2022-10-172-3/+46
|\
| * Fix failure of bind mount in _install_grub2Vanou Ishii2022-09-222-3/+46
| | | | | | | | | | | | | | | | | | | | | | | | When IPA runs _install_grub2, IPA tries to bind mount /dev, /proc and /run to <temporal directory path root partition mounted>/{dev,proc,run}. However that bind mount fails because there aren't such mount point path under temporal directory. To fix this failure, this patch add mkdir command before bind mount. Story: 2010292 Task: 46273 Change-Id: I434ce1bf1863ee0f11c4d09918d6d2d8dc065c02
* | Merge "prioritize lsblk as a source of device serials"Zuul2022-10-146-77/+190
|\ \
| * | prioritize lsblk as a source of device serialsRozzii2022-10-106-77/+190
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current way of prioritizing ID/DM_SERIAL_SHORT or ID/DM_SERIAL works in most cases but the udev values seem to be unreliable. Based on experience it looks like lsblk might be a better source of truth than udev in regerards to serial number information. This commit makes lsblk the default provider of block device serial number information. Story: 2010263 Task: 46161 Change-Id: I16039b46676f1a61b32ee7ca7e6d526e65829113
* | | Merge "Update release versions for yoga"Zuul2022-10-141-3/+3
|\ \ \ | |/ / |/| |
| * | Update release versions for yogaRiccardo Pittau2022-09-231-3/+3
| | | | | | | | | | | | Change-Id: I06d14bc499a7c081fe73b68de6c49e2f1bc51dc5
* | | Switch to 2023.1 Python3 unit tests and generic template nameOpenStack Release Bot2022-09-231-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for antelope. Also, updating the template name to generic one. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: I91232b32f26842802fc42c1d9e28a6ea791ecb7b
* | | Update master for stable/zedOpenStack Release Bot2022-09-232-0/+7
|/ / | | | | | | | | | | | | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/zed. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/zed. Sem-Ver: feature Change-Id: Iff9b5efee0b436357d5cae3909a89cd09d5e6070
* | Merge "add openstack-python3-zed-jobs-arm64 job"9.1.0Zuul2022-09-201-0/+1
|\ \
| * | add openstack-python3-zed-jobs-arm64 joblikui2022-08-291-0/+1
| | | | | | | | | | | | | | | | | | This is a non-voting job to validate py3 unittests on ARM64 Change-Id: I608d2e4e9e378b1f6e33a7e1a2cdc1c0bab7ec5c
* | | SoftwareRAID: Enable skipping RAIDSJakub Jelinek2022-09-058-59/+750
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | Extend the ability to skip disks to RAID devices This allows users to specify the volume name of a logical device in the skip list which is then not cleaned or created again during the create/apply configuration phase The volume name can be specified in target raid config provided the change https://review.opendev.org/c/openstack/ironic-python-agent/+/853182/ passes Story: 2010233 Change-Id: Ib9290a97519bc48e585e1bafb0b60cc14e621e0f
* | Merge "Create RAIDs with volume name"Zuul2022-09-025-44/+117
|\ \ | |/ |/|
| * Create RAIDs with volume nameJakub Jelinek2022-09-025-44/+117
| | | | | | | | | | | | | | | | Use 'volume_name' field from 'target_raid_config' to create logical disks if it is present Do not allow two logical disks to have the same volume name Change-Id: If3e4e9f8698ec3e0cb49717f8ed2087d2ba03f2c
* | Trivial: Fix reno for software raid fixJulia Kreger2022-08-251-1/+1
| | | | | | | | | | | | | | Fixes the release note for If721dfe1caa5915326482969e55fbf4697538231. Change-Id: I9971d12665f2c8a4fdfe82911c6173021d03ddc0
* | Merge "Fix software raid output poisoning"Zuul2022-08-254-1/+43
|\ \
| * | Fix software raid output poisoningJulia Kreger2022-08-244-1/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | remove unicode prefix from codeniuke2022-08-232-11/+11
|/ / | | | | | | Change-Id: I70f0112f1ee3066ffd9316d10b84b9ea5b7fc306
* | Merge "Improve function list_block_devices_check_skip_list"Zuul2022-08-172-25/+20
|\ \
View Lorry Controller Status