February 2026 - openstack-discuss

[cinder] festival of reviews friday 2026-02-06
by Brian Rosmaita 04 Feb '26

04 Feb '26

Hello Argonauts, This is a reminder that the twice-monthly Cinder Festival of Reviews will be held at the end of this week on Friday 6 February. who: Everyone! what: The Cinder Festival of Reviews when: Friday 6 February 2026 from 1400-1600 UTC where: videoconf info on the etherpad etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews This recurring meeting, that happens on the first and third Friday of each month, can be placed on your calendar by using this handy ICS file: https://meetings.opendev.org/calendars/cinder-festival-of-reviews.ics See you there!

1 0

[all][elections][ptl][tc] Combined PTL/TC 2026.2 cycle Election Nominations Kickoff
by Ian Y. Choi 04 Feb '26

04 Feb '26

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 18, 2026 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/2026.2/<Project_Name or "TC">/<email_address> (for example, "candidates/2026.2/TC/stacker(a)example.org"). The name of the file should match an email address for your current Foundation Individual Membership. Take this opportunity to ensure that your Open Infrastructure Foundation member profile contains current information: https://openinfra.org/a/profile Any Open Infrastructure Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an Open Infrastructure Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Feb 25, 2026 23:45 UTC through to Mar 18, 2026 23:45 UTC. The electorate for the TC election are the Open Infrastructure Foundation Individual Members who have a code contribution to one of the official teams over the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC, as well as any Extra ACs who are acknowledged by the TC. The electorate for a PTL election are the Open Infrastructure Foundation Individual Members who have a code contribution over the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ACs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ACs. Please find below the timeline: PTL + TC nomination starts @ Feb 04, 2026 23:45 UTC PTL + TC nomination ends @ Feb 18, 2026 23:45 UTC TC campaigning starts @ Feb 18, 2026 23:45 UTC TC campaigning ends @ Feb 25, 2026 23:45 UTC PTL + TC elections start @ Feb 25, 2026 23:45 UTC PTL + TC elections end @ Mar 18, 2026 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2026-02-18 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and Foundation individual member profiles can be updated at https://review.opendev.org/#/settings/contact and https://openinfra.org/a/profile accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials

1 0

[nova][ci] nova-next job is failing 100%
by melanie witt 04 Feb '26

04 Feb '26

Hey all, Just a heads up that we currently have a 100% fail rate broken nova-next job due to the following bug: https://bugs.launchpad.net/cinder/+bug/2127196 Fixes on both the Cinder and Nova side are proposed: * https://review.opendev.org/c/openstack/cinder/+/975540 * https://review.opendev.org/c/openstack/nova/+/975542 Please hold your rechecks until at least one of these patches is merged. Cheers, -melwitt

1 1

[qa][ptg] Call for 2026.2 vPTG QA topic
by Ghanshyam Maan 04 Feb '26

04 Feb '26

Hi All, I have created the etherpad to collect the QA topics for the coming vPTG (2026.2 cycle). Based on the topics, we will decide if we need any slots in PTG. Seeing the PTG signup deadline, please add your topics before Feb 17th so that we can discuss the same in Feb 18th QA office hour. - https://etherpad.opendev.org/p/qa-2026.2-ptg -gmann

1 0

[all][elections][ptl][tc] Combined PTL/TC 2026.2 cycle Election Season
by Ian Y. Choi 04 Feb '26

04 Feb '26

Election details: https://governance.openstack.org/election/ The nomination period officially begins Feb 04, 2026 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in these governance documents[1][2][3]. Due to circumstances of timing, PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. Similarly, there will only be a TC poll if there are more than 5 candidates stepping forward the available TC positions. All members of the community are encouraged to confirm their email address as described at: https://governance.openstack.org/election/#electorate All candidates and prospective voters need to make sure they have reestablished their individual memberships in the Open Infrastructure Foundation https://openinfra.org/a/renew-membership (if this URL redirects you to your profile page, your membership is already renewed and nothing more is required), otherwise their nominations won't be verified and ballots will not be sent. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you wish to discuss in private please email any of the election officials[4] so that we may address your concerns. Thank you, [1] https://governance.openstack.org/tc/reference/charter.html [2] https://governance.openstack.org/tc/reference/role-of-the-tc.html [3] https://docs.openstack.org/project-team-guide/ptl.html [4] https://governance.openstack.org/election/#election-officials

1 0

[ironic] A first-class physical location API?
by Jay Faulkner 03 Feb '26

03 Feb '26

Something I've seen come up in a few discussions over the last couple of cycles is the need for Ironic to contain more useful information about the physical world. It's made me wonder if there's an opportunity to add bigger support for physical characteristics/locations? I'm thinking metadata like: - Datacenter the server is in - Computer room (or other DC subdivision) - Row - Rack - Slot # - Physical cabling (e.g. what switches you might be connected to and how) Do other folks see this need? I'm trying to tease out if there's something here or not, so just curious about use cases and what people think. -Jay

4 5

[tc][ptls] Streamlining the OpenStack User Survey
by Allison Price 03 Feb '26

03 Feb '26

