- Release-announce - lists.openstack.org

ironic 23.0.5 (bobcat)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We are amped to announce the release of: ironic 23.0.5 This release is part of the bobcat 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. 23.0.5 ^^^^^^ Bug Fixes * Includes the agent token parameter in get command status requests as the endpoint now requires authentication. Changes in ironic 23.0.4..23.0.5 -------------------------------- 76009f281 ci: automatically set the branch for IPA to match TARGET_BRANCH 889ce1ac1 Pass agent token to get command results Diffstat (except docs and test files) ------------------------------------- devstack/lib/ironic | 2 +- ironic/drivers/modules/agent_client.py | 6 ++++++ .../notes/include-agent-token-to-get-requests-982bacce85d95ce8.yaml | 5 +++++ 4 files changed, 15 insertions(+), 4 deletions(-)

1 0

oslo.middleware 6.4.0 (flamingo)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We are gleeful to announce the release of: oslo.middleware 6.4.0 This release is part of the flamingo release series. The source is available from: https://opendev.org/openstack/oslo.middleware Download the package from: https://pypi.org/project/oslo.middleware Please report issues through: https://bugs.launchpad.net/oslo.middleware/+bugs For more details, please see below. 6.4.0 ^^^^^ Upgrade Notes * The following deprecated options were removed. Use "[oslo_middleware] max_request_body_size" instead. * "[DEFAULT] osapi_max_request_body_size" * "[DEFAULT] max_request_body_size" Changes in oslo.middleware 6.3.1..6.4.0 --------------------------------------- c2b1187 Add typing ce9a3fd Use ruff 61995db trivial: Consistent option naming a125f25 trivial: Use deferred logging cf6da5e Update master for stable/2025.1 8adcd4a sizelimit: Remove deprecated option names Diffstat (except docs and test files) ------------------------------------- .pre-commit-config.yaml | 26 +- oslo_middleware/__init__.py | 20 +- oslo_middleware/_i18n.py | 1 - oslo_middleware/base.py | 94 +- oslo_middleware/basic_auth.py | 108 ++- oslo_middleware/catch_errors.py | 13 +- oslo_middleware/correlation_id.py | 19 +- oslo_middleware/cors.py | 335 ++++--- oslo_middleware/debug.py | 16 +- oslo_middleware/exceptions.py | 6 +- oslo_middleware/healthcheck/__init__.py | 212 +++-- oslo_middleware/healthcheck/__main__.py | 45 +- oslo_middleware/healthcheck/disable_by_file.py | 93 +- oslo_middleware/healthcheck/enable_by_files.py | 38 +- oslo_middleware/healthcheck/opts.py | 92 +- oslo_middleware/healthcheck/pluginbase.py | 24 +- oslo_middleware/http_proxy_to_wsgi.py | 42 +- oslo_middleware/opts.py | 35 +- oslo_middleware/request_id.py | 21 +- oslo_middleware/sizelimit.py | 63 +- oslo_middleware/stats.py | 36 +- oslo_middleware/version.py | 1 - pyproject.toml | 49 + ...deprecated-sizelimit-opts-289290ff2fba9899.yaml | 8 + releasenotes/source/2025.1.rst | 6 + releasenotes/source/conf.py | 31 +- releasenotes/source/index.rst | 1 + setup.py | 3 +- tox.ini | 21 +- 41 files changed, 1923 insertions(+), 1184 deletions(-)

1 0

cloudkitty 19.1.0 (bobcat)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We joyfully announce the release of: cloudkitty 19.1.0 This release is part of the bobcat release series. The source is available from: https://opendev.org/openstack/cloudkitty Download the package from: https://pypi.org/project/cloudkitty Please report issues through: https://storyboard.openstack.org/#!/project/openstack/cloudkitty For more details, please see below. 19.1.0 ^^^^^^ New Features ************ * OpenSearch has been added as an alternative v2 storage backend. It is a duplicate of the ElasticSearch backend, with the naming changed where appropriate. This change is in support of the deprecation of ElasticSearch as a backend. Upgrade Notes ************* * The "storage_state.get_state" method has been removed in favor of the "storage_state.get_last_processed_timestamp" method. Bug Fixes ********* * Fix some API report requests that were returning HTTP 500 errors when using the "opensearch" storage backend. This fixes failures to load the Horizon "Rating" panel. * Fix retrieval of reprocessing tasks which was returning "Internal Server Error". Changes in cloudkitty 19.0.0..19.1.0 ------------------------------------ fe19718 Fix devstack runprocess for cloudkitty api 24211e7 Fix API report requests when using opensearch b3d8bf7 Remove get_state function and its references 7b1cd3a Add OpenSearch as a v2 storage backend 623e352 Fix retrieval of reprocessing tasks d9a3aa9 Remove the manual patch for WSME c1a6106 Update TOX_CONSTRAINTS_FILE for stable/2023.2 9bdba8b Update .gitreview for stable/2023.2 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + .zuul.yaml | 13 + cloudkitty/api/v2/task/reprocess.py | 8 +- cloudkitty/common/config.py | 3 + cloudkitty/orchestrator.py | 4 +- cloudkitty/storage/v2/opensearch/__init__.py | 205 +++++++++ cloudkitty/storage/v2/opensearch/client.py | 413 ++++++++++++++++++ cloudkitty/storage/v2/opensearch/exceptions.py | 32 ++ cloudkitty/storage_state/__init__.py | 8 - cloudkitty/write_orchestrator.py | 8 +- devstack/plugin.sh | 83 +++- devstack/settings | 4 + ...rch-as-v2-storage-backend-ff4080d6d32d8a2a.yaml | 7 + .../deprecate-get-state-2932a4e6a74295ce.yaml | 5 + .../fix-opensearch-report-344508dd4e3d0ccc.yaml | 6 + .../notes/reprocess-get-fix-f2bd1f2f9e2d640e.yaml | 5 + setup.cfg | 1 + tox.ini | 10 +- 25 files changed, 1406 insertions(+), 53 deletions(-)

