Zuul [Tue, 23 Dec 2025 02:14:09 +0000 (02:14 +0000)]
Update git submodules
* Update masakari-monitors from branch 'master'
to df7ed7b178c811a761bf9c793f928f9ed30ebd90
- Merge "Host-Monitor kubernetes_check host-status missing"
- Host-Monitor kubernetes_check host-status missing
Payload data from masakari-host-monitor process was missing the
host_status parameter to allow the masakari-engine to initiate
the recovery workflow message to the API server. Previous payload
would be ignored by masakari-engine workflow driver.
Zuul [Mon, 22 Dec 2025 21:02:59 +0000 (21:02 +0000)]
Update git submodules
* Update ironic from branch 'master'
to 6a18c386a6830fb6c3abffaa2cf5b577090ed15b
- Merge "Use oslo.config to split [console] port_range"
- Use oslo.config to split [console] port_range
Zuul [Mon, 22 Dec 2025 16:30:06 +0000 (16:30 +0000)]
Update git submodules
* Update openstacksdk from branch 'master'
to 12f9b903de8804494bb93f772350a9d4a429c8ef
- Merge "Add secure hash validation for image downloads"
- Add secure hash validation for image downloads
Add support for validating image downloads using secure hash algorithms
(SHA256, SHA512, etc.) via the ``os_hash_algo`` and ``os_hash_value``
metadata fields. This addresses the limitation of MD5-only validation
and improves data integrity verification.
Zuul [Mon, 22 Dec 2025 15:49:58 +0000 (15:49 +0000)]
Update git submodules
* Update ironic-python-agent-builder from branch 'master'
to c82015b70f582526071f1bc0e598ef4da3ffcb75
- Merge "Make multiple integration jobs voting"
- Make multiple integration jobs voting
A risk exists that we just sort of ingore an integration job
failure with an IPA change which might be a legitimate issue.
The key is that we really need to just fix the jobs when they
fail, and not leave jobs in non-voting status for long periods
of times.
So this, in order to help head off merging breaking changes
which might break a non-voting job, elevates those non-voting
jobs to voting.
Change-Id: I77249daf4bebeaead25ea87757de38b272e6ac7a Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
pip 23.1 removed the "setup.py install" fallback for projects
that do not have pyproject.toml and now uses a pyproject.toml
which is vendored in pip.
To address that, this change adds the minimal pyproject.toml
to enable pbr to be properly used to build editable wheels.
See https://pip.pypa.io/en/stable/news/#v23-1
and https://github.com/pypa/pip/issues/8368 for more
details on the removal of the fallback support.
Co-Authored-By: Sean Mooney <work@seanmooney.info>
Change-Id: I08e1ff67febd4cf518e8a8c75621224bbd816ab0 Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
Zuul [Mon, 22 Dec 2025 15:13:13 +0000 (15:13 +0000)]
Update git submodules
* Update openstack-ansible from branch 'master'
to 4c6664210068b66cb32268f65b5f20eaf7cadd64
- Merge "Do not define openstack_pki_san in integrated repo"
- Do not define openstack_pki_san in integrated repo
Explicit definition of `openstack_pki_san` in integrated repository is
reduntant because all service roles using PKI role already have a
`default()` filter applied that matches the value of `openstack_pki_san`
in integrated repo.
It's not necessary to define `openstack_pki_san` in integrated repo.
This patch removes it. However, it still can be used by the users to
override cert SAN globally for all openstack services.
Zuul [Mon, 22 Dec 2025 15:01:31 +0000 (15:01 +0000)]
Update git submodules
* Update python-masakariclient from branch 'master'
to fff1bc7376ff1e5c1ee7dd3aeb58b6896541530a
- Merge "add pyproject.toml to support pip 23.1"
- add pyproject.toml to support pip 23.1
pip 23.1 removed the "setup.py install" fallback for projects
that do not have pyproject.toml and now uses a pyproject.toml
which is vendored in pip.
To address that, this change adds the minimal pyproject.toml
to enable pbr to be properly used to build editable wheels.
See https://pip.pypa.io/en/stable/news/#v23-1
and https://github.com/pypa/pip/issues/8368 for more
details on the removal of the fallback support.
Co-Authored-By: Sean Mooney <work@seanmooney.info>
Change-Id: I16cd156ea443041b93aeffa8364a48fa4bcc62be Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
Zuul [Mon, 22 Dec 2025 14:33:47 +0000 (14:33 +0000)]
Update git submodules
* Update cloudkitty from branch 'master'
to f524e9261f0da9b1a48a210a53b63c27a68b9374
- Merge "Check that the limit is never over 5000 in Loki queries"
- Check that the limit is never over 5000 in Loki queries
Loki has hard limit of 5000 rows it can return at once, and if the user
tries to bring more, it will just deny the request. Instead of
delegating the request denial to Loki, we add the proper checks before
the queries are done, so we can properly inform the user that more than
5000 rows is not acceptable.
Change-Id: I9b98bb7d0c51724b1a63e2ecbf01ffe4a4f1c8e6 Signed-off-by: Juan Larriba <jlarriba@redhat.com>
Zuul [Mon, 22 Dec 2025 12:31:53 +0000 (12:31 +0000)]
Update git submodules
* Update python-masakariclient from branch 'master'
to 916f5dcd332ff6e954ea38fbfecffb2d3028922b
- Merge "Remove unnecessary hacking from test reqs"
- Remove unnecessary hacking from test reqs
It is used in only pep8 target which does not actually use
the requirements files.
Also remove the outdated note about pip's dependency resolver and adds
the note about lower bounds (which are no longer tested).
Zuul [Mon, 22 Dec 2025 12:26:33 +0000 (12:26 +0000)]
Update git submodules
* Update python-masakariclient from branch 'master'
to 1d0a9ba6dcfbb9d140c141b5862e53825e17510f
- Merge "Remove support for Python 3.8 and 3.9"
- Remove support for Python 3.8 and 3.9
These two old versions are no longer tested due to their EOL.
Zuul [Mon, 22 Dec 2025 12:17:45 +0000 (12:17 +0000)]
Update git submodules
* Update ironic-python-agent-builder from branch 'master'
to 40b946c1c10fe86b8f6f5b321f6329e75b9970b3
- Merge "Lockout configdrive reads on network boots"
- Lockout configdrive reads on network boots
We discovered it was possible, when the agent was network
booted, due to the model of "don't break existing users"
coding, that it was possible for the script to consider
a standing config drive as valid. This could result in
configuration getting loaded from the configuration drive
which is a security issue, but only for the networking portion
of the configuration due to the use of glean instead of
cloud-init.
We since reverted out the default to have simple-init enabled,
and this change fixes the load logic so we prevent these possible
cases considering that ironic deployments using virtual media
should now all be on code bases with the publisher ID value set.
Change-Id: If2a63fd16d8ae8e71b61b39f7c0c87ff45a81cf0 Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
Zuul [Sat, 20 Dec 2025 08:01:02 +0000 (08:01 +0000)]
Update git submodules
* Update kolla-ansible from branch 'master'
to 07b261bb86381f0c736289f31593d542e6238310
- Merge "Add support for Debian Trixie (13)"
- Add support for Debian Trixie (13)
Remove /etc/timezone bind mount since Debian does not provide
that file anymore.
Zuul [Fri, 19 Dec 2025 22:30:31 +0000 (22:30 +0000)]
Update git submodules
* Update openstack-ansible-plugins from branch 'master'
to e1cc9bc28e6b2968af6a517bd680f1d5d7288029
- Merge "Check for a supported Operating System - add information about AlmaLinux"
- Check for a supported Operating System - add information about AlmaLinux
Change-Id: I797c4cf0ffe88154b808a26fafd257c0e5bff016 Signed-off-by: Ivan Anfimov <lazekteam@gmail.com>
Zuul [Fri, 19 Dec 2025 22:20:08 +0000 (22:20 +0000)]
Update git submodules
* Update cinder from branch 'master'
to 2bdc892a023d2bbdf8e66e0e9645a86b776fcf61
- Merge "NFS driver: Fix driver fails to verify virtual size for Glance with Cinder/NFS"
- NFS driver: Fix driver fails to verify virtual size for Glance with Cinder/NFS
Glance images stored in Cinder with NFS as backend are sized in
the Cinder database to match the data size of the Image-volume
instead of the virtual_size. This prevents storage
resource to be unnecessarily allocated, but may also results into
errors in operations that requires checking for volume size
consistency.
Such checks aims to prevent users from extending NFS volumes
from within the virtual machine and outside of Cinder scope, by
comparing the virtual size of the NFS image with its size stored
in Cinder's database.
This patch changes how volume size is verified to fail only when
a volume virtual size has been extended in size instead of trying
to verify the exact size in bytes.
Closes-Bug: #2073146
Change-Id: I5c2216b72dda6bb3316ef30b352a6a8efe3a0429 Signed-off-by: Fernando Ferraz Silva <fesilva@redhat.com>
Zuul [Fri, 19 Dec 2025 22:19:52 +0000 (22:19 +0000)]
Update git submodules
* Update cinder from branch 'master'
to bb3895590cc58e238a6a9a67d8829484aded04f5
- Merge "NFS driver: Use database format in initialize_connection"
- NFS driver: Use database format in initialize_connection
The `qemu_img_info` operation in initialize_connection may not be
able to determine whether the volume format is `raw` or `qcow2`,
when an inner qcow2 image is writen into a volume. This issue
commonly happens when Glance is configured with Cinder/NFS as
image store.
This patch explicitily tells `qemu_img_info` operation to use
the database format stored in admin_metadata `format` field instead
of trying a autodiscover, to ensure volume metadata such as the
virtual_size will be gathered correctly.
Partial-Bug: #2073146
Change-Id: I28df6ddfa4f62b440e01918958352ab186234f87 Signed-off-by: Fernando Ferraz Silva <fesilva@redhat.com>
Zuul [Fri, 19 Dec 2025 20:39:25 +0000 (20:39 +0000)]
Update git submodules
* Update openstack-helm from branch 'master'
to bc23f506ac88880c4db46dd7e154efa7a58a00b7
- Merge "[ceph-rook] Update Rook to version 1.18.8"
- [ceph-rook] Update Rook to version 1.18.8
Update Rook to version 1.18.8 in the deployment tools.
Change-Id: Ie83ccb22bb6306e8d22faea3eb97622d09bfe4ff Signed-off-by: Stephen Taylor <stephen.taylor.1@att.com>
Zuul [Fri, 19 Dec 2025 20:06:24 +0000 (20:06 +0000)]
Update git submodules
* Update openstack-helm from branch 'master'
to e61f0342c0c0e1903f7f0d96afd961a3f5812070
- Merge "ironic: drop the retrieve-cleaning-network init container"
- ironic: drop the retrieve-cleaning-network init container
It was only setting a deprecated option and the script it ran gave less
feedback to the user than the built in check inside of Ironic. With the
future of Ironic standalone networking this option will make even less
sense so allow the default behavior of looking up the name in Ironic.
Zuul [Fri, 19 Dec 2025 19:38:24 +0000 (19:38 +0000)]
Update git submodules
* Update python-openstackclient from branch 'master'
to d1a0ede7dbf84b66bd4620857683f81808cff8a5
- Merge "zuul: Make openstackclient-check-plugins voting"
- zuul: Make openstackclient-check-plugins voting
This will ensure we do not forget to ignore a module when migrating
plugins in-tree.
Change-Id: Id4dd657746f7c5f8ebf5ef55964593123303b996 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Depends-on: https://review.opendev.org/c/openstack/openstackclient/+/970618
Zuul [Fri, 19 Dec 2025 19:32:20 +0000 (19:32 +0000)]
Update git submodules
* Update manila-tempest-plugin from branch 'master'
to 93319df40995334ec44062e307cc45457088f8e4
- Merge "Drop python 3.9 and support python 3.13"
- Drop python 3.9 and support python 3.13
Due to requirements repo dropped the constraints for
python3.9[1], Tempest needs to drop the python 3.9
support[2]. Because Tempest master cannot support
py3.9 anymore, it needs to be dropped from tempest
plugins also.
Also, add python 3.13 support which is tested as mandatory
in 2026.2 cycle.
The NetApp driver records info [original_name] and
[original_junction_path] when a share is managed.This data
is not removed during share deletion and is stored in
private_storage and never cleaned up
This change ensures that when a NetApp share is managed, the
associated private storage entry is deleted via
private_storage.delete(share['id'])
If the share does not exist, no deletion of private storage is done
so that diagnosis is possible if necessary.
private_storage.delete(share['id]) also removed from
_update_create_from_snapshot_status as it now introduces redundancy for
the deletion there, since the _delete_share function is already being
called before that.
Test Plan:
test_delete_share_clears_private_storage
- Verifies private storage is deleted when the share exists.
This is when _share_exists() is True
test_delete_share_nonexistent_does_not_delete_private_storage
- Verifies that when _share_exixts() returns False,
private_storage.delete is not called, preserving any metadata.
Closes-Bug: #2084666
Change-Id: I0b3613e1ea1f54471b1f9cc73fec0761f3639b26 Signed-off-by: Rose Kimondo <rosewairimu1@gmail.com>
Zuul [Fri, 19 Dec 2025 18:01:29 +0000 (18:01 +0000)]
Update git submodules
* Update kolla-ansible from branch 'master'
to 3439c6b8e812550cf9afba9b7a35878dd1697935
- Merge "tempest: Rework regex to a list"
- tempest: Rework regex to a list
Change-Id: I7505f8feeb85f606df92a20bf4a4700d5ea36a51 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Zuul [Fri, 19 Dec 2025 17:26:35 +0000 (17:26 +0000)]
Update git submodules
* Update cinder from branch 'master'
to ffc441fe5531a27bbc72d9eacb40c3d255f70102
- Merge "NFS driver: Set volume format for snapshot operations"
- NFS driver: Set volume format for snapshot operations
On snapshot operations, the NFS driver does not properly update
the volume format in admin_metadata to correspond to the format
of the active snaphot, as in the case of offline snapshot
creation, in which the driver does update the format to match
the newly created qcow2 snapshot, resulting in the resizing
operation to fail due to the format mismatch in the
`qemu-img resize` command.
This patch fixes such behavior by updating the volume format
in volume_admin_metadata whenever the active snapshot is replaced.
Change-Id: I7cacdd9b78820d272058e9c35f926e23b4c87ba4 Signed-off-by: Fernando Ferraz Silva <fesilva@redhat.com>
Zuul [Fri, 19 Dec 2025 16:51:37 +0000 (16:51 +0000)]
Update git submodules
* Update ironic from branch 'master'
to 534e9ff6b833a006e3995cf8d5f7d80d1587c681
- Merge "Support filtering portgroups by shard"
- Support filtering portgroups by shard
This was somehow missed during initial implementation. Adding ability to
filter portgroup by shard. This was mostly vibe coded with claude, with
me interupting to suggest better implementations when it did something
silly. Tested manually by a human using fake drivers :).
Closes-bug: #2134566 Generated-by: Claude code (claude) Signed-off-by: Jay Faulkner <jay@jvf.cc>
Change-Id: Ic67c02763c2d832f616dc4526e4be891d639b976
Zuul [Fri, 19 Dec 2025 16:06:55 +0000 (16:06 +0000)]
Update git submodules
* Update kolla-ansible from branch 'master'
to d41e90abc783788168884abb273c63333ae65152
- Merge "haproxy: skip redundant backend configuration for memcached"
- haproxy: skip redundant backend configuration for memcached
Previously, Kolla-Ansible generated unnecessary HAProxy backend
configuration entries for the memcached service. These backend entries
were redundant since memcached is not accessed through HAProxy by any
OpenStack service. This patch removes the redundant configuration,
keeping the HAProxy configuration minimal and consistent with actual
service usage.
Closes-Bug: #2130641
Change-Id: I62f40d48a7f2d58b3a3b9ac6d5827a721e02c545 Signed-off-by: Piotr Milewski <vurmil@gmail.com>
Zuul [Fri, 19 Dec 2025 16:06:49 +0000 (16:06 +0000)]
Update git submodules
* Update kolla-ansible from branch 'master'
to b00675bec03c2e4ec5473306a5040a17d33356c0
- Merge "certificates: rework to use Ansible modules"
- certificates: rework to use Ansible modules
Add keyCertSign and digitalSignature key_usage required by Python 3.13 [1]
The member_create, member_delete and handle_member_dvr helper
methods expect lists but _ensure_loadbalancer was passing single
dictionaries, causing sync operations to fail.
This patch fixes regression introduced when [1] was merged
Zuul [Fri, 19 Dec 2025 15:11:34 +0000 (15:11 +0000)]
Update git submodules
* Update cinder from branch 'master'
to 616f134ba98adbd46277334b2d6361a522662f77
- Merge "Doc: Improve docs for Glance Cinder Store"
- Doc: Improve docs for Glance Cinder Store
This patch improves the documentation for Cinder as a backend for
Glance by including:
1. Configuration changes with the New location API
2. Details about how the optimizations are performed vs the generic path
3. Pre-conditions for the optimizations to work
4. Recommendations regarding the internal/service project while uploading volume
Change-Id: I6f3035178b2b43145b34fbeb14bac22d0b52bc27 Signed-off-by: Rajat Dhasmana <rajatdhasmana@gmail.com>
Zuul [Fri, 19 Dec 2025 15:01:17 +0000 (15:01 +0000)]
Update git submodules
* Update kolla-ansible from branch 'master'
to 62a27c792dc878c9367b5db2d911318507877134
- Merge "ironic: Make inspector related volume removal optional"
- ironic: Make inspector related volume removal optional
Since we need to keep the upgrade steps for 2025.1->2026.1
and 2025.2->2026.1 upgrade currently fails on missing
inspector-related container volume - we need to adapt
the logic to check if that volume migration and removal
needs to be done.
Change-Id: If15a43733117ff48f107614589347b992ed1baa4 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
$ git log --oneline --no-merges 3.22.0..67854d12 67854d12 Add "both" direction to tap mirror definition 28a37284 Fix tap_mirror extension name in KNOWN_EXTENSIONS 62a07e9a Adding new base class 'BaseOvnDbSynchronizer' 15d8373e Service role is now considered as the one who can change project_id b5272aab Deprecate "is_advsvc" attribute in the Context object 39527e93 Rehome PortHardwareOffloadTypeEnumField 20ab081c Fix assertion in unit test b7dd86ea Add information to network ip availabilities dde9ccfe Add "can_set_project_id" attribute to the context object b116c74e Replace deprecated warn_on_missing_entrypoint 2feaec5a Fix documentation for maximum tag length 7f4285b9 Remove ACCESS_READONLY RBAC constant. ba498831 reno: Update master for unmaintained/2024.1 7d8fcafa Start running pylint on the test tree 7b3be70b Fix duplicate registration for resource_extend dbf206fe Add the localhost IPv4 and IPv6 addresses constant
Signed-off-by: Rodolfo Alonso Hernandez <ralonsoh@redhat.com>
Change-Id: Ic2d13f300264cbd3dac6fbd426b917ae44852b78
Zuul [Fri, 19 Dec 2025 13:36:14 +0000 (13:36 +0000)]
Update git submodules
* Update releases from branch 'master'
to 51ca1cf9dac1282aeb63fdb94baaa05a4a76086a
- Merge "Move unmaintained/wallaby to EOL"
- Move unmaintained/wallaby to EOL
As announced on mailing list [1], this patch moves unmaintained/wallaby
to End of Life.
Zuul [Fri, 19 Dec 2025 13:33:13 +0000 (13:33 +0000)]
Update git submodules
* Update releases from branch 'master'
to 51a6b59706eb902eef38d81a1b126d43440d7318
- Merge "Move unmaintained/victoria to EOL"
- Move unmaintained/victoria to EOL
As announced on mailing list [1], this patch moves
unmaintained/victoria to End of Life.
The file should be owned by the user(STACK_USER) to run the process.
Note that STACK_USER may not match the current user in case stack.sh is
run by root.
Also we should not assume that the group name always matches the user
name.
Provider networks (VLANs and flat) with localnet ports cause
datapath confusion when Load Balancers are associated to them.
When traffic arrives via Floating IPs, this results in SYN
packet drops and high latency issues.
This patch adds detection of localnet ports in logical switches
and skips LB association when a provider network is detected.
This prevents the datapath issues while still allowing normal
LB operation on tenant networks.
Closes-Bug: #2130211
Change-Id: Ie86d088514bfc491f58069c2f4987672a32b8314 Signed-off-by: Fernando Royo <froyo@redhat.com>
Zuul [Fri, 19 Dec 2025 04:15:12 +0000 (04:15 +0000)]
Update git submodules
* Update swift from branch 'master'
to 8bf6e090f4753f7e9d1df1ef2bea46aad9c6e088
- Merge "test_diskfile.py: fix failing test if O_TMPFILE unsupported"
- test_diskfile.py: fix failing test if O_TMPFILE unsupported
Previously test_commit_overwritten_before_ppi_rename would fail when
O_TMPFILE is not supported (e.g macos) because an extra, unexpected,
rename call is made to rename a temporary file to a data file.
Change-Id: I30f4dcee50e30e3c501b302e2242dc1abe9b6b62 Signed-off-by: Alistair Coles <alistairncoles@gmail.com>
Zuul [Fri, 19 Dec 2025 01:26:53 +0000 (01:26 +0000)]
Update git submodules
* Update tempest from branch 'master'
to 0a40adcd71db3e057d9da0ddadb01660dfc8b86e
- Merge "Use reader role in test_list_servers_negative"
- Use reader role in test_list_servers_negative
Update test_list_servers_negative.py to use the reader role for all
GET requests (list operations) following the pattern in
test_list_server_filters.py. This ensures proper RBAC testing by
using the project_reader credentials for read operations while
maintaining the primary credentials for write operations.
Partial-Implements: blueprint test-nova-with-srbac-defaults
Change-Id: I4be4395a538c59b3faca4abbf5baaf546accbd00 Signed-off-by: Jason Paroly <jparoly@redhat.com>
As discussed during the PTG, VTEP support for OVN is being
removed in order to eliminate confusion and also the Ironic
community is working on a suitable solution to these problems
which integrates with Neutron.
Closes-Bug: 2106460
Change-Id: I4147371c28cf786edb6f29ea83e3b7103f268347 Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com> Signed-off-by: Jay Faulkner <jay@jvf.cc>
In order to support the deployment of OCI images utilizing bifrost,
we also need to explicitly support basic authentication.
This has been extended to support inclusion of the authentication
credentials into the pull secret string, and fallback on the deploy
interface settings for static configuration. While this will likely
never be perfect, it is at least a forward step to better supporting
a variety of use cases.
Additionally, doing some of this highlighted some extraneous guard
rail style checks which exist elsewhere in the overall image handling
flow. A exeception check was added to prevent tag based deployments
from failing because the existing code structure of the guard rail
checks cannot gain the context around basic auth.
In part becasue the check directly uses the image_source as well,
as opposed to any other state data which is presently available
in deploy_utils when the image information is identified.
That situation highlights why additional fixes are needed,
but bug 2133885 was opened for that separately.
Claude also helped me out with the unit tests.
Assisted-By: Claude Code - Claude Sonnet 4.5
Change-Id: I13f4d5cd8b98ad88e7b6088c79c7b014b6461668 Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
Zuul [Thu, 18 Dec 2025 22:39:53 +0000 (22:39 +0000)]
Update git submodules
* Update nova from branch 'master'
to 4b71dab239b4f82d50297ec5bd887c207b43b7ea
- Merge "Remove tpool_execute as it is unused"
- Remove tpool_execute as it is unused
The previous commits removed all the users for nova.utils.tpool_execute
so this patch removes that utility.
This also allows us to inline the _pass_context helper as now it is only
used by spawn_on.
Zuul [Thu, 18 Dec 2025 21:01:37 +0000 (21:01 +0000)]
Update git submodules
* Update ironic from branch 'master'
to d069f2a886f5be30e987ce0f668170eec6383a13
- Merge "fix redfish inspect system product name"
- fix redfish inspect system product name
The intention of this code is to read the system product name which is
stored in the model field per the Redfish spec and not in the name field
which will always store the name of the object we are working with. This
results in the value always being 'System'.
Zuul [Thu, 18 Dec 2025 20:37:46 +0000 (20:37 +0000)]
Update git submodules
* Update horizon from branch 'master'
to 7ff84aac8f2632e7c4691ef5d3b4040e6b0046cc
- Merge "feat(dashboard): add microversion support for Nova live migration"
- feat(dashboard): add microversion support for Nova live migration
- Include "live_migrate" in MICROVERSION_FEATURES with minimum version 2.30.
- Update `server_live_migrate` to use the appropriate microversion when calling
Nova's live_migrate API.
Change-Id: Ief547b55f90ff2bfd9f97ea859b4511c631676ef
Closes-Bug: 1788367 Signed-off-by: Dong Ma <dong.ma@vexxhost.com>
Zuul [Thu, 18 Dec 2025 19:34:56 +0000 (19:34 +0000)]
Update git submodules
* Update watcher-specs from branch 'master'
to ea5d9742bd929399bc3dc11839c835cf0d73b711
- Merge "Add specification for migrating Watcher to OpenStackSDK"
- Add specification for migrating Watcher to OpenStackSDK
This specification proposes a phased migration from individual
Python client libraries to OpenStackSDK for inter-service
communication. The individual client libraries (python-novaclient,
python-cinderclient, etc.) are deprecated and scheduled for
removal from future OpenStack releases.
Phase 1 (2026.1) focuses on:
- Establishing OpenStackSDK infrastructure
- Migrating Nova client to SDK compute proxy
- Creating migration patterns for subsequent phases
Future phases will migrate remaining clients (Cinder, Keystone,
Placement, Ironic) and eventually integrate Watcher itself into
OpenStackSDK as an infra_optim service.
The neutron network interface's add_ports_to_network() function only
checked for 'pxe_boot' capability when determining PXE capability,
but iPXE is also a form of PXE booting and should be treated the
same way. This caused inconsistent behavior for boot interfaces like
'http-ipxe' that have 'ipxe_boot' capability but not 'pxe_boot'
capability.
Without this fix, iPXE boot interfaces were incorrectly treated as
non-PXE capable, causing the neutron interface to create ports for
all baremetal ports with local_link_connection info during cleaning
operations, regardless of their pxe_enabled setting.
This change adds 'pxe_boot' capability to both iPXEBoot and
iPXEHttpBoot classes, ensuring that iPXE boot interfaces are
correctly recognized as PXE-capable.
Additionally, this adds the missing pxe_boot capability check to
the remove_ports_from_network() function, which was previously
missing this logic entirely. This ensures consistent port creation
and deletion behavior, preventing orphaned neutron ports after
cleaning operations.
Change-Id: I7721f917fb723e8a4cef69e0f7be1ece0238d7ed Signed-off-by: Milan Fencik <milan.fencik@rackspace.co.uk>
Zuul [Thu, 18 Dec 2025 17:35:59 +0000 (17:35 +0000)]
Update git submodules
* Update openstack-ansible-ops from branch 'master'
to c1b95130ad7b8d96d3d8dd517aec8dfcc9d99d1f
- Merge "Update mcapi to test against latest versions"
- Update mcapi to test against latest versions
* Removes workarounds for venv support in Noble
* Updates docs
* Updates functional test image versions
* Updates CI testing versions
* Moves minimal config to main OSA repo to match latest AIO expectations
* Add minimal role to install rust/cargo and configure as required
There were libvirt disk attach / detach unit test cases that mocked
threading.Event.wait to speed up the test execution as the libvirt event
based device detach has a 20 seconds timeout.
However this mock is very wide. It effects all the threading.Event usage
during the test case. As we are switched to the native threaded backed
of oslo.service we got an LoopingCall implementation that relies on
threading.Event to signal when the call is finished. In these test cases
the wide mock broke this logic and the LoopingCall signalled "done" while
the actual call in the background was still running making that call
leaking out from the test case and therefore under the fixtures the test
case tore down after the test case finished. This caused that later the
call hit non mocked code paths like importing the real libvirt lib
instead of using our libvirt fixture causing late failures.
The fix is to remove the wide mock and instead change the detach timeout
in these test cases.
Later follow ups will check put protection in place to avoid
re-introducing this wide mock.
Abhishek Kekane [Thu, 18 Dec 2025 16:36:47 +0000 (16:36 +0000)]
Update git submodules
* Update python-openstackclient from branch 'master'
to ed2dc692ddaf0b5b7fd62d2c7e0eb03c2e4b1287
- Fix image owner change when accepting membership with --project
When using 'openstack image set --project <project> --accept <image>',
the command incorrectly changed the image owner. The --project parameter
when used with membership flags should only identify which member's
status to update, not change ownership.
Zuul [Thu, 18 Dec 2025 16:31:46 +0000 (16:31 +0000)]
Update git submodules
* Update ironic from branch 'master'
to 50aa083013a102540a2b583972549ce224b05962
- Merge "OCI: Add an option to fallback to HTTP"
- OCI: Add an option to fallback to HTTP
While working on trying to get OCI support in CI, I realized that the
default pattern setup with Bifrost was to setup a registry *without*
HTTPS.
This is different from the common practice and expectation of operational
OCI registries always utilizing HTTPS as the underlying transport mechanism.
The net result is an idea of offering the ability to "fall back" to HTTP
automatically, and make it a configuration option which needs to be
chosen by an operator.
The code pattern is such that the invocation of the client code paths
automatically identify the SSLError, and then attempt to fallback
to HTTP, while also saving the fallback on the class instance so the
additional URL generation calls for the underlying HTTP(S) client
gets an appropriate URL.
By default, this new option is disabled.
Claude helped with the tests, which was nice of it.
Assisted-By: Claude Code - Claude Sonnet 4.5
Change-Id: I3f28c8d6debe25b63ca836d488bc9fd8541b04d9 Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
Zuul [Thu, 18 Dec 2025 16:14:39 +0000 (16:14 +0000)]
Update git submodules
* Update kolla-ansible from branch 'master'
to 2d7728ff321f9c9a6223f906d42288fd3668f9be
- Merge "Make generation of prometheus.yml idempotent when using custom override files"
- Make generation of prometheus.yml idempotent when using custom override files
As the result from the find is not always sorted the same way, consecutive deployments would have a configuration file change, while it actually is not.
Also, diffs are really hard to interpret, when some config parts have been moved up or down.
Change-Id: I6f724de6ec46e0691639f0a64de5af9e248a27ff
Resolves-bug: #2126635 Signed-off-by: Michel Nederlof <michel.nederlof@nl.team.blue>
Zuul [Thu, 18 Dec 2025 15:33:04 +0000 (15:33 +0000)]
Update git submodules
* Update openstack-ansible from branch 'master'
to 072a66673dbed0d0dd017f179b10b3b71ee9b62a
- Merge "ci: add nova console log collection and fix build file collection"
- ci: add nova console log collection and fix build file collection
Bash wildcard expansion resulted in too many arguments to the
store_artifacts function. This is remedied by passing in
directories instead, with a wildcard filter for file types.
The same approach is used to store nova VM console output
without picking up disk images from the same directory.
Change-Id: Ia28e3639299247ff28b4b150a4006c7a9f558959 Signed-off-by: Andrew Bonney <andrew.bonney@bbc.co.uk>
This patch refactors the ovn-db-sync CLI tool provided by Neutron in the
way that actual sync tasks are now made as "plugins" which can be loaded
through the entry_points. With that change stadium or 3rd party projects
can add their own ovn-db-sync tasks and Neutron will load them together
with tasks implemented in Neutron directly.
Zuul [Thu, 18 Dec 2025 14:06:05 +0000 (14:06 +0000)]
Update git submodules
* Update releases from branch 'master'
to 5afb186dab10dc5022ea0b9211a8c42231972319
- Merge "[barbican-tempest-plugin] Tag 2024.1-last"
- [barbican-tempest-plugin] Tag 2024.1-last
2024.1 branch is moving to unmaintained state now[1]. Tempest and
tempest plugins are branchless which means master version of
Tempest and its plugins are not guaranteed to support unmaintained
branched. To continue testing the unmaintained branches, Tempest
and its plugins compatible tag[2][3] needs to be released for
their testing.
Tagging '2024.1-last' with the same hash as existing 4.4.0 version.
Zuul [Thu, 18 Dec 2025 14:06:00 +0000 (14:06 +0000)]
Update git submodules
* Update releases from branch 'master'
to 1b1caeadd585add3c00db9991a4d40a9e762b9c0
- Merge "[glance-tempest-plugin] Tag 2024.1-last"
- [glance-tempest-plugin] Tag 2024.1-last
2024.1 branch is moving to unmaintained state now[1]. Tempest and
tempest plugins are branchless which means master version of
Tempest and its plugins are not guaranteed to support unmaintained
branched. To continue testing the unmaintained branches, Tempest
and its plugins compatible tag[2][3] needs to be released for
their testing.
Tagging '2024.1-last' with the same hash as existing 0.14.0 version.
Zuul [Thu, 18 Dec 2025 14:05:55 +0000 (14:05 +0000)]
Update git submodules
* Update releases from branch 'master'
to 9eeab45213da2628826c2df66998625d2581dee5
- Merge "[octavia-tempest-plugin] Tag 2024.1-last"
- [octavia-tempest-plugin] Tag 2024.1-last
2024.1 branch is moving to unmaintained state now[1]. Tempest and
tempest plugins are branchless which means master version of
Tempest and its plugins are not guaranteed to support unmaintained
branched. To continue testing the unmaintained branches, Tempest
and its plugins compatible tag[2][3] needs to be released for
their testing.
Tagging '2024.1-last' with the same hash as existing
flamingo 3.2.0 version (as there is no functional change
after that).
Zuul [Thu, 18 Dec 2025 13:58:35 +0000 (13:58 +0000)]
Update git submodules
* Update releases from branch 'master'
to f6498e18a607088a6e55804326ff33aacbc9b07b
- Merge "[telemetry-tempest-plugin] Tag 2024.1-last"
- [telemetry-tempest-plugin] Tag 2024.1-last
2024.1 branch is moving to unmaintained state now[1]. Tempest and
tempest plugins are branchless which means master version of
Tempest and its plugins are not guaranteed to support unmaintained
branched. To continue testing the unmaintained branches, Tempest
and its plugins compatible tag[2][3] needs to be released for
their testing.
Tagging '2024.1-last' with the latest hash, also releasing
a new tag 2.8.0.
With QoS policy, admin can control a certain quality (minimum and
maximum level) to be sure to know what to expect. Similar to
max_throughput, share-type extra-spec needs to update to consider
min_throughput. It can be specified using any single key from list
of ['netapp:miniops', 'netapp:miniopspergib', 'netapp:minbps',
'netapp:minbpspergib'].
Zuul [Thu, 18 Dec 2025 10:40:31 +0000 (10:40 +0000)]
Update git submodules
* Update devstack from branch 'master'
to feb248232842f5f299a34f433a7603cffecf3e08
- Merge "Drop logic for CentOS (Stream) 8"
- Drop logic for CentOS (Stream) 8
Zuul [Thu, 18 Dec 2025 07:37:56 +0000 (07:37 +0000)]
Update git submodules
* Update ironic from branch 'master'
to 4bef17b9bcad796b24e35e309b242365d6a7f582
- Merge "fix loading of built-in inspection rules"
- fix loading of built-in inspection rules
The built-in inspection rules cannot be loaded because the jsonschema
validates them against the expected API however the built-in rules had a
'built-in' key that is not part of the schema and included the 'scope'
key which was ultimately dropped before inspection rules support landed.
The built-in rules also did not validate that the data was a list of
rules before attempting to utilize it giving an incorrect error.
Fixing error in install hook:
ERROR: Could not find a version that satisfies the requirement hatch-vcs<0.6.0,>=0.4.0 (from versions: none)
ERROR: No matching distribution found for hatch-vcs<0.6.0,>=0.4.0
projects / 0xmirror / openstack.git / log