- Release-announce - lists.openstack.org

blazar-nova 6.0.0.0rc1 (dalmatian)
by no-reply＠openstack.org 13 Sep '24

13 Sep '24

Hello everyone, A new release candidate for blazar-nova for the end of the Dalmatian cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/blazar-nova/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Dalmatian release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/dalmatian release branch at: https://opendev.org/openstack/blazar-nova/src/branch/stable/dalmatian Release notes for blazar-nova can be found at: https://docs.openstack.org/releasenotes/blazar-nova/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/blazar/+bugs and tag it *dalmatian-rc-potential* to bring it to the blazar-nova release crew's attention.

1 0

skyline-apiserver 5.0.0.0rc1 (dalmatian)
by no-reply＠openstack.org 13 Sep '24

13 Sep '24

Hello everyone, A new release candidate for skyline-apiserver for the end of the Dalmatian cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/skyline-apiserver/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Dalmatian release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/dalmatian release branch at: https://opendev.org/openstack/skyline-apiserver/src/branch/stable/dalmatian Release notes for skyline-apiserver can be found at: https://docs.openstack.org/releasenotes/skyline-apiserver/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/skyline-apiserver/+bugs and tag it *dalmatian-rc-potential* to bring it to the skyline-apiserver release crew's attention.

1 0

skyline-console 5.0.0.0rc1 (dalmatian)
by no-reply＠openstack.org 13 Sep '24

13 Sep '24

Hello everyone, A new release candidate for skyline-console for the end of the Dalmatian cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/skyline-console/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Dalmatian release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/dalmatian release branch at: https://opendev.org/openstack/skyline-console/src/branch/stable/dalmatian Release notes for skyline-console can be found at: https://docs.openstack.org/releasenotes/skyline-console/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/skyline-apiserver/+bugs and tag it *dalmatian-rc-potential* to bring it to the skyline-console release crew's attention.

1 0

manila 19.0.0.0rc1 (dalmatian)
by no-reply＠openstack.org 13 Sep '24

13 Sep '24

Hello everyone, A new release candidate for manila for the end of the Dalmatian cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/manila/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Dalmatian release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/dalmatian release branch at: https://opendev.org/openstack/manila/src/branch/stable/dalmatian Release notes for manila can be found at: https://docs.openstack.org/releasenotes/manila/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/manila/+bugs and tag it *dalmatian-rc-potential* to bring it to the manila release crew's attention.

1 0

neutron 25.0.0.0rc1 (dalmatian)
by no-reply＠openstack.org 13 Sep '24

13 Sep '24

Hello everyone, A new release candidate for neutron for the end of the Dalmatian cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Dalmatian release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/dalmatian release branch at: https://opendev.org/openstack/neutron/src/branch/stable/dalmatian Release notes for neutron can be found at: https://docs.openstack.org/releasenotes/neutron/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/neutron/+bugs and tag it *dalmatian-rc-potential* to bring it to the neutron release crew's attention.

1 0

adjutant 9.0.0.0rc1 (dalmatian)
by no-reply＠openstack.org 13 Sep '24

13 Sep '24

Hello everyone, A new release candidate for adjutant for the end of the Dalmatian cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/adjutant/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Dalmatian release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/dalmatian release branch at: https://opendev.org/openstack/adjutant/src/branch/stable/dalmatian Release notes for adjutant can be found at: https://docs.openstack.org/releasenotes/adjutant/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/openstack/adjutant and tag it *dalmatian-rc-potential* to bring it to the adjutant release crew's attention.

1 0

tacker-horizon 10.0.0.0rc1 (dalmatian)
by no-reply＠openstack.org 13 Sep '24

13 Sep '24

