September 2025 - openstack-discuss

[designate] DNS records stuck in PENDING state but records created succesfully
by Jadon Naas 24 Sep '25

24 Sep '25

Hello! I am using Designate on 2023.2 with a PowerDNS backend. I have a recordset with three A records created through Designate. The A records are stuck in "PENDING" state with action "CREATE" or "UPDATE". The records were successfully created in PowerDNS, and changes are pushed to PowerDNS. However, the record status never finishes updating. Deleting and recreating the recordset results in the same situation. I do not see any notable errors in the logs for Designate or for PowerDNS. I have checked that the Desigate configuration for the nameservers and for the targets match the correct IP addresses for my PowerDNS server and for my Designate service hosts. Would folks have any suggestions for what I could do to determine what is preventing Designate from updating these records or to manually update the status of the records? Thank you! Jadon Naas

2 1

[publiccloud-sig] Public Cloud SIG meeting d.d. 23 September
by Kees Meijs | Nefos 24 Sep '25

24 Sep '25

Hello Stackers, Tomorrow (that's 23 September) the bi-weekly Public Cloud SIG meeting will be held again. The publicly available video meeting will be conducted from 07:00 hrs UTC (09:00 hrs CEST) and on here: https://meetpad.opendev.org/publiccloud-sig Additional information to be found on https://wiki.openstack.org/wiki/PublicCloudSIG See you tomorrow! Cheers, Kees __ Kees Meijs BICT Nefos Cloud & IT <https://nefos.com/contact> Nefos IT bv Burgemeester Mollaan 34a 5582 CK Waalre - NL kvk 66494931 +31 (0)88 2088 188 <tel:+31882088188> nefos.com <https://nefos.com/contact> The information contained in this message is intended for the addressee only and may contain classified information. If you are not the addressee, please delete this message and notify the sender; you should not copy or distribute this message or disclose its contents to anyone. Any views or opinions expressed in this message are those of the individual(s) and not necessarily of the organization. No reliance may be placed on this message without written confirmation from an authorised representative of its contents. No guarantee is implied that this message or any attachment is virus free or has not been intercepted and amended. General terms and conditions ("The NLdigital Terms") apply to all our products and services.

1 1

Compatebilty
by nahoms＠altacomputec.com 23 Sep '25

23 Sep '25

The customer currently uses 15 Dell PowerEdge R650 servers for their OpenStack private cloud and wants to expand. Is there any compatibility issue if we propose Lenovo servers along with the existing Dell ones?

2 1

[octavia] Creation of several master amps
by yardalgedal＠gmail.com 23 Sep '25

23 Sep '25

Hi all, we're using octavia of version zed and caught a case when it regularly creating 3 amphorae instead of 2. We have not had any amphorae for which of these LBs and I did failover for each of them: openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer failover 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer failover 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 openstack loadbalancer failover f9f859d0-2b31-449b-8723-700bb7f3f3f4 then first backup amphorae was created pretty fast openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 3dfa43cd-2719-487e-8ba2-8a4aa0fe7301 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | BACKUP | 10.94.64.112 | 10.210.73.197 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | b39472aa-04a0-42b8-8c09-4617ea1a0f33 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | BACKUP | 10.94.64.232 | 10.210.64.32 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | 60af8e11-c6ad-45f0-8e07-1bcc4a477444 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | BACKUP | 10.94.64.74 | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ but then it started to create 2x Master's for each (!) of them (we can talk about lags, but not in case of 3x): openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 3dfa43cd-2719-487e-8ba2-8a4aa0fe7301 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | BACKUP | 10.94.64.112 | 10.210.73.197 | | 3dd9bdb4-0dfe-4d77-b08f-02fbbffcd892 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | BOOTING | None | None | None | | ff6ec3de-6942-4978-9ea5-d793ff1fdbf8 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | BOOTING | None | None | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | b39472aa-04a0-42b8-8c09-4617ea1a0f33 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | BACKUP | 10.94.64.232 | 10.210.64.32 | | 9909b300-d266-4344-b6fc-edc4af651485 | 96223d34-6941-4bc5-881a-ddfd83070739 | BOOTING | None | None | None | | cc123c55-2953-425e-867e-f4057483bb09 | 96223d34-6941-4bc5-881a-ddfd83070739 | BOOTING | None | None | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | 60af8e11-c6ad-45f0-8e07-1bcc4a477444 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | BACKUP | 10.94.64.74 | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ as a result we started to have 3x Master's for them openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 3dfa43cd-2719-487e-8ba2-8a4aa0fe7301 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | BACKUP | 10.94.64.112 | 10.210.73.197 | | 3dd9bdb4-0dfe-4d77-b08f-02fbbffcd892 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | MASTER | 10.94.64.56 | 10.210.73.197 | | 14e8acfe-8510-4629-a583-53ba88f91eca | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | MASTER | 10.94.64.30 | 10.210.73.197 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | b39472aa-04a0-42b8-8c09-4617ea1a0f33 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | BACKUP | 10.94.64.232 | 10.210.64.32 | | 9909b300-d266-4344-b6fc-edc4af651485 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | MASTER | 10.94.64.151 | 10.210.64.32 | | 9d197234-6411-4069-8be3-a399cc1fbc3a | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | MASTER | 10.94.64.212 | 10.210.64.32 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 60af8e11-c6ad-45f0-8e07-1bcc4a477444 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | BACKUP | 10.94.64.74 | 10.211.193.63 | | d086f283-b9d8-4b23-a782-e0ace769e893 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | MASTER | 10.94.64.225 | 10.211.193.63 | | 8a90fc7c-eb0a-4635-8ece-7c4704c60f7a | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | MASTER | 10.94.64.50 | 10.211.193.63 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ taskflow is enabled in our case, backend is redis can you suggest smth to check or maybe some updates were already done?

3 3

[all][tc] Retrospective for OpenStack Elections
by Goutham Pacha Ravi 23 Sep '25

23 Sep '25

Hello Stackers, The OpenStack Technical Committee would like to take a moment to reflect on the recently concluded elections [1][2]. Elections and renewal of governance are a cornerstone of our Open Community principle [3]. We firmly believe that well-governed projects are sustainable and successful. In the recent elections, we saw 78 electors cast their votes to elect members to the TC out of 173 eligible voters. Jeremy Stanley (fungi) is planning to follow up with some more detailed analysis, but I wanted to kick-start this thread to share a few insights and initiate a call-to-action. To be eligible to contest or vote in OpenStack elections, you must meet two criteria: - You must be an Active Contributor, which means you have had a change merged in the roughly one-year period prior to the elections. - You must be an "Individual Member" of the OpenInfra Foundation (not a "Community Member") at the time the electoral rolls are created. This date is published and typically occurs a few days before polling begins. For the recently concluded 2026.1 elections, we identified over 650 active contributors in the one-year timeframe. However, as you can see, the number of eligible voters and the number of actual voters were significantly smaller. We've identified a few key reasons for this: - Individual Membership Renewal: In the past few months, as the OIF has transitioned under the Linux Foundation, we asked all individual members to "renew" their memberships. OIF staff and OpenStack election officials noticed a drop in the electorate due to this new requirement. It's quite easy for an email seeking renewal to get lost in a crowded inbox. - Opt-in for Ballots: We host our elections with CIVS, a free and secure internet voting service. A ballot arrives via email when polling begins, but CIVS will not send you an email unless you have opted in. While we have tried to remind folks to enable these emails, they can still get "lost" in the noise. - Membership Type Confusion: Many of us may not realize that we need to be an "Individual" member of the OIF to participate in the governance process. I feel we need to do a better job of reminding people why this is needed, so they can make an informed choice about whether they'd like to impact the governance of OpenStack. Nearly 500 contributors are currently either "Community" members or have no affiliation with the OIF. We'd like to hear your thoughts and ideas on how we can improve in these areas (are there any more?). What can we do to ensure a wider and more engaged electorate in future elections? We believe that increasing participation is essential for the long-term health and success of the OpenStack community. Thank you, Goutham Pacha Ravi (gouthamr) OpenStack Technical Committee [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] https://opendev.org/openinfra/four-opens/src/branch/master/doc/source/openc….

2 1

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-1)
by Goutham Pacha Ravi 23 Sep '25