1 0

octavia 13.0.1 (bobcat)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We are psyched to announce the release of: octavia 13.0.1 This release is part of the bobcat release series. The source is available from: https://opendev.org/openstack/octavia Download the package from: https://pypi.org/project/octavia Please report issues through: https://storyboard.openstack.org/#!/project/908 For more details, please see below. 13.0.1 ^^^^^^ Bug Fixes ********* * Fixed error on update UDP Health Monitor with empty "delay" parameter * Fixed an issue when a failover reverts, a neutron port may get abandoned. The issue was logged with "Failed to delete port", "Resources may still be in use for a port intended for amphora", and "Search for a port named octavia-lb-vrrp-<uuid>". * Fix the issue, when "limit" parameter in request less or equal 0. Now it returns resources according pagination_max_limit as expected, instead of error. * Fixed an issue when using certificates with a blank subject or missing CN. * Fixed wrong endpoint information in neutron client configuration. * Remove record in amphora_health table on revert. It's necessary, because record in amphora table for corresponding amphora also deleted. It allows to avoid false positive react of failover threshold due to orphan records in amphora_health table. * Fixed a bug that prevented the amphora from being updated by the Amphora Configure API call, the API call was succesfull but the internal flow for updating it failed. * Fixed potential AttributeError during listener update when security group rule had no protocol defined (ie. it was null). * Fixed a potential issue when deleting a load balancer with an amphora that was not fully created, the deletion may have failed when deallocating the VIP port, leaving the load balancer in ERROR state. * Added a validation step in the batch member API request that checks if a member is included multiple times in the list of updated members, this additional check prevents the load balancer from being stuck in PENDING_UPDATE. Duplicate members in the batch member flow triggered an exception in Taskflow. The API now returns 400 (ValidationException) if a member is already present in the body of the request. * Fixed an issue when filtering resources with a boolean attribute in the GET calls in the Octavia API. * Fixed a bug when creating a load balancer and a listener with "allowed_cidrs" with the fully-populated load balancer API, the call was rejected because Octavia could not validate that the IP addresses of the "allowed_cidrs" have the same family as the VIP address. * Fixed an issue with SINGLE topology load balancer with UDP listeners, the Amphora now sends a Gratuitous ARP packet when a UDP pool is added, it makes the VIP address more quickly reachable after a failover or when reusing a previously allocated IP address. * Bug fix: The response body of the LB API, when creating a new load balancer, now correctly includes information about the health monitor. Previously, this information was consistently null, despite configuring a health monitor. * Fixed a bug with HTTP/HTTPS health-monitors on pools with ALPN protocols in the amphora-driver. The healthchecks sent by haproxy were flagged as bad requests by the backend servers. Updated haproxy configuration to use ALPN for the heathchecks too. * Fixed an issue with load balancers stuck in a "PENDING_*" state during database outages. Now when a task fails in Octavia, it retries to update the "provisioning_status" of the load balancer until the database is back (or it gives up after a really long timeout - around 2h45) * Fix load balancer stuck in PENDING_DELETE if TLS storage unavailable or returns error * Fixed an issue when using UDP listeners in dual-stack (IPv4 and IPv6) load balancers, some masquerade rules needed by UDP were not correctly set on the member interfaces. * Fixed a bug when the deprecated settings ("endpoint", "endpoint_type", "ca_certificates_file") are used in the "[neutron]" section of the configuration file. The connection to the neutron service may have used some settings from the "[service_auth]" section or used undefined settings. * Fixed a race condition in the members batch update API call, the data passed to the Octavia worker service may have been incorrect when quickly sending successive API calls. Then the load balancer was stuck in PENDING_UPDATE provisioning_status. * Fixed a too long timeout when attempting to start the VRRP service in an unreachable amphora during a failover. A specific shorter timeout should be used during the failovers. * Fixed TLS-HELLO health-monitors in the amphora-driver. * Fix verification of certificates signed by a private CA when using Neutron endpoints. * Fix error on revert PlugVIPAmphora task, when db_lb is not defined and get_subnet raises NotFound error. It could happen when Amphora creation failed by timeout and before it VIP network was removed. As result revert failed with exception. * Reduce the duration of the failovers of ACTIVE_STANDBY load balancers. Many updates of an unreachable amphora may have been attempted during a failover, now if an amphora is not reachable at the first update, the other updates are skipped. * Reduce the duration of the failovers of ACTIVE_STANDBY load balancers when both amphorae are unreachable. * Fixed a bug with the *nopreempt* option in keepalived. The option didn't work properly because the default role of the *MASTER* amphora was set. Removing the default roles from the configuration files fixed that issue. Now after a failover, the newly created amphora doesn't preempt the *MASTER* role from the other amphora. Other Notes *********** * Noop certificate manager was added. Now any Octavia certificate operations using noop drivers will be faster (as they won't be validated). Changes in octavia 13.0.0..13.0.1 --------------------------------- 3142d13ab Cleanup duplicate DB sessions for quotas 37e6e6395 Fix amphora image builds to use DIB bindep c972ff9b8 Fix port abandonment on failover flow revert 5a23a8eca Fixed VRRP nopreempt option 2bae2e287 Fix test_prometheus_proxy.test_main 3497e769a Fix incorrect filtering when using bool attrs ce0066f03 Handle undefined protocol field in security group rules correctly 35817025b Update stable/2023.2 to use 2023.2 tests f1ea5ed2c Fix verification of certificates signed by a private CA 6987845c8 Fix missing GARP with UDP listeners on SINGLE LB ceb55b567 Remove amphora_health record on revert CreateAmphoraInDB 649f8967b Do not fail on revert PlugVIPAmphora due undefined db_lb b4adc98f6 Use cryptography to load PKCS12 certificates 09ea1e991 Fix loadbalancer stuck in cascade delete 70ecbcc8b Add check for duplicate members in batch update 80bbf2e56 Removing tips jobs on stable/2023.2 dbe59b8b4 When we failed to load pkcs12 cert print warning f548fa53a Fix DB deadlock in quotas 2f170b79a Fix health monitor information retrieval in API response 1f38d29b2 Fix incorrect masquerade rules in multivip LBs a9a3c64ee Fix neutron setting overrides a1d422fe7 Fix fully-populated API with allowed_cidrs b509b0795 Handle empty delay on update healthmonitor 06142805e Fix negative or 0 limit parameter in pagination 56cd4d3a9 Pin pylint (<=3.0.4) 33627fbb4 Fix error when deleting LB with broken amp c664c865b fix: specify endpoint info. for neutron client acf4a3064 fix pep8 use-yield-from rule d0725c084 Fix issue with certificates with no subject or CN 421c7fdce Stable-only: Cap hacking to < 6.1.0 0f9bc3b8c Fix TLS-HELLO healthmonitors in the amphora-driver 7c468ca4c Fix health-monitors with ALPN members 281379c6d Remove publish-openstack-octavia-amphora-image jobs be828d7cf Remove slqalchemy-tips job 88d7315a6 Add Noop Certificate Manager 7c67c1023 Fix Amphora Configure API call ef4b4d500 Retry to set loadbalancer prov status on failures 562243153 Fix amphorae in ERROR during the failover 6fdc2079d Reduce duration of failovers with amphora in ERROR 54eb1624f Fix timeout duration in start_vrrp_service during failovers a04e0f520 [stable/2023.2] Remove octavia-grenade-skip-level job 8a5bed4ce Fix race condition in members batch update API call 4f827c4a7 Fix remaining usage of [neutron] endpoint_type f5d56c0fd Update TOX_CONSTRAINTS_FILE for stable/2023.2 853d0f69e Update .gitreview for stable/2023.2 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + .../amphora-agent/source-repository-amphora-agent | 4 +- elements/octavia-lib/source-repository-octavia-lib | 2 +- .../backends/agent/api_server/keepalivedlvs.py | 9 + .../amphorae/backends/agent/api_server/osutils.py | 3 +- octavia/amphorae/backends/agent/api_server/util.py | 37 ++- octavia/amphorae/backends/utils/interface.py | 9 +- octavia/amphorae/drivers/driver_base.py | 16 ++ .../amphorae/drivers/haproxy/rest_api_driver.py | 21 +- .../amphorae/drivers/keepalived/jinja/jinja_cfg.py | 1 - .../jinja/templates/keepalived_base.template | 1 - .../drivers/keepalived/vrrp_rest_driver.py | 3 +- octavia/amphorae/drivers/noop_driver/driver.py | 3 + octavia/api/common/pagination.py | 2 +- octavia/api/v2/controllers/health_monitor.py | 5 +- octavia/api/v2/controllers/l7policy.py | 1 - octavia/api/v2/controllers/l7rule.py | 1 - octavia/api/v2/controllers/listener.py | 1 - octavia/api/v2/controllers/load_balancer.py | 20 +- octavia/api/v2/controllers/member.py | 23 +- octavia/api/v2/controllers/pool.py | 13 +- octavia/api/v2/types/pool.py | 2 +- octavia/certificates/common/pkcs12.py | 18 +- octavia/certificates/manager/barbican.py | 40 ++-- octavia/certificates/manager/castellan_mgr.py | 19 +- octavia/certificates/manager/noop.py | 106 +++++++++ octavia/common/clients.py | 26 ++- octavia/common/config.py | 26 ++- octavia/common/constants.py | 4 + octavia/common/exceptions.py | 6 + .../haproxy/combined_listeners/templates/macros.j2 | 12 +- octavia/common/keystone.py | 14 +- octavia/common/tls_utils/cert_parser.py | 32 ++- octavia/controller/worker/task_utils.py | 34 ++- octavia/controller/worker/v2/controller_worker.py | 4 +- .../controller/worker/v2/flows/amphora_flows.py | 51 ++++- octavia/controller/worker/v2/flows/flow_utils.py | 10 +- .../worker/v2/flows/load_balancer_flows.py | 20 +- .../worker/v2/tasks/amphora_driver_tasks.py | 137 +++++++++-- .../controller/worker/v2/tasks/database_tasks.py | 83 +++---- .../controller/worker/v2/tasks/lifecycle_tasks.py | 136 +++++++---- .../controller/worker/v2/tasks/network_tasks.py | 25 +- octavia/db/base_models.py | 20 +- octavia/db/repositories.py | 67 +++--- .../drivers/neutron/allowed_address_pairs.py | 18 +- octavia/network/drivers/noop_driver/driver.py | 3 +- .../backends/agent/api_server/test_util.py | 90 +++++++- .../unit/amphorae/backends/utils/test_interface.py | 4 +- .../drivers/haproxy/test_rest_api_driver.py | 6 +- .../drivers/keepalived/jinja/test_jinja_cfg.py | 4 - .../drivers/keepalived/test_vrrp_rest_driver.py | 17 ++ .../unit/certificates/manager/test_barbican.py | 6 +- .../haproxy/combined_listeners/test_jinja_cfg.py | 33 ++- .../unit/controller/worker/test_task_utils.py | 60 ++++- .../worker/v2/flows/test_amphora_flows.py | 33 ++- .../worker/v2/flows/test_load_balancer_flows.py | 15 +- .../worker/v2/tasks/test_amphora_driver_tasks.py | 251 +++++++++++++++++++-- .../worker/v2/tasks/test_database_tasks.py | 34 ++- .../worker/v2/tasks/test_database_tasks_quota.py | 38 ++-- .../worker/v2/tasks/test_network_tasks.py | 59 ++++- .../controller/worker/v2/test_controller_worker.py | 57 ++++- .../drivers/neutron/test_allowed_address_pairs.py | 25 +- playbooks/image-build/run.yaml | 51 +---- ...itor-update-without-delay-c56240e59e15483f.yaml | 4 + ...failover-revert-port-leak-d9879523506c6ff3.yaml | 7 + ...nation-less-or-equal-zero-93a33f1318ea34e5.yaml | 6 + ...andle-blank-cert-subjects-b660d403ce56b0b8.yaml | 4 + ...ron-client-interface-info-06faaaad92886b8c.yaml | 4 + .../add-noop-cert-manager-7018d3933a0ce9c6.yaml | 4 + ...lth_row_on_amphora_revert-082f94459ecacaa2.yaml | 7 + ...x-amphora-update-api-call-d90853d7f75304a4.yaml | 6 + ...up-rule-has-protocol-none-9b7217c5477d01b6.yaml | 5 + ...on-delete-with-broken-amp-10d7f4e85754d7ee.yaml | 6 + ...e-members-in-batch-update-610ffbbf949927d0.yaml | 10 + ...g-with-boolean-attributes-15df51820753a900.yaml | 5 + ...ulated-with-allowed-cidrs-ad04ccf02bf9cbbc.yaml | 7 + ...ix-garp-for-udp-listeners-6bf2ec8d491d1e1b.yaml | 7 + ...retrieval-in-api-response-d3b2e02a3a966f60.yaml | 7 + ...thmonitor-with-alpn-pools-82249b2b9a025068.yaml | 7 + ...-in-PENDING-on-DB-failure-1ffea71a86cd4ea9.yaml | 7 + ...dbalancer-stuck-on-delete-da5950cf87fc8507.yaml | 5 + ...de-rules-in-dualstack-lbs-94f97606c5804b36.yaml | 6 + .../fix-neutron-overrides-710ed047ebf0c45c.yaml | 8 + ...ition-member-batch-update-1aed0e06004c5dad.yaml | 7 + ...eout-dict-when-start-vrrp-278d4837702bd247.yaml | 6 + ...-tls-hello-healthmonitors-a4b98a80f6de8394.yaml | 4 + ...te-ca-signed-certificates-b9386a0d92627b03.yaml | 5 + ..._db_lb_on_plug_vip_revert-5c24af124498b246.yaml | 7 + .../reduce-duration-failover-636032433984d911.yaml | 7 + ...-standby-amphora-in-error-3c1d75bc7d9b169f.yaml | 5 + ...ault-role-from-keepalived-c879bad3a42a6b4a.yaml | 8 + requirements.txt | 1 - setup.cfg | 1 + test-requirements.txt | 4 +- tox.ini | 8 +- zuul.d/jobs.yaml | 152 +++++++------ zuul.d/projects.yaml | 45 ++-- 111 files changed, 2266 insertions(+), 639 deletions(-) Requirements updates -------------------- diff --git a/requirements.txt b/requirements.txt index e20ed6e15..0905f0305 100644 --- a/requirements.txt +++ b/requirements.txt @@ -41 +40,0 @@ python-cinderclient>=3.3.0 # Apache-2.0 -pyOpenSSL>=19.1.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 051ebbdf3..c1936926e 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -4 +4 @@ -hacking>=3.0 # Apache-2.0 +hacking<6.1.0 # Apache-2.0 @@ -11 +11 @@ oslotest>=3.2.0 # Apache-2.0 -pylint>=2.5.3 # GPLv2 +pylint>=2.5.3,<=3.0.4 # GPLv2