Hello everyone, A new release candidate for tacker-horizon for the end of the Dalmatian cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tacker-horizon/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Dalmatian release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/dalmatian release branch at: https://opendev.org/openstack/tacker-horizon/src/branch/stable/dalmatian Release notes for tacker-horizon can be found at: https://docs.openstack.org/releasenotes/tacker-horizon/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/tacker/+bugs and tag it *dalmatian-rc-potential* to bring it to the tacker-horizon release crew's attention.

1 0

blazar-dashboard 12.0.0.0rc1 (dalmatian)
by no-reply＠openstack.org 13 Sep '24

13 Sep '24

Hello everyone, A new release candidate for blazar-dashboard for the end of the Dalmatian cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/blazar-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Dalmatian release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/dalmatian release branch at: https://opendev.org/openstack/blazar-dashboard/src/branch/stable/dalmatian Release notes for blazar-dashboard can be found at: https://docs.openstack.org/releasenotes/blazar-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/blazar/+bugs and tag it *dalmatian-rc-potential* to bring it to the blazar-dashboard release crew's attention.

1 0

ironic 21.4.3 (antelope)
by no-reply＠openstack.org 12 Sep '24

12 Sep '24

We contentedly announce the release of: ironic 21.4.3: OpenStack Bare Metal Provisioning This release is part of the antelope release series. The source is available from: https://opendev.org/openstack/ironic Download the package from: https://tarballs.openstack.org/ironic/ Please report issues through: https://storyboard.openstack.org/#!/project/943 For more details, please see below. 21.4.3 ^^^^^^ Upgrade Notes ************* * When upgrading Ironic to address the "qemu-img" image conversion security issues, the "ironic-python-agent" ramdisks will also need to be upgraded. * When upgrading Ironic to address the "qemu-img" image conversion security issues, the "[conductor]conductor_always_validates_images" setting may be set to "True" as a short term remedy while "ironic- python-agent" ramdisks are being updated. Alternatively it may be advisable to also set the "[agent]image_download_source" setting to "local" to minimize redundant network data transfers. * As a result of security fixes to address "qemu-img" image conversion security issues, a new configuration parameter has been added to Ironic, "[conductor]permitted_image_formats" with a default value of "raw,qcow2,iso". Raw and qcow2 format disk images are the image formats the Ironic community has consistently stated as what is supported and expected for use with Ironic. These formats also match the formats which the Ironic community tests. Operators who leverage other disk image formats, may need to modify this setting further. Security Issues *************** * Ironic now checks the supplied image format value against the detected format of the image file, and will prevent deployments should the values mismatch. If being used with Glance and a mismatch in metadata is identified, it will require images to be re-uploaded with a new image ID to represent corrected metadata. This is the result of CVE-2024-44082 tracked as bug 2071740 (https://bugs.launchpad.net/ironic/+bug/2071740) * Ironic *always* inspects the supplied user image content for safety prior to deployment of a node should the image pass through the conductor, even if the image is supplied in "raw" format. This is utilized to identify the format of the image and the overall safety of the image, such that source images with unknown or unsafe feature usage are explicitly rejected. This can be disabled by setting "[conductor]disable_deep_image_inspection" to "True". This is the result of CVE-2024-44082 tracked as bug 2071740 (https://bugs.launchpad.net/ironic/+bug/2071740) * Ironic can also inspect images which would normally be provided as a URL for direct download by the "ironic-python-agent" ramdisk. This is not enabled by default as it will increase the overall network traffic and disk space utilization of the conductor. This level of inspection can be enabled by setting "[conductor]conductor_always_validates_images" to "True". Once the "ironic-python-agent" ramdisk has been updated, it will perform similar image security checks independently, should an image conversion be required. This is the result of CVE-2024-44082 tracked as bug 2071740 (https://bugs.launchpad.net/ironic/+bug/2071740) * Ironic now explicitly enforces a list of permitted image types for deployment via the "[conductor]permitted_image_formats" setting, which defaults to "raw", "qcow2", and "iso". While the project has classically always declared permissible images as "qcow2" and "raw", it was previously possible to supply other image formats known to "qemu-img", and the utility would attempt to convert the images. The "iso" support is required for "boot from ISO" ramdisk support. * Ironic now explicitly passes the source input format to executions of "qemu-img" to limit the permitted qemu disk image drivers which may evaluate an image to prevent any mismatched format attacks against "qemu-img". * The "ansible" deploy interface example playbooks now supply an input format to execution of "qemu-img". If you are using customized playbooks, please add "-f {{ ironic.image.disk_format }}" to your invocations of "qemu-img". If you do not do so, "qemu-img" will automatically try and guess which can lead to known security issues with the incorrect source format driver. * Operators who have implemented any custom deployment drivers or additional functionality like machine snapshot, should review their downstream code to ensure they are properly invoking "qemu-img". If there are any questions or concerns, please reach out to the Ironic project developers. * Operators are reminded that they should utilize cleaning in their environments. Disabling any security features such as cleaning or image inspection are at **your** **own** **risk**. Should you have any issues with security related features, please don't hesitate to open a bug with the project. * The "[conductor]disable_deep_image_inspection" setting is conveyed to the "ironic-python-agent" ramdisks automatically, and will prevent those operating ramdisks from performing deep inspection of images before they are written. * The "[conductor]permitted_image_formats" setting is conveyed to the "ironic-python-agent" ramdisks automatically. Should a need arise to explicitly permit an additional format, that should take place in the Ironic service configuration. Bug Fixes ********* * Fixes multiple issues in the handling of images as it relates to the execution of the "qemu-img" utility, which is used for image format conversion, where a malicious user could craft a disk image to potentially extract information from an "ironic-conductor" process's operating environment. Ironic now explicitly enforces a list of approved image formats as a "[conductor]permitted_image_formats" list, which mirrors the image formats the Ironic project has historically tested and expressed as known working. Testing is not based upon file extension, but upon content fingerprinting of the disk image files. This is tracked as CVE-2024-44082 via bug 2071740 (https://bugs.launchpad.net/ironic/+bug/2071740) Changes in ironic 21.4.2..21.4.3 -------------------------------- d409512b4 CI: stable/2023.1 - remove partition and older non-voting jobs 188d43616 CVE-2024-44982: Harden all image handling and conversion code 12b49a29d [CI][stable only] fix zuul config 2e1bfeb15 [CI] Fix job parent name Diffstat (except docs and test files) ------------------------------------- ironic/api/controllers/v1/ramdisk.py | 2 + ironic/common/exception.py | 4 + ironic/common/image_format_inspector.py | 1038 ++++++++++++++++++++ ironic/common/images.py | 152 ++- ironic/common/qemu_img.py | 89 ++ ironic/conf/__init__.py | 2 + ironic/conf/conductor.py | 43 + ironic/conf/disk_utils.py | 33 + ironic/conf/opts.py | 1 + .../playbooks/roles/deploy/tasks/write.yaml | 2 +- ironic/drivers/modules/deploy_utils.py | 202 +++- ironic/drivers/modules/image_cache.py | 71 +- .../unit/drivers/modules/test_deploy_utils.py | 515 +++++++++- .../address-qemu-issues-1bbead8bb70b76fb.yaml | 108 ++ zuul.d/ironic-jobs.yaml | 3 +- zuul.d/project.yaml | 18 - 25 files changed, 3500 insertions(+), 184 deletions(-)

