- openstack-discuss - lists.openstack.org

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

02 Sep '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

3 10

[neutron][ovn] Logical Port Statistics
by James Denton 02 Sep '25

02 Sep '25

Hello all, Is anyone aware of a method to gather statistics (bytes in/out, packets, etc.) for logical router ports or similar when using ML2/OVN? I understand neutron-metering-agent parity is currently a feature gap, but I’m curious if there’s some OVN-native functionality that can provide those details. The ask is to provide a bytes-in/out counter for tenant routers, specifically on the external interface(s). Thanks, James Get Outlook for Mac <https://aka.ms/GetOutlookForMac>

3 3

[release][PTLs] Reminder to 2025.2 Flamingo Cycle highlights
by Elõd Illés 02 Sep '25

02 Sep '25

Hi, Let me remind you that this week is the week when 2025.2 Flamingo's Cycle highlights should be finalized (now that the Feature Freeze deadline has passed) so that they can be included in release marketing preparations. Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

[magnum] Proposing Scott Davidson as magnum-capi-helm core reviewer
by Michał Nasiadka 02 Sep '25

02 Sep '25

Hello, I’d like to propose Scott Davidson as a core reviewer for magnum-capi-helm repository. His insightful and timely reviews have been helping to drive fixes and new features - and it would be great to have him as part of the core reviewers team. Best regards, Michal Nasiadka

3 3

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

01 Sep '25

