- openstack-discuss - lists.openstack.org

[tacker] Cancelling weekly IRC meeting
by Yasufumi Ogawa 20 Feb '26

20 Feb '26

Hi Tacker team, Due to a holiday in Japan and most of team members aren't join, I'm cancelling meeting this week. Regards, Yasufumi

1 0

[all][elections][ptl] Opt in to CIVS voting system
by Ian Y. Choi 20 Feb '26

20 Feb '26

The election uses the Condorcet Internet Voting Service (CIVS). Due to CIVS policy, to vote in private CIVS polls, you must opt in to email communication. To opt in, please enter your Gerrit email address in the following page before the start of the election Feb 25, 2026 23:45 UTC, and confirm with the code that will be sent to you via email. https://civs1.civs.us/cgi-bin/opt_in.pl If you have any questions, please contact the election officials. https://governance.openstack.org/election/#election-officials

1 0

Nova Multi-Cell Live Migration Issues
by Tyler Wilson 20 Feb '26

20 Feb '26

Hello All, I'm trying to get a 2 cell setup going as a test environment and am running into some troubles. I seem to be able to start VM's just fine, however when I try live-migrations I am getting this error: 2026-02-19 20:11:01.448 1 ERROR nova.conductor.manager [None req-91d4c1c6-a69f-41d4-a3ca-c0890bde0af8 - - - - - -] Migration of instance 73123ed9-d112-4030-945c-96c75a016d55 to host compute1 unexpectedly failed.: oslo_messaging.rpc.client.RemoteError: Remote error: RemoteError Remote error: CantStartEngineError No sql_connection parameter is established I see this on the following service logs nova-conductor (superconductor role only) nova-api nova-compute What is odd is that I don't see any activity in the cell-conductor when this happens, even with debug enabled. Here are the configured connection strings I have in each conductor/api/compute services: https://pastebin.com/raw/uuamtzsk Are these the correct database connection strings for each service? I'm basing this off the multi-cell diagram in the docs. The fact that the cell-conductors aren't showing any activity when this happens is throwing me off. I feel like I'm missing something here but I can't put my finger on it. Any help would be appreciated, thanks!

2 2

[release] Release countdown for week R-5, Feb 23 - 27
by Elõd Illés 20 Feb '26

20 Feb '26

Development Focus ----------------- We are getting close to the end of the 2026.1 Gazpacho cycle! Next week on February 26th, 2026 is the Gazpacho-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2026.2 Hibiscus cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on February 26th, 2026. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2026.1 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… February 26th, 2026 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also a good time for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Gazpacho-3 milestone (feature freeze): February 26th, 2026 (R-5 week) RC1 deadline: March 12th, 2026 (R-3 week) Final RC deadline: March 26th, 2026 (R-1 week) Final 2026.1 "Gazpacho" release: April 1st, 2026 2026.2 "Hibiscus" (virtual) PTG: April 20-24, 2026 Előd Illés irc: elodilles @ #openstack-release

1 0

Feb 19 Digital Sovereignty WG Recording + Next Steps
by Kendall Nelson 19 Feb '26

19 Feb '26

Hello All! Thank you to all those that were able to find the time to attend and participate in this week's meeting! For those that were not able to attend, here is the recording of today's meeting so that you can catch up and stay engaged with these efforts: https://zoom.us/rec/share/a5cXdx6RsWRNuGt8uqyQEgrVDNnIbexDag8NaUEzhcuyiUmTh… *Now, as far as next steps go: * - Soon, Allison and I will send around some samples of stance text for the landing page and we will *NEED* your feedback and opinions to make sure we have everything covered. - If you have a use case that you think would be good to share, please start working on those case studies ASAP! While we don't need them to launch the landing page (which is scheduled for March 20th-ish) the more content we have ready to go early on, the better! - If you are interested in helping with either of the other initial deliverables ( the comparison sheet or the best practices doc), please add your name to those sections of the etherpad <https://etherpad.opendev.org/p/Digital-Sovereignty-WG>. Also, if you have additional resources that would be helpful in crafting either deliverable, add them to the etherpad. Feel free to also get started throwing content in either as well! They will be living documents in draft form for a while, so nothing has to be perfect. Focus on just getting content in and we will polish things up later. When Allison and I send drafts of stances for review, we will also send out the poll for selecting the next meeting time which is slated for the week of March 9th, likely the 10th, 11th or 12th. Whew, that was a lot of information, but we have a lot of work to get done as a group! I am so excited to see this effort through with you all; we are a strong community and we are stronger together, so thank you for sharing your expertise and time with the Digital Sovereignty Working Group. -- Kendall Nelson *Senior Upstream Developer Advocate* The OpenInfra Foundation <https://openinfra.dev/>

1 0

[all] POST_FAILURE in openstack-tox-py310
by Takashi Kajinami 19 Feb '26

19 Feb '26