1 0

placement 11.0.1 (caracal)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We are glad to announce the release of: placement 11.0.1 This release is part of the caracal release series. The source is available from: https://opendev.org/openstack/placement Download the package from: https://pypi.org/project/placement Please report issues through: https://storyboard.openstack.org/#!/project/openstack/placement For more details, please see below. 11.0.1 ^^^^^^ Bug Fixes * In a deployment with wide and symmetric provider trees, i.e. where there are multiple children providers under the same root having inventory from the same resource class (e.g. in case of nova's mdev GPU or PCI in Placement features) if the allocation candidate request asks for resources from those children RPs in multiple request groups the number of possible allocation candidates grows rapidly. E.g.: * 1 root, 8 child RPs with 1 unit of resource each a_c requests 6 groups with 1 unit of resource each => 8*7*6*5*4*3=20160 possible candidates * 1 root, 8 child RPs with 6 unit of resources each a_c requests 6 groups with 6 unit of resources each => 8^6=262144 possible candidates Placement generates these candidates fully before applying the limit parameter provided in the allocation candidate query to be able do a random sampling if "[placement]randomize_allocation_candidates" is True. Placement takes excessive time and memory to generate this amount of allocation candidates and the client might time out waiting for the response or the Placement API service run out of memory and crash. To avoid request timeout or out of memory events a new "[placement]max_allocation_candidates" config option is implemented. This limit is applied not after the request limit but *during* the candidate generation process. So this new option can be used to limit the runtime and memory consumption of the Placement API service. The new config option is defaulted to "-1", meaning no limit, to keep the legacy behavior. We suggest to tune this config in the affected deployments based on the memory available for the Placement service and the timeout setting of the clients. A good initial value could be around "100000". If the number of generated allocation candidates is limited by the "[placement]max_allocation_candidates" config option then it is possible to get candidates from a limited set of root providers (e.g. compute nodes) as placement uses a depth-first strategy, i.e. generating all candidates from the first root before considering the next one. To avoid this issue a new config option "[placement]allocation_candidates_generation_strategy" is introduced with two possible values: * "depth-first", generates all candidates from the first viable root provider before moving to the next. This is the default and this triggers the old behavior * "breadth-first", generates candidates from viable roots in a round-robin fashion, creating one candidate from each viable root before creating the second candidate from the first root. This is the possible behavior. In a deployment where "[placement]max_allocation_candidates" is configured to a positive number we recommend to set "[placement]allocation_candidates_generation_strategy" to "breadth- first". (https://bugs.launchpad.net/nova/+bug/2070257) Changes in placement 11.0.0..11.0.1 ----------------------------------- b798523e Add round-robin candidate generation strategy dc4ffdc4 Factor out allocation candidate generation strategy 47ee16bd Add a global limit on the number of allocation candidates af00c864 Update TOX_CONSTRAINTS_FILE for stable/2024.1 f2452734 Update .gitreview for stable/2024.1 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + placement/conf/placement.py | 67 +++++++- placement/objects/allocation_candidate.py | 142 +++++++++------ placement/objects/research_context.py | 4 + .../unit/objects/test_allocation_candidate.py | 57 +++++++ placement/util.py | 13 ++ ...n-limit-and-strategy.yaml-e73796898163fb55.yaml | 63 +++++++ tox.ini | 2 +- 10 files changed, 506 insertions(+), 61 deletions(-)