23 Sep '25

Hello Stackers, We're wrapping up work on the 2025.2 "Flamingo" release [1] within all projects that follow the "cycle-with-rc" release model [2]. The coordinated release is scheduled for October 1, 2025. You can follow the cycle highlights that Project Team Leads and liaisons have put together to get a preview of what this release brings [3]. In the past week, election officials posted results from the Combined TC/PTL elections for the 2026.1 release cycle [4][5]. I'm happy to welcome Tony Breeds (tonyb) and welcome back Doug Goldstein (cardoe), Dr. Jens Harbott (frickler), and Sylvain Bauza (bauzas) to the OpenStack Technical Committee. On behalf of the TC, I'd also like to congratulate the newly appointed PTLs of 34 project teams. This includes Arnaud Morin (amorin), who is leading the Mistral project as a first-time PTL, and Li Liu (liliueecg), who is returning to Cyborg as PTL after the Stein release. Thank you all for dedicating your time to fill these important roles. In the past week, the TC didn't merge any new governance changes; however, a few are currently undergoing community review. === Weekly Meeting === The TC held its weekly meeting on OFTC's #openstack-tc IRC channel on September 16, 2025 [6]. We discussed the community's participation in the election process [7] and are seeking input on how the process can be improved. It's possible that any changes we come up with would need buy-in from the OpenInfra Foundation's Board and staff. We followed up on the effort to standardize database character sets and collations across OpenStack projects [8]. The TC agreed that consistency would be beneficial for operators and supported the plan to make this a community goal. We'll follow up regarding the details. We touched on the status of "leaderless" projects, specifically Venus, OpenStack Charms, and Vitrage. If we find no PTL volunteers, the TC plans to follow up with the project teams and discuss options like retirement, finding liaisons and switch projects to a DPL governance model, or moving the projects to a Special Interest Group (SIG). We briefly discussed the upcoming PTG (Project Teams Gathering), with a suggestion to dedicate the first two days to cross-project discussions to encourage collaboration. The meeting concluded with a discussion about vendoring a BSD-3 licensed library, ply, into the yaql project, which the TC approved after confirming the license is compatible with OpenStack's Apache V2 license [9]. The next meeting of the OpenStack Technical Committee is on September 23, 2025. This meeting will be hosted on OFTC's #openstack-tc IRC channel and will begin at 1700 UTC. Please find the meeting's agenda on the wiki [10]. I hope you'll be able to join us there! === Governance Proposals === ==== Open For Review ==== - Add TC/PTL results from 2026.1 election | https://review.opendev.org/c/openstack/governance/+/961598 - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 === Upcoming Events === - 2025-10-01: OpenStack 2026.1 "Flamingo" release day - 2025-10-03: OpenStack's Birthday Meetup, Austin: https://www.meetup.com/openinfra-austin/events/310508680 - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] "cycle-with-rc" release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] 2025.2 "Flamingo" Release highlights: https://releases.openstack.org/flamingo/highlights.html [4] 2026.1 TC election results: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [5] 2026.1 PTL election results: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [6] TC Meeting IRC Log, Sep 17th 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-16-17.00.html [7] 2026.1 Election Retrospective: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] Dealing with Mariadb/Mysql changes: https://etherpad.opendev.org/p/gazpacho-collations-charsets [9] Vendoring ply in OpenStack: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [10] TC Meeting Agenda, Sep 23rd 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[diversity] [outreachy] Call for mentors for Dec 2025 cohort
by Dmitry Tantsur 23 Sep '25