I feel like this week is one of the most exciting week we have had recently :-P We started seeing consistent POST_FAILURE in openstack-tox-py310 (and other jobs using py310). https://github.com/testing-cabal/testtools/issues/569 The issue was caused by testtools and was fixed in testools 2.8.4, but we likely need to rebuild the image used in CI to pull the fixed version. Please avoid mass recheck or merging any new changes now before you check the CI status carefully. Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 3

[neutron] Drivers meeting canceled Friday, February 20th
by Brian Haley 19 Feb '26

19 Feb '26

Hello Neutrinos: I am going to cancel tomorrow's Drivers meeting as there are no topics on the agenda. Just a reminder that our open spec list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

[kolla-ansible][ironic] Simple setup for baremetal in Flamingo OpenStack
by vincent lee 19 Feb '26

19 Feb '26

Hi all, I am currently experiencing issues while setting up a basic ironic deployment. My environment consists of a controller running Ubuntu 24.04 and a baremetal host with IPMI support but no operating system installed. I am using kolla-ansible for the Flamingo version OpenStack deployment, and all configuration is being managed through the globals.yml file. One of the controller’s network interfaces is configured to provide DHCP and is connected to a physical switch. I have attached an image (Figure 1) illustrating the physical layout of my setup. My controller had the following configuration: { Two interface (eth0 and eth1) eth0: 10.42.0.1 with netmask 24 eth1: No IP assignment } My compute had the following configuration: { 5 interfaces (eth0, eth1, eth2, eth3, IPMI) eth1: No IP assignment and is connected to switch (MAC: 6F:F1:34:E9:01:29) IPMI: 10.42.0.100 connected to switch } In my globals.yml file, I have the following configuration: { openstack_release: "2025.2" # Flamingo kolla_internal_vip_address: "10.42.0.1" docker_configure_for_zun: true containerd_configure_for_zun: true containerd_grpc_gid: 42463 enable_openstack_core: true enable_haproxy: false enable_cinder: false enable_etcd: true enable_fluentd: true enable_ironic: true enable_kuryr: true enable_magnum: true enable_zun: true ironic_dnsmasq_dhcp_ranges: - range: "10.42.0.5,10.42.0.200" ironic_dnsmasq_boot_file: "pxelinux.0" ironic_cleaning_network: "public1" ironic_dnsmasq_default_gateway: "10.42.0.1" ironic_inspector_kernel_cmdline_extras: ['ipa-lldp-timeout=90.0', 'ipa-collect-lldp=1'] } After completing the deployment, I verified that all the required services are running as docker containers. Immediately afterward, I executed the necessary command to generate the admin credentials, which allows me to use the OpenStack client. 1. $pip install python-openstackclient -c https://releases.openstack.org/constraints/upper/master 2. $kolla-ansible post-deploy 3. $/path/to/venv/share/kolla-ansible/init-runonce After running the command, the following baseline was created. 1. Two network (public1 and demo-net), where public is a flat network 2. cirros image file 3. flavors After that, I uploaded a working kernel, initramfs, and ISO image to OpenStack. I verified that these images were functioning correctly by successfully launching an instance. Next, during the node enrollment process, I ran the following command to enroll my baremetal node. 1. $openstack flavor create --ram 32768 --vcpu 16 --disk 120 baremetal 2. $openstack flavor set --property resources:CUSTOM_IRONIC=1 baremetal 3. $openstack flavor set --property resources:VCPU=0 baremetal 4. $openstack flavor set --property resources:MEMORY_MB=0 baremetal 5. $openstack flavor set --property resources:DISK_GB=0 baremetal 6. $openstack baremetal node create --driver ipmi --deploy-interface direct --driver-info ipmi_username=<IPMI_usernmae> --driver-info ipmi_password=<IPMI_password> --driver-info ipmi_address=10.42.0.100 --driver-info deploy_kernel=<kernel uploaded> --driver-info deploy_ramdisk=<initramfs uploaded> --property local_gb=20 --resource-class baremetal --name My_node After enrolling the node as described above, and since I do not have an ironic Inspector setup, I manually created a port for the enrolled node using the MAC address 6F:F1:34:E9:01:29, which corresponds to the LAN interface. At this point, I am unsure how to proceed with booting the desired image onto the bare-metal host. I would greatly appreciate any guidance on the next steps required to deploy the image to the machine. Best, Vincent

1 0

[nova][meeting] Reserving time for bug scrubbing
by René Ribaud 19 Feb '26

19 Feb '26

Hi everyone, First of all, apologies for the lack of regular updates over the past few months. I haven’t managed to find the time and energy recently, but I’m trying to get back to a more regular rhythm. For the next meeting, I’d like us to explicitly reserve 10 to 15 minutes for bug scrubbing and avoid skipping it. To make this possible, I’ll adjust the agenda accordingly so that this time is clearly allocated. For those volunteering for bug scrubbing: if you have questions about specific bugs, please try to prepare them in advance and, if possible, add them to the agenda document under the Bug Scrubbing section. This should help us make that time more efficient and focused upfront. Thanks everyone, and see you at the meeting. Cheers, René

1 0

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

18 Feb '26

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.2/…

1 0