1 0

octavia 14.0.1 (caracal)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We are glad to announce the release of: octavia 14.0.1 This release is part of the caracal release series. The source is available from: https://opendev.org/openstack/octavia Download the package from: https://pypi.org/project/octavia Please report issues through: https://storyboard.openstack.org/#!/project/908 For more details, please see below. 14.0.1 ^^^^^^ Bug Fixes * Fixed an issue updating listeners when using SR-IOV VIP ports. * Fixed a bug in the VIP SR-IOV implementation that would cause load balancer memebers that use the SR-IOV VIP interface to not receive traffic. * Fixed error on update UDP Health Monitor with empty "delay" parameter * Fixed an issue when failing over load balancers using SR-IOV VIP ports. * Fixed an issue when a failover reverts, a neutron port may get abandoned. The issue was logged with "Failed to delete port", "Resources may still be in use for a port intended for amphora", and "Search for a port named octavia-lb-vrrp-<uuid>". * Fix the issue, when "limit" parameter in request less or equal 0. Now it returns resources according pagination_max_limit as expected, instead of error. * Remove record in amphora_health table on revert. It's necessary, because record in amphora table for corresponding amphora also deleted. It allows to avoid false positive react of failover threshold due to orphan records in amphora_health table. * Fixed potential AttributeError during listener update when security group rule had no protocol defined (ie. it was null). * Added a validation step in the batch member API request that checks if a member is included multiple times in the list of updated members, this additional check prevents the load balancer from being stuck in PENDING_UPDATE. Duplicate members in the batch member flow triggered an exception in Taskflow. The API now returns 400 (ValidationException) if a member is already present in the body of the request. * Fixed an issue when filtering resources with a boolean attribute in the GET calls in the Octavia API. * Fixed a bug when creating a load balancer and a listener with "allowed_cidrs" with the fully-populated load balancer API, the call was rejected because Octavia could not validate that the IP addresses of the "allowed_cidrs" have the same family as the VIP address. * Fixed an issue with SINGLE topology load balancer with UDP listeners, the Amphora now sends a Gratuitous ARP packet when a UDP pool is added, it makes the VIP address more quickly reachable after a failover or when reusing a previously allocated IP address. * Fix load balancer stuck in PENDING_DELETE if TLS storage unavailable or returns error * Fix verification of certificates signed by a private CA when using Neutron endpoints. * Fix error on revert PlugVIPAmphora task, when db_lb is not defined and get_subnet raises NotFound error. It could happen when Amphora creation failed by timeout and before it VIP network was removed. As result revert failed with exception. * Fixed a bug with the *nopreempt* option in keepalived. The option didn't work properly because the default role of the *MASTER* amphora was set. Removing the default roles from the configuration files fixed that issue. Now after a failover, the newly created amphora doesn't preempt the *MASTER* role from the other amphora. Changes in octavia 14.0.0..14.0.1 --------------------------------- 2c2f0d328 Fix incorrect filtering when using bool attrs 6e1b00a8e Fix test_prometheus_proxy.test_main 9c33604ae Fixed VRRP nopreempt option 1338f29d2 Fix port abandonment on failover flow revert e5e462c6e Update stable/2024.1 to use 2024.1 tests 6edc3f274 Fix verification of certificates signed by a private CA 11515cdd4 Fix missing GARP with UDP listeners on SINGLE LB a97dcca94 curl-minimal conflicts with already installed curl 1e1301ff8 Don't install firewalld in the amphora 2e4a03e5c Remove amphora_health record on revert CreateAmphoraInDB efe3ee865 Handle undefined protocol field in security group rules correctly 5a039fcd9 Do not fail on revert PlugVIPAmphora due undefined db_lb 87f5d0a4c Fix amphora image builds to use DIB bindep e5a9a9538 Fix SR-IOV when VIP interface is used for members 2733a6766 Fix failover when using SRIOV VIP 3af5401b8 Fix loadbalancer stuck in cascade delete b61c340b0 Add check for duplicate members in batch update c704267c5 Fix listener update when using SRIOV VIP b370e46c1 Pin pylint on 2024.1 32df43144 Removing tips jobs on stable/2024.1 8d1998299 Fix fully-populated API with allowed_cidrs 1945df32d Fix negative or 0 limit parameter in pagination 8b4e9e731 Handle empty delay on update healthmonitor 6b11062d3 Update TOX_CONSTRAINTS_FILE for stable/2024.1 894023ec9 Update .gitreview for stable/2024.1 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + elements/amphora-agent/package-installs.yaml | 4 + elements/amphora-agent/pkg-map | 1 - .../amphora-agent/source-repository-amphora-agent | 4 +- .../static/usr/local/bin/lvs-masquerade.sh | 62 +++++++++------ elements/octavia-lib/source-repository-octavia-lib | 2 +- .../backends/agent/api_server/keepalivedlvs.py | 9 +++ .../amphorae/backends/agent/api_server/osutils.py | 6 +- octavia/amphorae/backends/agent/api_server/plug.py | 9 ++- .../amphorae/backends/agent/api_server/server.py | 5 +- octavia/amphorae/backends/agent/api_server/util.py | 37 ++++++++- octavia/amphorae/backends/utils/interface.py | 39 +--------- octavia/amphorae/backends/utils/interface_file.py | 33 +++++--- octavia/amphorae/backends/utils/nftable_utils.py | 44 ++++++++--- .../amphorae/drivers/keepalived/jinja/jinja_cfg.py | 1 - .../jinja/templates/keepalived_base.template | 1 - octavia/api/common/pagination.py | 2 +- octavia/api/v2/controllers/health_monitor.py | 4 +- octavia/api/v2/controllers/load_balancer.py | 7 ++ octavia/api/v2/controllers/member.py | 14 +++- octavia/common/clients.py | 8 +- octavia/common/constants.py | 6 +- octavia/controller/worker/v2/controller_worker.py | 4 +- .../controller/worker/v2/flows/amphora_flows.py | 17 +++- octavia/controller/worker/v2/flows/flow_utils.py | 10 ++- .../controller/worker/v2/flows/listener_flows.py | 22 ++++-- .../controller/worker/v2/tasks/database_tasks.py | 16 ++-- .../controller/worker/v2/tasks/network_tasks.py | 25 +++--- octavia/db/base_models.py | 20 ++++- .../drivers/neutron/allowed_address_pairs.py | 5 +- .../backend/agent/api_server/test_server.py | 2 +- .../backends/agent/api_server/test_osutils.py | 2 +- .../backends/agent/api_server/test_plug.py | 7 +- .../backends/agent/api_server/test_util.py | 90 ++++++++++++++++++++- .../unit/amphorae/backends/utils/test_interface.py | 67 +--------------- .../amphorae/backends/utils/test_nftable_utils.py | 50 ++++++------ .../drivers/keepalived/jinja/test_jinja_cfg.py | 4 - .../worker/v2/flows/test_listener_flows.py | 25 +++--- .../worker/v2/flows/test_load_balancer_flows.py | 10 +-- .../worker/v2/tasks/test_database_tasks.py | 34 ++++++-- .../worker/v2/tasks/test_network_tasks.py | 59 +++++++++++++- .../controller/worker/v2/test_controller_worker.py | 57 +++++++++++++- .../drivers/neutron/test_allowed_address_pairs.py | 3 +- playbooks/image-build/run.yaml | 52 ++----------- ...ner-Update-for-SRIOV-VIPs-8348b7fe0c02b9c4.yaml | 4 + ...rface-is-used-for-members-adb150ece454ecff.yaml | 5 ++ ...itor-update-without-delay-c56240e59e15483f.yaml | 4 + ...x-failover-for-SRIOV-VIPs-e2ab193c0de5eb1d.yaml | 4 + ...failover-revert-port-leak-d9879523506c6ff3.yaml | 7 ++ ...nation-less-or-equal-zero-93a33f1318ea34e5.yaml | 6 ++ ...lth_row_on_amphora_revert-082f94459ecacaa2.yaml | 7 ++ ...up-rule-has-protocol-none-9b7217c5477d01b6.yaml | 5 ++ ...e-members-in-batch-update-610ffbbf949927d0.yaml | 10 +++ ...g-with-boolean-attributes-15df51820753a900.yaml | 5 ++ ...ulated-with-allowed-cidrs-ad04ccf02bf9cbbc.yaml | 7 ++ ...ix-garp-for-udp-listeners-6bf2ec8d491d1e1b.yaml | 7 ++ ...dbalancer-stuck-on-delete-da5950cf87fc8507.yaml | 5 ++ ...te-ca-signed-certificates-b9386a0d92627b03.yaml | 5 ++ ..._db_lb_on_plug_vip_revert-5c24af124498b246.yaml | 7 ++ ...ault-role-from-keepalived-c879bad3a42a6b4a.yaml | 8 ++ test-requirements.txt | 2 +- tox.ini | 8 +- zuul.d/jobs.yaml | 91 ++++++++++++++++++++-- zuul.d/projects.yaml | 38 +++++---- 68 files changed, 902 insertions(+), 351 deletions(-) Requirements updates -------------------- diff --git a/test-requirements.txt b/test-requirements.txt index fa31c123f..6f9f2cb36 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -11 +11 @@ oslotest>=3.2.0 # Apache-2.0 -pylint>=2.5.3 # GPLv2 +pylint>=2.5.3,<3.2.0 # GPLv2