23 Sep '25

Hi folks! It's the Outreachy time of the year. Despite the enormous financial and organizational difficulties, the December cohort will start soon, and OpenStack is, as usual, a part of it. We're looking for mentors and their projects. Please submit your ideas to https://www.outreachy.org/communities/cfp/openstack/ by this Friday, Sep 26th. You can check my blog post https://owlet.today/posts/how-to-propose-the-best-project-for-outreachy/ on some tips. Note that, just like in the previous cycle, we'll only be able to fund one intern. I still hope we get a few project proposals for interns to choose from. Let me know if you have any questions! Dmitry on behalf on OpenStack community coordinators. P.S. Apologies for the late notice: it took us some time to confirm everything.

1 0

[neutron] bug deputy report for 2025w38
by Bence Romsics 22 Sep '25

22 Sep '25

Hi Team, We had the following new reports last week. Two of the High bugs are unassigned at the moment. High: * https://bugs.launchpad.net/neutron/+bug/2124252 [L3] A router with multiple GW ports fails when deleting the first one fixes proposed by Rodolfo: https://review.opendev.org/q/topic:bug/2124252 * https://bugs.launchpad.net/neutron/+bug/2124254 [L3] A router with multiple GW ports, if the first is deleted, the GW info is empty unassigned * https://bugs.launchpad.net/neutron/+bug/2124269 Can't bind an HA router_gateway port to chassis unassigned, could be related to the migration to HA Chassis Group RFEs: * https://bugs.launchpad.net/neutron/+bug/2123836 [RFE] Set a local TXT record in the DHCP agent/dnsmasq * https://bugs.launchpad.net/neutron/+bug/2124215 [RFE] Implement more graceful handling of dhcp_lease_duration reduction Opinion: * https://bugs.launchpad.net/neutron/+bug/2123848 [ovn-octavia-provider] Octavia LB not reachable with custom firewall appliance According to Froyo this should be discussed with OVN cores first. Invalid: * https://bugs.launchpad.net/neutron/+bug/2124259 [ovn] Direct routing (non NAT) does not work between VLAN and Geneve networks Problematic backport of WIP patches. * https://bugs.launchpad.net/neutron/+bug/2125034 During live-migration nova-conductor report 'No valid host was found' due to duplicated port bindings This looks like a nova bug, so I routed it to them. Cheers, Bence

