August 2025 - openstack-discuss - lists.openstack.org

[all][elections][ptl][tc] Conbined PTL/TC 2026.1 cycle Election Voting Kickoff
by Ian Y. Choi 27 Aug '25

27 Aug '25

Polls for PTL and TC elections are now open and will remain open for you to cast your vote until Sep 17, 2025 23:45 UTC. We are selecting 4 TC members, and are having PTL elections for Horizon. Please rank all candidates in your order of preference. You are eligible to vote in the TC election if you are a Foundation individual member[0] that also has committed to any official project team's deliverable repositories[1] over the Sep 13, 2024 00:00 UTC - Aug 20, 2025 00:00 UTC timeframe (2025.1 to 2025.2) or if you are in the list of extra-acs[2] for any official project team. You are eligible to vote in a PTL election if you are a Foundation individual member[0] and had a commit in one of that team's deliverable repositories[1] over the Sep 13, 2024 00:00 UTC - Aug 20, 2025 00:00 UTC timeframe (2025.1 to 2025.2) or if you are in that team's list of extra-acs[2]. If you are eligible to vote in an election, you should find your email with a link to the Condorcet Internet Voting Service (CIVS) page to cast your vote in the inbox of your Gerrit preferred email[3]. What to do if you don't see the email and have a commit in at least one of the projects having an election: * due to a new CIVS policy, to get the email from poll supervisors, you must opt in to email communication opt in with your Gerrit email address at: https://civs1.civs.us/cgi-bin/opt_in.pl * eligible voters who opt in to email communication late can see a pending poll invitation and vote until Sep 17, 2025 23:45 UTC. * check the trash or spam folders of your Gerrit Preferred Email address, in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the project's deliverable repos[0] and email the election officials[4]. If we can confirm that you are entitled to vote, we will add you to the voters list for the appropriate election. Our democratic process is important to the health of OpenStack, please exercise your right to vote! Candidate statements/platforms can be found linked to Candidate names on this page: https://governance.openstack.org/election/ Happy voting, [0] https://www.openstack.org/community/members/ [1] The list of the repositories eligible for electoral status: https://opendev.org/openstack/governance/src/tag/0.19.0/reference/projects.… [2] Look for the extra-acs element in [1] [3] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your preferred email. That is where the ballot has been sent. [4] https://governance.openstack.org/election/#election-officials

1 0

[Nova&Neutron] pagination returns an http, not https href link
by Chang Xue 27 Aug '25

27 Aug '25

Hello, we just migrated using new openstack CLI tools, and when using pagination for both Nova and Neutron, we noticed that they are returning http href link although they are expecting https, causing failure: ``` openstack port list Failure: Unable to establish connection to http://openstack....example.com:9696/v2.0/ports: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')). Retrying in 0.5s.1 retries left Unable to establish connection to http://openstack.....example.com:9696/v2.0/ports: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) ``` Is this a bug in Nova/Neutron? I tried other services like Heat, Keystone, etc, and they either returning https href links or just take relative path without schema/host. Thanks, Chang

1 0

[ironic] Future of Metalsmith
by Jay Faulkner 27 Aug '25

27 Aug '25

For almost two years, the Ironic team has had a "maintenance mode" message on the Metalsmith readme: "Please note the Metalsmith project is in maintenance mode and it's functionality is slowly being introduced into Ironic's API and usual clients. No additional features are expected to be added to Metalsmith directly." CI is currently not passing on this repository, and as far as I can tell there are no engaged users of this project upstream, and no current maintainers of Ironic invested in keeping this project afloat. I propose we retire the metalsmith project and exclude it from the Flamingo release. Are there any objections? Thanks, JayF

3 3

[oslo] status of eventlet removal for oslo.service?
by Chris Friesen 27 Aug '25

27 Aug '25