1 0

python-cloudkittyclient 4.8.1 (bobcat)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We eagerly announce the release of: python-cloudkittyclient 4.8.1 This release is part of the bobcat release series. The source is available from: https://opendev.org/openstack/python-cloudkittyclient Download the package from: https://pypi.org/project/python-cloudkittyclient Please report issues through: https://storyboard.openstack.org/#!/project/openstack/python- cloudkittyclient For more details, please see below. 4.8.1 ^^^^^ Bug Fixes * Fixed a bug where creating a reprocessing task would fail due to sending a POST request to the wrong endpoint. Changes in python-cloudkittyclient 4.8.0..4.8.1 ----------------------------------------------- c151d6b Fix reprocessing POST request 61d7fce Update TOX_CONSTRAINTS_FILE for stable/2023.2 f34ec5a Update .gitreview for stable/2023.2 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + cloudkittyclient/v2/reprocessing.py | 4 +--- .../notes/fix-reprocessing-post-request-95512686754ee271.yaml | 5 +++++ tox.ini | 4 ++-- 4 files changed, 9 insertions(+), 5 deletions(-)

1 0

placement 12.0.1 (dalmatian)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We exuberantly announce the release of: placement 12.0.1 This release is part of the dalmatian release series. The source is available from: https://opendev.org/openstack/placement Download the package from: https://pypi.org/project/placement Please report issues through: https://storyboard.openstack.org/#!/project/openstack/placement For more details, please see below. 12.0.1 ^^^^^^ Bug Fixes * In a deployment with wide and symmetric provider trees, i.e. where there are multiple children providers under the same root having inventory from the same resource class (e.g. in case of nova's mdev GPU or PCI in Placement features) if the allocation candidate request asks for resources from those children RPs in multiple request groups the number of possible allocation candidates grows rapidly. E.g.: * 1 root, 8 child RPs with 1 unit of resource each a_c requests 6 groups with 1 unit of resource each => 8*7*6*5*4*3=20160 possible candidates * 1 root, 8 child RPs with 6 unit of resources each a_c requests 6 groups with 6 unit of resources each => 8^6=262144 possible candidates Placement generates these candidates fully before applying the limit parameter provided in the allocation candidate query to be able do a random sampling if "[placement]randomize_allocation_candidates" is True. Placement takes excessive time and memory to generate this amount of allocation candidates and the client might time out waiting for the response or the Placement API service run out of memory and crash. To avoid request timeout or out of memory events a new "[placement]max_allocation_candidates" config option is implemented. This limit is applied not after the request limit but *during* the candidate generation process. So this new option can be used to limit the runtime and memory consumption of the Placement API service. The new config option is defaulted to "-1", meaning no limit, to keep the legacy behavior. We suggest to tune this config in the affected deployments based on the memory available for the Placement service and the timeout setting of the clients. A good initial value could be around "100000". If the number of generated allocation candidates is limited by the "[placement]max_allocation_candidates" config option then it is possible to get candidates from a limited set of root providers (e.g. compute nodes) as placement uses a depth-first strategy, i.e. generating all candidates from the first root before considering the next one. To avoid this issue a new config option "[placement]allocation_candidates_generation_strategy" is introduced with two possible values: * "depth-first", generates all candidates from the first viable root provider before moving to the next. This is the default and this triggers the old behavior * "breadth-first", generates candidates from viable roots in a round-robin fashion, creating one candidate from each viable root before creating the second candidate from the first root. This is the possible behavior. In a deployment where "[placement]max_allocation_candidates" is configured to a positive number we recommend to set "[placement]allocation_candidates_generation_strategy" to "breadth- first". (https://bugs.launchpad.net/nova/+bug/2070257) Changes in placement 12.0.0..12.0.1 ----------------------------------- 828b2559 Add round-robin candidate generation strategy 1b0a9272 Factor out allocation candidate generation strategy f276fc23 Add a global limit on the number of allocation candidates 901dc827 Update TOX_CONSTRAINTS_FILE for stable/2024.2 0ede4513 Update .gitreview for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + placement/conf/placement.py | 67 +++++++- placement/objects/allocation_candidate.py | 142 +++++++++------ placement/objects/research_context.py | 4 + .../unit/objects/test_allocation_candidate.py | 57 +++++++ placement/util.py | 13 ++ ...n-limit-and-strategy.yaml-e73796898163fb55.yaml | 63 +++++++ tox.ini | 2 +- 10 files changed, 506 insertions(+), 61 deletions(-)