1 0

[kolla][kolla-ansible] Python dependency handling in custom Ansible module without toolbox
by sarah.kh09＠gmail.com 22 Sep '25

22 Sep '25

Hi everyone, I'm developing a new Ansible module for one of the kolla-ansible roles, and it depends on a Python package that needs to be installed via pip on the target nodes. I understand that Kolla Ansible generally avoids installing Python packages directly on hosts, and prefers handling such dependencies through the kolla_toolbox container. However, in my case: - Deploying a sidecar container isn't feasible within our current architecture - Delegating execution to localhost or kolla_toolbox would introduce complexity that we’d rather avoid Given these considerations, I'm looking for alternative ways to handle this dependency while staying aligned with Kolla's principles of reproducibility and container isolation. Has anyone faced a similar situation or found a clean workaround? Is using kolla-toolbox the only standard and recommended approach in such cases? Thanks a lot for your help and feedback!

2 2

[nova] Nova API call duration increases after upgrading to Caracal
by Chang Xue 22 Sep '25

22 Sep '25

Hello, we recently upgraded from Bobcat to Caracal. After upgrading, an interesting increment of duration of nova api call is observed. It's involved to multiple API calls, e.g. os-query-sets, /v2.1/servers/detail, etc. And it seems to be accumulated, meaning whenever nova-api is restarted, the duration seems to be fairly fast, giving response within like 80, 90 ms. As it keeps running for like up to 10 days, the duration increases to over 500 ms. I noticed that Caracal is using UnifiedLimitsDriver instead of DbQuotaDriver. I tried to change nova.conf to use DbQuotaDriver but it seems not working well with reducing the duration. I understand that calling to Keystone and Placement (and likely other external APIs) could result to longer duration, but pretty confused why it shows up as accumulated. Wondering if anyone else in Openstack community noticed the similar issue, thanks!

6 14