1 0

ironic-python-agent 9.7.2 (bobcat)
by no-reply＠openstack.org 12 Sep '24

12 Sep '24

We are glad to announce the release of: ironic-python-agent 9.7.2: Ironic Python Agent Ramdisk This release is part of the bobcat release series. The source is available from: https://opendev.org/openstack/ironic-python-agent Download the package from: https://tarballs.openstack.org/ironic-python-agent/ Please report issues through: https://storyboard.openstack.org/#!/project/openstack/ironic- python-agent For more details, please see below. 9.7.2 ^^^^^ Upgrade Notes ************* * Deployers implementing their own "HardwareManagers" must to audit their code for unsafe uses of *qemu-img* and related methods. Security Issues *************** * Ironic-Python-Agent now checks any supplied image format value against the detected format of the image file and will prevent deployments should the values mismatch. * Images previously misconfigured as raw despite being in another format, in some non-default configurations, may have been mistakenly converted if needed. Ironic-Python-Agent will no longer perform conversion in any case for images with metadata indicating in raw format. * Ironic-Python-Agent *always* inspects any non-raw user image content for safety before running any qemu-based utilities on the image. This is utilized to identify the format of the image and to verify the overall safety of the image. Any images with unknown or unsafe feature uses are explicitly rejected. This can be disabled in both IPA and Ironic by setting "[conductor]disable_deep_image_inspection" to "True" for the Ironic deployment. Image inspection is the primary mitigation for CVE-2024-44082 being tracked in bug 2071740 (https://bugs.launchpad.net/ironic-python-agent/+bug/2071740) Operators may desire to set "[conductor]conductor_always_validates_images" on Ironic conductors to mitigate the issue before they have upgraded their Ironic-Python- Agent. * Ironic-Python-Agent now explicitly enforces a list of permitted image types for deployment, defaulting to "raw" and "qcow2". Other image types may work, but are not explicitly supported and must be enabled. This can be modified by setting "[conductor]permitted_image_formats" for all Ironic services. Bug Fixes ********* * Fixes an issue where configuration drive volumes which are mounted by the operating system could remain mounted and cause a lock to be held, which may conflict with actions such as "rebuild". The agent now always makes sure the folder used by Glean and Cloud-init is not mounted. * Fixes multiple issues in the handling of images as it related to execution of the "qemu-img" utility. When using this utility to convert an unsafe image, a malicious user can extract information from a node while Ironic-Python-Agent is deploying or converting an image. Ironic-Python-Agent now inspects all non-raw images for safety, and never runs qemu-based utilities on raw images. This fix is tracked as CVE-2024-44082 and bug 2071740 (https://bugs.launchpad.net/ironic-python-agent/+bug/2071740) * Images with metadata indicating a "raw" disk format may have been transparently converted from another format. Now, these images will have their exact contents imaged to disk without modification. * Fixes bug 2066308, an issue where Ironic Python Agent would call evaluate_hardware_support multiple times on hardware manager plugins. Scanning for hardware and disks is time consuming, and caused timeouts on badly-performing nodes. Changes in ironic-python-agent 9.7.1..9.7.2 ------------------------------------------- b7fa84d Inspect non-raw images for safety 9008eca Remove and disable examples job b066a21 Call evaluate_hardware_support exactly once per hwm 0337474 Unmount config drives Diffstat (except docs and test files) ------------------------------------- ironic_python_agent/agent.py | 6 + ironic_python_agent/config.py | 69 +- ironic_python_agent/disk_partitioner.py | 125 +++ ironic_python_agent/disk_utils.py | 788 +++++++++++++++ ironic_python_agent/errors.py | 9 + ironic_python_agent/extensions/standby.py | 86 +- ironic_python_agent/format_inspector.py | 1044 +++++++++++++++++++ ironic_python_agent/hardware.py | 67 +- ironic_python_agent/partition_utils.py | 11 +- ironic_python_agent/qemu_img.py | 153 +++ ironic_python_agent/utils.py | 28 + ...-config-drive-is-umounted-a3985bbb45e89051.yaml | 8 + .../notes/image-security-5c23b890409101c9.yaml | 48 + ...ate-hardware-support-once-9ec1ae327b4e03f2.yaml | 7 + zuul.d/ironic-python-agent-jobs.yaml | 17 +- zuul.d/project.yaml | 2 - 27 files changed, 4305 insertions(+), 199 deletions(-)

1 0