Hi everyone, Today in the OpenStack TC meeting, I shared the intention of streamlining the OpenStack User Survey[1] in an effort to increase participation while still preserving the valuable insights we get from the responses. As a next step, I wanted to share an etherpad[2] with some context on what we are trying to achieve with this process as well as some pointed questions to help guide us as we make changes to improve the survey. If you have taken or reviewed the results of the OpenStack User Survey, please share your insights. This is an incredibly valuable tool and I want to ensure that any changes that we make are intentional and can help support the upstream community. I know everyone is in the middle of 2026.1 Gazpacho work, so we have some time. If possible, I would like to have as much input as possible in the etherpad by April 15 so we can then use the upcoming virtual PTG[3] to go through the responses and make a plan. Then, we can implement the changes in August 2026 for the next version of the survey. If you have any questions or would like to ensure you’re a part of this process, please let me know. I will send reminders as we get closer to the PTG. Thanks, Allison [1] https://www.openstack.org/user-survey [2] https://etherpad.opendev.org/p/OpenStack-User-Survey-Streamlining [3] https://openinfra.org/ptg

1 0

[neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects
by Maximilian Stinsky-Damke 03 Feb '26

03 Feb '26

Hello, I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609: https://bugs.launchpad.net/neutron/+bug/1998609) and the associated patch (https://review.opendev.org/c/openstack/neutron/+/867513) As noted in the bug comments, Roberto Bartzen Acosta maintained this patch across multiple release cycles, but it hasn't received reviews from core maintainers and is currently blocked by merge conflicts. Roberto mentioned that the feature hasn't been getting traction despite the work put in. This feature would enable distributed routing for IPv6 GUA addresses in OVN deployments, similar to how IPv4 FIPs work with DVR today. The spec was approved and merged (https://review.opendev.org/c/openstack/neutron-specs/+/867979) indicating community interest. Before I invest time rebasing the patch and resolving merge conflicts, I'd like to understand: 1. Are there technical or architectural concerns that have prevented review? 2. Is there a reason this hasn't been prioritized, or is it a matter of reviewer availability? 3. Would core maintainers be willing to review if the patch is rebased and updated? I'm happy to do the rebase work, but I'd prefer not to spend time on something that won't be merged. Any guidance on the status and viability of this feature would be appreciated. Thanks, Max

2 5

OVN issues
by engineer2024 03 Feb '26

03 Feb '26

HI, I am trying to setup an extport host to act as host for an sriov vm IP. Set it up using ovs-vsctl set Open_vSwitch . external_ids:ovn-cms-options=enable-chassis-as-extport-host But when a vm is created with this sriov port, it is not able to reach the metadata service at 169.254.169.254. Inside the vm vm:~# ip r 10.1.0.0/24 dev ens5 proto kernel scope link src 10.1.0.20 169.254.169.254 via 10.1.0.12 dev ens5 proto dhcp src 10.36.160.60 metric 100 On the node marked as the extport host for this vm's ip, its ovn-controller log shows --------- 2026-01-29T11:52:26.922Z|00069|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf up in Southbound 2026-01-29T11:52:27.849Z|00070|binding|INFO|Releasing lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf from this chassis (sb_readonly=0) 2026-01-29T11:52:27.851Z|00071|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf down in Southbound 2026-01-29T11:52:28.480Z|00072|binding|INFO|Claiming lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf for this chassis. 2026-01-29T11:52:28.480Z|00073|binding|INFO|a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf: Claiming fa:16:3e:f3:82:f9 10.1.0.20 2026-01-29T11:52:28.482Z|00074|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf up in Southbound 2026-01-29T11:52:29.486Z|00075|binding|INFO|Releasing lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf from this chassis (sb_readonly=0) 2026-01-29T11:52:29.489Z|00076|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf down in Southbound ------------ It is fluctuating intermittently and not stable. Why is this flapping ? Also the metadata proxy is running fine on the extport host ip netns exec ovnmeta-7d9a4c21-1e6f-4f2b-9a84-3c8e1b7d62f0 telnet 169.254.169.254 80 Trying 169.254.169.254... Connected to 169.254.169.254. # ip netns exec ovnmeta-7d9a4c21-1e6f-4f2b-9a84-3c8e1b7d62f0 ss -ln | grep 80 tcp LISTEN 0 1024 169.254.169.254:80 <http://169.254.169.254/> 0.0.0.0:* # ps -ef | grep ovn-meta root 408634 1 9 11:52 ? 00:02:45 neutron-ovn-metadata-agent (/openstack/venvs/neutron-29.2.3/bin/python3 /openstack/venvs/neutron-29.2.3/bin/neutron-ovn-metadata-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_ovn_metadata_agent.ini) root 408673 1 0 11:52 ? 00:00:00 haproxy -f /var/lib/neutron/ovn-metadata-proxy/7d9a4c21-1e6f-4f2b-9a84-3c8e1b7d62f0.conf root 421770 388277 0 12:21 pts/12 00:00:00 grep --color=auto ovn-meta

2 1

[manila] Removal of the "manila" CLI
by Carlos Silva 03 Feb '26

03 Feb '26

Hello everyone, Following up on our deprecation of the manila shell client, we are officially announcing its removal in the 2026.1 Gazpacho release [1]. The legacy manila shell was first deprecated in the OpenStack Zed release. Since then, we have achieved full feature parity with our OpenStackClient (OSC) plugin. Moving forward, Manila will exclusively support the "openstack share" command set. No new features have been added to the legacy "manila" client since its deprecation, and it did not support recent API microversions. The manila executable will no longer be installed or supported. All management and provisioning tasks must be performed using the openstack CLI (e.g., openstack share create instead of manila create). If you are still using the "manila" command in your automation, CI/CD pipelines, or daily workflows, please migrate to the openstack CLI immediately. We appreciate your cooperation as we move toward a more maintainable OpenStack CLI experience. Regards, carloss [1] https://review.opendev.org/q/topic:%22bp/openstack-client-support%22+(statu…

1 0