1 0

puppet-designate 26.0.0 (epoxy)
by no-reply＠openstack.org 16 Apr '25

16 Apr '25

We are amped to announce the release of: puppet-designate 26.0.0 This release is part of the epoxy release series. The source is available from: https://opendev.org/openstack/puppet-designate Download the package from: https://tarballs.openstack.org/puppet-designate/ Please report issues through: https://bugs.launchpad.net/puppet-designate/+bugs For more details, please see below. Changes in puppet-designate 25.0.0..26.0.0 ------------------------------------------ 262a358 Fix version number for epoxy release 0fa0fd4 Bump Ubuntu version 010e2e9 Prepare 2025.1 release a0c795c Add a rabbit_transient_queues_ttl and amqp_auto_delete params 093c129 Fix new lint errors 56e9ea9 Fix assertion of heartbeat_in_pthread parameter 661288b Deprecate support for [oslo_messaging_rabbit] heartbeat_in_pthread 5b3bfe0 Stop using absolute names for defined resource types 2f464e9 Mark puppet 8 supported b80aa36 bind9: Make rndc options optional aff99fc reno: Update master for unmaintained/2023.1 7d5d39f mdns: Add support for [service:mdns] tcp_keepidle 2aea380 Expose configure_service 879a0a0 Update master for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- example/all-in-one-noauth.pp | 2 +- manifests/backend/bind9.pp | 10 +++--- manifests/db/mysql.pp | 2 +- manifests/db/postgresql.pp | 2 +- manifests/init.pp | 41 ++++++++++++++++------ manifests/keystone/auth.pp | 6 ++++ manifests/keystone/authtoken.pp | 2 +- manifests/mdns.pp | 6 ++++ manifests/producer.pp | 2 +- manifests/wsgi/apache.pp | 2 +- metadata.json | 12 +++---- .../notes/amqp_auto_delete-b5c8adf45591c917.yaml | 5 +++ .../notes/configure_service-42a7bc042a86a946.yaml | 5 +++ ...bbit_heartbeat_in_pthread-efd1ff77b7816503.yaml | 5 +++ .../notes/mdns-tcp_keepidle-d358daa4768b3ed3.yaml | 4 +++ releasenotes/notes/puppet-8-c37cfff2cbe4294a.yaml | 4 +++ ...bbit_transient_queues_ttl-60aa2aed9724e5ba.yaml | 6 ++++ .../notes/rndc-optional-303e6561b611d0d1.yaml | 8 +++++ .../notes/ubuntu-noble-6bfcfc2c716003b8.yaml | 8 +++++ releasenotes/source/2023.1.rst | 2 +- releasenotes/source/2024.2.rst | 6 ++++ releasenotes/source/index.rst | 1 + spec/classes/designate_init_spec.rb | 6 +++- spec/classes/designate_keystone_auth_spec.rb | 3 ++ spec/classes/designate_mdns_spec.rb | 3 ++ templates/bind9-pools.yaml.erb | 6 ++++ 26 files changed, 129 insertions(+), 30 deletions(-)