Hi everyone, Looking at the "epoxy" spec for removing Eventlet from oslo.service (https://specs.openstack.org/openstack/oslo-specs/specs/epoxy/remove-eventle…) the very top line is a link to search blueprints.launchpad.net. Following that link it seems like there is no blueprint for removing eventlet from oslo.service, so does the spec itself (with the proposed milestones) represent the current plan? Separately, is there somewhere that shows the progress on the threading backend for oslo.service? I see it exists, are there any limitations on the current implementation? Thanks, Chris

2 1

[ops] [all] One Week until 2025 OpenStack User Survey Deadline
by Allison Price 27 Aug '25

27 Aug '25

Hi everyone, I wanted to remind everyone that next Friday, August 29 is the deadline to complete this year’s OpenStack User Survey. If you haven’t taken it before, this is a great opportunity to help channel feedback to the upstream community while helping us understand the global OpenStack footprint better. It should only take ~20 minutes and is incredibly valuable. If you have taken it before, it’s still important to review and update your data. This should only take a few minutes. https://openstack.org/usersurvey Thank you all! Cheers, Allison

2 2

[keystone][ops] Upgrade to 2025.1 and "corner cases"
by Dmitriy Rabotyagov 27 Aug '25

27 Aug '25

Hey folks, I wanted to raise awareness of operators regarding Keystone upgrade to Epoxy (2025.1), as found that existing release notes are slightly more vague about corner case definition. During analysis, it appeared that a lot of users (and under "a lot" I mean 4 figures number) in my really old deployments (which were deployed during Newton), still in use passwords hashed with sha512_crypt which has been dropped in 2025.1 [1]. As this was referenced as a "corner case" in upgrade docs, it may not bring enough attention to this matter reading notes, while sha512_crypt removal is mentioned in "Other" section which I personally missed when analyzing upgrade requirements. So I would highly recommend to ensure that all your users are using supported hashing algorithms before the upgrade to Epoxy, and inform them to reset their passwords if they don't. You can list users who are using unsupported hashing algorithm using following MySQL query: SELECT distinct l_u.user_id FROM keystone.local_user AS l_u JOIN keystone.password AS hash ON l_u.id = hash.local_user_id WHERE (hash.password_hash LIKE '$6$%' OR hash.password_hash LIKE '$5$%') AND hash.expires_at i s null; Hope this helps somebody to save some time in the future. [1] https://opendev.org/openstack/keystone/commit/4a4137d5f77ced3f4f011846fb9c2…

6 10

[ironic][magnum][tacker][telemetry][venus][vitrage] broken gate on master branch
by Elõd Illés 27 Aug '25

27 Aug '25

Hi teams in $SUBJECT, The release team usually checks the gate health of deliverables that did not have merged patches recently and it seems you have a project with broken gate: https://review.opendev.org/q/topic:release-health-check-flamingo+is:open Could you please check and fix the gate so that we don't release 2025.2 Flamingo with a broken state. Thanks in advance, Előd Illés irc: elodilles @ #openstack-release

4 3

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

26 Aug '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!

5 11

[all][elections][tc] TC Election Campaigning Kickoff
by Ian Y. Choi 26 Aug '25

26 Aug '25

Developers, The TC Election Campaigning Period has now started[1]. During the next couple days, you are all encouraged to ask the candidates questions about their platforms[2], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform[2], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. [1] https://governance.openstack.org/election/ [2] https://opendev.org/openstack/election/src/branch/master/candidates/2026.1/… Ian Y. Choi & Slawek Kaplonski, on behalf of election officials.

4 3

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

26 Aug '25

Hello Stackers, We're nearing the feature freeze date for the 2025.2 "Flamingo" release [1]. It's on Thursday, August 28, 2025. In the past week, we wrapped up the nomination window for the upcoming community elections [2]. We are currently observing a week of campaigning for TC positions where you may ask the candidates to share their views on any subject pertaining to the community. Their profiles and platforms are posted on the elections website [3]. The elections will begin on August 27, 2025, and will wrap up in three weeks. Also in the past week, the TC defined the tested runtimes and operating systems across OpenStack projects for the upcoming 2026.1 "Gazpacho" release [4]. Our hope is that project teams will prioritize technical debt, such as dropping the use of the eventlet library per our envisioned timeline, so we can match these runtime changes. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee occurred on August 19, 2025 [5]. The main topics of discussion were updates on the 2026.1 elections, the retirement process for Monasca repositories, and the ongoing issues with the Zuul CI system. A good portion of the meeting was dedicated to reviewing the election status, where we discussed the low engagement from some project teams with the election process. The change in OIF membership semantics affected several PTL and TC nominations and has resulted in a significantly reduced electorate. The meeting also addressed the Monasca repository retirement, where the path forward for deleting unmaintained branches and merging "empty" changes was discussed. Lastly, the meeting briefly touched on the impact of a recent Ansible version update on Zuul, which has caused job failures for jobs running on older Ubuntu nodes and older Python versions. If you're affected, please do consider migrating these jobs, or bring your concerns to OFTC's #opendev channel. The next meeting of the OpenStack Technical Committee is today, August 26, 2025, at 1700 UTC. This meeting will be hosted over IRC in OFTC's #openstack-tc channel. Please find the agenda and other details on the meeting's wiki [6]. I hope you'll be able to join us there. === Governance Proposals === ==== Merged ==== - Define testing runtime for 2026.1 release | https://review.opendev.org/c/openstack/governance/+/957199 ==== Open for Review ==== - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Show inactive project status in project.yaml | https://review.opendev.org/c/openstack/governance/+/958229 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Use DPL model for watcher project leadership for 2026.1 release | https://review.opendev.org/c/openstack/governance/+/958085 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-08-26: OpenInfra Days, Korea: https://2025.openinfradays.kr/ - 2025-08-27: OpenStack 2026.1 Election Voting begins: https://governance.openstack.org/election/ - 2025-08-28: Feature Freeze deadline, Milestone-3 of the Flamingo release [1] - 2025-08-29: Colombia OpenInfra User Group Meetup: https://www.meetup.com/colombia-openinfra-user-group/events/307096751/ - 2025-09-09: OIF Board Monthly meeting: https://board.openinfra.org/ - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] Nominations close email: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] 2026.1 TC Candidates: https://governance.openstack.org/election/#tc-candidates [4] Tested Runtimes for Gazpacho: https://governance.openstack.org/tc/reference/runtimes/2026.1 [5] TC Meeting IRC Log, Aug 19, 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-08-19-17.00.html [6] TC Meeting Agenda, Aug 26, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0