Hello Stackers, We're in the final leg of our release journey with the 2025.2 "Flamingo" release [1]. Last week, we observed a feature freeze across all OpenStack deliverables that follow a "cycle-with-rc" [2] release model. Project teams are now preparing their release candidates, which will be posted next week. Polls have opened to elect a Project Team Lead in the Horizon (OpenStack Dashboard) project, as well as to elect four representatives on the OpenStack Technical Committee. Polls will close on September 17th, 2025, at 23:45 UTC [2]. Election officials observed that a good portion of the electorate would not receive their ballots because they haven't signed up to receive emails from the election system: CIVS. Please do ensure that your preferred email on gerrit has been used to opt in to CIVS emails. If you opt in newly, you will not receive an email ballot; instead, you'll see a pending poll invitation on CIVS: https://civs1.civs.us/cgi-bin/opt_in.pl In the past week, the Watcher project team has constituted a new set of project liaisons, and election officials have let the TC know that four OpenStack project teams have not had any PTL nominees. These are Monasca, OpenStack Charms, Venus, and Vitrage. We expect to make some changes shortly. === Weekly Meeting === The OpenStack Technical Committee had its last weekly meeting over IRC on August 26th, 2025 [3]. We had a lively discussion on several key topics. We're closing out the 'Migrate from WSGI scripts to module paths' goal [4] as complete. We also discussed the status of the Monasca project team [5]. It's still a point of contention with some folks wanting to move forward with its retirement while others want to give a new contributor a chance to get it running again. We've decided to defer a final decision to allow for more discussion on Gerrit and to give the new contributor a chance to make some progress. Another important topic we covered was the impact of the recent OIF membership renewals on the ongoing TC elections. With a significant number of potential voters not renewing their memberships, we are concerned about potential disenfranchisement. We hope to urge renewals past these elections and share a follow-up regarding the elections to the OIF Board. Finally, we discussed a proposed "phone-home" patch in the Cinder project [6]. While the feature technically sends data to an external storage system rather than an OpenStack service, there was a consensus that any "call-home" functionality should be opt-in, not enabled by default. This is a matter of respecting user privacy and not making assumptions about an operator's environment. Jon Bernard (jbernard) plans to draft a formal resolution to address this, and we'll advise on the process. The next meeting of the OpenStack TC is on Tuesday, September 2nd, 2025. This meeting will be hosted simultaneously on Meetpad (video) and IRC (#openstack-tc on OFTC) at 1700 UTC. Please find the agenda and call details on the meeting's wiki page [7]. I hope you'll be able to join us there! === Governance Proposals === ==== Merged ==== - Use DPL model for Watcher project leadership for 2026.1 release | https://review.opendev.org/c/openstack/governance/+/958085 ==== 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 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Mark "Migrate from wsgi scripts" goal as completed | https://review.opendev.org/c/openstack/governance/+/958817 === Upcoming Events === - 2025-09-06: OpenInfra Days, Kenya: https://www.meetup.com/kenya-openinfra-user-group/ - 2025-09-17: OpenStack TC and Horizon project elections conclude: https://governance.openstack.org/election/ - 2025-09-09: OIF Board Monthly meeting: https://board.openinfra.org/ - 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) OpenStack TC Chair [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] TC Meeting IRC Log, August 26th 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-08-26-17.00.html [4] Community Goal to update wsgi configuration: https://governance.openstack.org/tc/goals/proposed/migrate-from-wsgi-script… [5] Retiring the Monasca project team: https://review.opendev.org/c/openstack/governance/+/953671 [6] Cinder driver phoning home: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [7] TC Meeting Agenda, September 2nd, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[neutron] Bug deputy report (week starting on August 25)
by Elvira Garcia Ruiz 01 Sep '25

01 Sep '25

Hi folks, Here you have the list of bugs reported for Neutron during last week. (Aug 25 - Aug 31) High ------- - https://bugs.launchpad.net/neutron/+bug/2121609 flake8 plugins from neutron-lib are enabled by default, breaking existing projects dependent on it Fix proposed by Takashi Kajinami https://review.opendev.org/c/openstack/neutron-lib/+/958786 - https://bugs.launchpad.net/neutron/+bug/2121649 [n-t-p] Test "test_subport_connectivity" failing randomly in 2025.1 Unassigned. Medium ----------- - https://bugs.launchpad.net/neutron/+bug/2121605 nova and neutron pagination returns an http, not https href link Unassigned Low ------ - https://bugs.launchpad.net/neutron/+bug/2121530 [SR-IOV] Trusted VF port MAC address can be changed from inside the VM Fix proposed by Ralonsoh https://review.opendev.org/c/openstack/neutron/+/958877 Undecided -------------- - https://bugs.launchpad.net/neutron/+bug/2121582 Source / Destination IP address is not respected in firewall group rule FWaaS v2 Unassigned. I will ask mlavalle about how to triage this since it’s ovs-fw related if I understand correctly. Best regards! Elvira

1 0

Setting up HA in OpenStack with Kolla-Ansible (Instance failover across compute nodes)
by Thamanna Farhath 01 Sep '25

01 Sep '25

Hi OpenStack Community, I have installed *Masakari* using Kolla-Ansible, and after that I also installed *HACluster*. However, the HACluster containers are failing and keep exiting. Setup: - 3 controller nodes - Multiple compute nodes - Deployment: Kolla-Ansible My questions are: 1. Do I really need Masakari together with HACluster for instance HA? 2. Is there an alternative or recommended way to deploy HACluster with Kolla-Ansible? 3. Has anyone faced the issue where HACluster containers keep exiting after deployment? Any guidance, troubleshooting tips, or experiences would be very helpful. Thamanna Farhath Associate Engineer R&D mailto:manoj.kumar@zybisys.com thamanna.f(a)zybisys.com https://www.zybisys.com https://in.linkedin.com/company/zybisys https://www.facebook.com/Zybisys/ https://www.instagram.com/ZyBiSys/ https://www.youtube.com/@zybisys https://www.facebook.com/Zybisys/ Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

1 0

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

01 Sep '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.

5 4

[release] Release countdown for week R-4, Sep 01 - 05
by Elõd Illés 29 Aug '25

29 Aug '25

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the 2025.2 "Flamingo" deliverables can be proposed, well ahead of the final 2025.2 "Flamingo" release date. General Information ------------------- We are still finishing up processing a few release requests, but the 2025.2 "Flamingo" release requirements are now frozen. If new library releases are needed to fix release-critical bugs in 2025.2 "Flamingo", you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in 2025.2 "Flamingo" that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By September 26th, 2025 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/2025.2 branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for 2025.2 "Flamingo" changes should be added there to make sure the consumers of your release notes see them. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 12th, 2025 (R-3 week) Final RC deadline: September 26th, 2025 (R-1 week) Final 2025.2 "Flamingo" release: October 1st, 2025 OpenInfra Summit Europe: October 17th-19th, 2025 Előd Illés irc: elodilles @ #openstack-release

1 0

[release][swift][ironic] Deliverables missing Flamingo releases
by Thierry Carrez 29 Aug '25

29 Aug '25

Hi everyone, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the 2025.2 Flamingo cycle: bifrost ironic-inspector ironic-prometheus-exporter ironic-ui networking-generic-switch swift Those should be released ASAP, and in all cases before September 12th, so that we have a release to include in the final 2025.2 Flamingo release. -- Thierry Carrez (ttx)

1 0