1 0

puppet-horizon 26.0.0 (epoxy)
by no-reply＠openstack.org 16 Apr '25

16 Apr '25

We are jazzed to announce the release of: puppet-horizon 26.0.0 This release is part of the epoxy release series. The source is available from: https://opendev.org/openstack/puppet-horizon Download the package from: https://tarballs.openstack.org/puppet-horizon/ Please report issues through: https://bugs.launchpad.net/puppet-horizon/+bugs For more details, please see below. 26.0.0 ^^^^^^ New Features ************ * Ubuntu 24.04 is now formally supported. Upgrade Notes ************* * Ubuntu 22.04 is no longer supported. Changes in puppet-horizon 25.0.0..26.0.0 ---------------------------------------- d231d1c Bump Ubuntu version 8102e13 Prepare 2025.1 release 258b1c8 Use common implementation in litmus tests 43e815d Validate redirect_type using data type f6a8b2a Replace remaining use of legacy fact 013f80f Mark puppet 8 supported addf49f reno: Update master for unmaintained/2023.1 4ffebe8 Remove support for MemcachedCache backend ce86df8 Require absolutepath for cache cert/key file dfce4a9 Accept an array for cache_tls_allowed_ciphers cd5216f Pass custom_wsgi_process_options to horizon::wsgi::apache 507e4b2 Update master for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- manifests/init.pp | 281 ++++++++++----------- manifests/params.pp | 2 - manifests/wsgi/apache.pp | 58 ++--- metadata.json | 8 +- ...stom_wsgi_process_options-e11e7d92a9d631b1.yaml | 5 + releasenotes/notes/puppet-8-2654c8e29011ca99.yaml | 4 + .../remove-memcached-backend-e429c4f280d4b02b.yaml | 6 + .../notes/ubuntu-noble-7072fa6f20dc8b5e.yaml | 8 + releasenotes/source/2023.1.rst | 2 +- releasenotes/source/2024.2.rst | 6 + releasenotes/source/index.rst | 1 + spec/acceptance/horizon_with_apache_spec.rb | 29 +-- spec/classes/horizon_init_spec.rb | 76 ++---- templates/local_settings.py.erb | 4 + 14 files changed, 230 insertions(+), 260 deletions(-)

1 0