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
Zuul [Wed, 17 Dec 2025 21:39:24 +0000 (21:39 +0000)]
Update git submodules
* Update devstack from branch 'master'
to bd160a3d2a33ba383c06f895ef819b3621290d05
- Merge "Silence SyntaxWarnings in outfilter.py"
- Silence SyntaxWarnings in outfilter.py
Zuul [Wed, 17 Dec 2025 21:39:17 +0000 (21:39 +0000)]
Update git submodules
* Update devstack from branch 'master'
to c50ebf08654bb1d42cc5250b5706ce3ba7978d59
- Merge "Enable response validation in Nova"
- Enable response validation in Nova
Per inline description
Change-Id: I85c959461e4e96b69d252e06fc697a1c61488411 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Zuul [Wed, 17 Dec 2025 21:39:11 +0000 (21:39 +0000)]
Update git submodules
* Update devstack from branch 'master'
to 4a18166d9b2b81b225ed7996517f9c8dcfb58dd0
- Merge "[Neutron] Add TARGET_ENABLE_OVN_AGENT variable to enable OVN agent"
- [Neutron] Add TARGET_ENABLE_OVN_AGENT variable to enable OVN agent
The new flag ``TARGET_ENABLE_OVN_AGENT`` will be disabled by default.
If enabled:
* The OVN agent will be enabled, regardless of not being configured.
* The OVN Metadata agent will be disabled, regardless of being
configured.
This variable will be used, initially, in the grenade jobs. It will
be used to test the migration from the OVN Metadata agent to the
OVN agent.
This variable will be removed in 2026.2, along with the OVN Metadata
agent, that is set as deprecated and marked for removal.
Related-Bug: #2112313 Signed-off-by: Rodolfo Alonso Hernandez <ralonsoh@redhat.com>
Change-Id: I8f91e1cb8543da489f495b8cf5196e606a0f5eea
Zuul [Wed, 17 Dec 2025 21:00:22 +0000 (21:00 +0000)]
Update git submodules
* Update bifrost from branch 'master'
to 88797af9b1f021b6a9eb4f6f36765e1646c96ffc
- Merge "Switch IPA ramdisk to debian DIB based"
- Switch IPA ramdisk to debian DIB based
The debian based IPA ramdisk is smaller and has a more recent
default python version (3.13) compared to CentOS Stream 9.
Zuul [Wed, 17 Dec 2025 19:48:02 +0000 (19:48 +0000)]
Update git submodules
* Update ironic from branch 'master'
to 1fecbce5155d43f5264efa0e9b5fc647208b8497
- Merge "fix: inspection rules docs to match the code"
- fix: inspection rules docs to match the code
These inspection rules actions are implemented but were not documented
so add some documentation for them. The redfish inspection interface
also supports inspection rules.
Zuul [Wed, 17 Dec 2025 19:47:56 +0000 (19:47 +0000)]
Update git submodules
* Update ironic from branch 'master'
to 78323a90167b1f351f16884c9906eae1f6c5e429
- Merge "update inspection rules docs and code to the same order"
- update inspection rules docs and code to the same order
Updated the docs and code to match the same order and to break out each
operation like it is in the code. Fixed incorrect indent of an example.
This is just mechanical to make visual inspection of the docs to the
code easier.
Zuul [Wed, 17 Dec 2025 19:11:06 +0000 (19:11 +0000)]
Update git submodules
* Update ironic-python-agent-builder from branch 'master'
to a090c0445fa46322baddaf049bbb6feeec5d45c3
- Merge "ci: Start running the advaned ironic job"
- ci: Start running the advaned ironic job
Recent issues which forced an ipa-b revert should have been
caught in an ideal case, but the test to actually discover
that is in Ironic. So to start, get the job running, and
later on switch it over to voting.
Change-Id: I0e976967e8b973806a9fbdb36e1e6c30c810f215 Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
Zuul [Wed, 17 Dec 2025 19:09:49 +0000 (19:09 +0000)]
Update git submodules
* Update openstack-helm from branch 'master'
to 4c467cb5e9d0031544b1736d5ee03f63e78cae22
- Merge "feat: build charts into sub dirs"
- feat: build charts into sub dirs
As outlined in
https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/thread/VTMDDVSPM5HRUYWAATNMZOILT5OE57VR/
the current structure of building all the charts into one directory is
causing issues on the opendev infra due too many entries in one
directory. Switch away from using a Makefile to using an Ansible role to
build each chart and then use chart-testing to identify the charts that
need to be rebuilt and lastly build them build put the output into a
subdir matching the chart name.
Change-Id: I61f11950ba381c7897eb6bfff05a508ca4db9f06 Signed-off-by: Doug Goldstein <cardoe@cardoe.com> Signed-off-by: Vladimir Kozhukalov <kozhukalov@gmail.com>
While looking at some logs, I discovered that systemd was now erroring about
the ConditionPathExists parameter. It appears that belongs in unit instead.
As such, moving.
Error: systemd[1]: /usr/lib/systemd/system/ironic-python-agent.service:6: Unknown key name 'ConditionPathExists' in section 'Service', ignoring.
Change-Id: Ifc2b2cbde939d9d9b9fec4e9a5f548e5420650a2 Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
Zuul [Wed, 17 Dec 2025 18:22:32 +0000 (18:22 +0000)]
Update git submodules
* Update devstack from branch 'master'
to f755f3ffe3b024df7bdc0784b61521f83b831102
- Merge "almalinux: Switch to build OVS from source"
- almalinux: Switch to build OVS from source
Since almalinux-10 label in OpenDev runs on both x86-64-v2 and v3,
and CentOS NFV SIG OVS packages are only build for v3, these jobs
have been only successful when spawned on v3 hardware.
In order to make the job passable on v2 hardware - we should be
building OVS from source.
Rename the jobs to reflect the change
Change-Id: I67b19c18b45af23cda7899f7c2edab21b8ed1ede Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
Zuul [Wed, 17 Dec 2025 18:16:37 +0000 (18:16 +0000)]
Update git submodules
* Update devstack from branch 'master'
to 5d8e557a8e007c4395cbf6e92d978b8f1f15d500
- Merge "lib/neutron: Prepare for move of api-paste, rootwrap conf"
- lib/neutron: Prepare for move of api-paste, rootwrap conf
Change-Id: I70ba357f9af668fb7a7cb737d13fe24e572eb0ff Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Zuul [Wed, 17 Dec 2025 17:56:53 +0000 (17:56 +0000)]
Update git submodules
* Update bifrost from branch 'master'
to 297d2872953e43d88eaba8084125db8aa6e60c65
- Merge "Centos: set masked: false for firewalld"
- Centos: set masked: false for firewalld
It appears that Centos has changed the default firewall masking state
and as such the playbook now fails. Adding masked: false to unmask the
unit so hopefuly bifrost works as expected.
Also, temporarily disables the bookworm job so we can un-wedge CI
which is broken in multiple ways including centos breakages.
Change-Id: Ib30795a88d4908fd1b78250b99a840bccb185ba3 Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
When size_gb='MAX' is specified, Ironic was calculating the maximum
volume size and including it in ``CapacityBytes``. This calculated size
doesn't account for controller metadata overhead, causing iLO and other
controllers to reject the request with UnsupportedOperation.
Fix by omitting ``CapacityBytes`` from the Redfish payload when
size_gb='MAX', allowing the controller to calculate the optimal size
automatically and the actual volume size is queried and stored after
creation via ``update_raid_config()``.
Use current openstack python versions to run unit tests, but keep
testing Python 3.9 using stable/2025.1
Pin stable/2025.1 for CS9 and Rocky 9 jobs
Add CS10 jobs to test current master
Remove ancient jammy and bullseye jobs
Add bookworm and noble jobs
Currently, when a call to the Nova API fails for any connection
temporary issue, Watcher actions fail.
This patch is adding retries to nova api calls when connection issues
are detected. The retries can be configured with new parameters in the
nova section:
- http_retries (default is 3 retries)
- http_retry_interval (default is 2 seconds).
Note that, in order to implement the retries in all the nova_helper
methods, in some cases i am adding new elementary calls which are called
by more complex ones.
This patch is implementing some improvements in the tests for the
nova_helper:
- Replaces mocks by novaclient real objects for faking servers and
hypervisors.
- Removes all usage of getattr and setattr.
- Removes usage of some helpers which were only used once.
- Removes some mocks for time.sleep in tests given that we have one in
the setup function of the class.
- Improves fake_nova_find_list so that it can return lists with more
that one element if needed.
- Add some asserts to validate calls to migrate, live_migrate and resize
methods.
Note that the test cases and scenarios remains the same.
Zuul [Wed, 17 Dec 2025 13:38:56 +0000 (13:38 +0000)]
Update git submodules
* Update barbican from branch 'master'
to 5c28289ebe11164bdb51d29cfde7cd221eb8133f
- Merge "[CI] Do not use devstack-single-node-fedora-latest nodeset"
- [CI] Do not use devstack-single-node-fedora-latest nodeset
devstack-single-node-fedora-latest nodeset does not exist anymore in
CI, so let's use the default nodeset for barbican-dogtag-tox-functional
test job to get rid of the zuul config error [1].
[1] The nodeset "devstack-single-node-fedora-latest" was not found.
Apparently we're getting an error in some cases, but also
the base job configuration changed at some point which mooted
the purpose of some of the code. So now, only trigger the excess
code and log an error if there was a failure so it is possible to
understand the actual failure.
Change-Id: I33236532d826e3795497a51bab78d2ceba55285e Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>
We have project_reader credentials in tempest and they
use the same project as member role creds. Nova support
the project reader role in get server API. Moving the
create server tests to use project reader creds in GET
API calls.
Zuul [Tue, 16 Dec 2025 23:13:31 +0000 (23:13 +0000)]
Update git submodules
* Update swift from branch 'master'
to 9059935f9f532031259f50410892f139331f24ad
- Merge "sharder: use correct Timestamp formats"
- sharder: use correct Timestamp formats
Use Timestamp.internal for X-Timestamp header when making a PUT
request to send shard range updates to the root container. The unit
test already asserts that the internal format is sent, but the test
failed to use a Timestamp where the internal and normal formats
differed..
Don't try to cast timestamp strings to floats when sorting
CleavingContext metadata. Timestamp strings may have the form
<float>_<offset> so it is safer to cast a Timestamp string to a
Timestamp and then to cast the Timestamp to a float when necessary.
Change-Id: I59e140d1226a4b0c2c8f37678bc2dc87d9ffa631 Signed-off-by: Alistair Coles <alistairncoles@gmail.com> Co-Authored-By: Alistair Coles <alistairncoles@gmail.com> Signed-off-by: Matthew Oliver <matt@oliver.net.au>
Zuul [Tue, 16 Dec 2025 21:22:48 +0000 (21:22 +0000)]
Update git submodules
* Update openstack-helm from branch 'master'
to 3faddf006a688ad4bece0134438642b3fbbe2a57
- Merge "chore: set chart-testing project wide to 3.11.0"
- chore: set chart-testing project wide to 3.11.0
This makes it so that 3.11.0 is the version used consistently and sets
it at the top-level.
Zuul [Tue, 16 Dec 2025 20:54:37 +0000 (20:54 +0000)]
Update git submodules
* Update openstack-helm from branch 'master'
to 800b6788da000fe8f4d7bdf9536820cae71d57e6
- Merge "chore: set helm project wide to 3.18.1"
- chore: set helm project wide to 3.18.1
This makes it so that 3.18.1 is the version used consistently and sets
it at the top-level.
Adds a tool that will ingest a TBN configuration file along with test
network/port-like objects in order to simulate how TBN would plan the
network for a node.
Zuul [Tue, 16 Dec 2025 19:29:44 +0000 (19:29 +0000)]
Update git submodules
* Update nova from branch 'master'
to 11dff40b4fba04e1423fb1ffe3866f59f5325a6e
- Merge "Make image upload tpool usage conditional"
- Make image upload tpool usage conditional
When running in eventlet mode we keep the original eventlet.tpool usage
but when running in threading mode we call the functions directly on the
thread of the caller.
The original tpool_execute() call made the upload call running in a
native tread as it has parts that are blocking and therefore running
them in the current greenthread would make the other greenthreads
starved.
After this patch we preserve the same effect but with different syntax.
We use tpool_wrap to wrap the function into a tpool.Proxy object and
then call the proxy object. That proxy ensures that any call on the
proxy object is run in a native thread.
This change is useful for us in native threaded mode. There the
tpool_wrap returns the function unchanged. So upload is executed in the
caller's native thread. This is OK as in native threaded mode any
concurrent tasks are also in native threads and native threads are
preempted when needed. So other tasks will not be starved.
Zuul [Tue, 16 Dec 2025 18:13:49 +0000 (18:13 +0000)]
Update git submodules
* Update python-openstackclient from branch 'master'
to 08b1bb70dd2154acadaa53e22a70d0d0e4d98a0f
- Merge "taas: Use custom command classes"
- taas: Use custom command classes
In change I53d9058273748ecd4d4eecec5f7291d5f38ce5ab we added custom
Command classes for typing purposes. However, the Tap-as-a-Service code
merged around the same time and was missed. Correct this.
Change-Id: I3a9fe20b5b8eb54708644527538f27396f29b476 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Zuul [Tue, 16 Dec 2025 18:13:44 +0000 (18:13 +0000)]
Update git submodules
* Update neutron from branch 'master'
to 9f3a5cde17da4f978846772ab787766ef2d65d95
- Merge "Search for active port binding when updating LSP host info"
- Search for active port binding when updating LSP host info
When updating LSP host info for an UP port, the code
always uses the first port binding in the DB entry
(db_port.port_bindings[0].host).
Since there could be multiple port bindings present,
search for the active one when determining which host
value to use.
Closes-bug: #2134504
Change-Id: Ia07610a17afb55b802290c8910a17dace7794c4f Signed-off-by: Brian Haley <haleyb.dev@gmail.com>
projects / 0xmirror / openstack.git / log