The Big Picture

The week of feature freeze for the 2025.2 "Flamingo" release (it landed Thursday, August 28, per the TC's R-5 summary) was, fittingly, all about closing things out: cutting missing releases, squashing bugs, and tidying up gates ahead of release candidates. The release team marked week R-4. The most operator-relevant story was a sharp warning about a Keystone upgrade gotcha that can lock out thousands of users, while governance continued to grapple with a reduced electorate and several struggling project teams as the 2026.1 "Gazpacho" elections got underway.

Development & Technical Decisions

The standout operator warning came from Dmitriy Rabotyagov in "[keystone][ops] Upgrade to 2025.1 and 'corner cases'." Upgrading to Epoxy (2025.1) drops support for sha512_crypt password hashing, but the upgrade docs bury this in an "Other" section and frame it as a corner case. In his older deployments (originally Newton-era), Dmitriy found a four-figure number of users still on sha512_crypt or sha256_crypt hashes — all of whom would be unable to authenticate post-upgrade. He shared a MySQL query to identify affected users (matching $6$ and $5$ hashes) and strongly recommends auditing users and forcing password resets before upgrading to Epoxy. This is the most actionable item of the week for anyone on the upgrade path.

A second cross-cutting issue: Dmitriy also flagged that an oslo.messaging QManager fix for containers introduced a regression (backported to 2024.1) that fails to handle os.getpgrp() returning 0 in edge cases — which can make Nova database syncs impossible during upgrades when QManager is in use. He's asking for review of the long-pending fix (review 939540) as an upgrade blocker.

Chang Xue's http-vs-https pagination href thread continued: Nova and Neutron return http links in paginated responses even when clients expect https, causing connection failures, whereas Keystone, Heat and others behave correctly — raising the question of whether this is a genuine Nova/Neutron bug rather than something to paper over in HAProxy. James Denton kept exploring per-port statistics in ML2/OVN for tenant-router external interfaces, an acknowledged metering feature gap. On Ironic, Jay Faulkner proposed making the just-cut Flamingo-versioned Metalsmith release the final one ever, then retiring the master branch after the integrated release completes. Chris Friesen sought clarity on the eventlet-removal plan for oslo.service, noting the spec lacks a matching Launchpad blueprint and asking where threading-backend progress and limitations are tracked.

Releases & Announcements

With feature freeze hitting mid-week, release-readiness reminders piled up. Elõd Illés posted the R-4 countdown, and Thierry Carrez flagged cycle-with-intermediary deliverables that have done no Flamingo release at all — bifrost, ironic-inspector, ironic-prometheus-exporter, ironic-ui, networking-generic-switch, and swift — asking that they be released ASAP and in all cases before September 12 so each has something to include in the final Flamingo. Carlos Silva announced the Manila Flamingo bug squash (Sep 2–4), focused on closing in-progress bugs and triaging the backlog.

Community & Events

The combined PTL/TC 2026.1 election entered its voting phase (Ian Y. Choi): polls opened August 27 and close September 17 at 23:45 UTC, electing four TC members plus a Horizon PTL. Eligibility requires OpenInfra Foundation membership plus a qualifying commit; voters must opt into CIVS emails to receive a ballot. The TC's R-5 summary reiterated the concern that OIF membership-renewal changes have shrunk the electorate, and noted the TC has defined the tested runtimes and operating systems for the 2026.1 "Gazpacho" cycle — with a push for teams to prioritize tech debt (notably eventlet removal) to match.

Goutham Pacha Ravi's TC campaign thread asked candidates how they'd handle project teams essential to the ecosystem but lacking active contributors or sustainable governance — a live question given the Monasca retirement discussion and several leaderless teams. The User Survey deadline was approaching, though Eugen Block reported the survey form is partly broken (mixed German/English questions and a ranking UI that won't accept valid input).

On the operational side, several troubleshooting threads recurred: Masakari + HACluster containers crash-looping on Kolla-Ansible (a repeat ask), OVN agent aliveness/HA-chassis-group failover not updating port bindings when a metadata agent is stopped, and a broken master gate across Ironic, Magnum, Tacker, Telemetry, Venus, and Vitrage that Yasufumi Ogawa partly fixed (tacker-horizon). Michał Nasiadka and Jake Yip proposed Scott Davidson as a magnum-capi-helm core reviewer. The Public Cloud SIG held its bi-weekly meeting, and the Ironic team canceled its September 1 meeting for US Labor Day.

Heads Up / Action Needed

• Before upgrading Keystone to Epoxy (2025.1): audit users for sha512_crypt/sha256_crypt hashes and force resets — otherwise affected users (potentially thousands) will be unable to log in.
• Release by September 12: bifrost, ironic-inspector, ironic-prometheus-exporter, ironic-ui, networking-generic-switch, and swift have no Flamingo release yet.
• oslo.messaging upgraders: review fix 939540 — the QManager container regression can block Nova DB syncs during upgrades.
• Vote by Sept 17, 23:45 UTC (four TC seats + Horizon PTL) and confirm your CIVS opt-in.
• Manila bug squash Sep 2–4 — add bugs to the etherpad and join the kickoff.