October 2025 - openstack-discuss - lists.openstack.org

How to set admin password during server create but not using user-data file
by Ahmad Milad Pour 13 Oct '25

13 Oct '25

Hello there, This is how I download an ubuntu cloud image: wget -c https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.i… -O ~/noble-server-cloudimg-amd64.img virt-customize -a noble-server-cloudimg-amd64.img \ --timezone Asia/Tehran \ --root-password password:q \ --run-command 'sed -i "s/^disable_root.*/disable_root: false/" /etc/cloud/cloud.cfg' \ --run-command 'grep -q "^ssh_pwauth:" /etc/cloud/cloud.cfg && sed -i "s/^ssh_pwauth:.*/ssh_pwauth: true/" /etc/cloud/cloud.cfg || echo "ssh_pwauth: true" >> /etc/cloud/cloud.cfg' \ --run-command 'printf "PasswordAuthentication yes\nPermitRootLogin yes\n" > /etc/ssh/sshd_config.d/99-allow-root.conf' \ --run-command "sed -e 's/^[# ]*PasswordAuthentication.*/PasswordAuthentication yes/g' -i /etc/ssh/sshd_config || true" \ --run-command "sed -e 's/^[# ]*PermitRootLogin.*/PermitRootLogin yes/g' -i /etc/ssh/sshd_config || true" \ --run-command 'systemctl enable ssh || systemctl enable sshd' \ --run-command 'systemctl disable systemd-networkd-wait-online.service' openstack image create --file ~/noble-server-cloudimg-amd64.img --disk-format qcow2 --container-format bare --public --property os_distro=ubuntu --property hw_qemu_guest_agent=yes "Ubuntu 24" || true rm -f noble-server-cloudimg-amd64.img cat <<EOF > /root/userdata.txt #cloud-config chpasswd: list: | root:q expire: False ssh_pwauth: True cmd: - systemctl disable systemd-networkd-wait-online.service EOF openstack server create --image "Ubuntu 24" --flavor first --network public_network --config-drive True ahmad --password 'ahmad' This is how I create image. I'm going to find a way if possible, to set the admin password during the "server create". Currently the root login is only possible with password "q". The "ahmad" is not working. I know I can change it via user-data file (I intentionally added there but not using it), but the question is can I set the password during the server create? I tried to use "virt-customize --install qemu-guest-agent", but the virt-customize has no network, so no installation. I also know I can do this: 1. create server 2. do whatever I want (install guest agent, etc) 3. create snapshot 4. create server from that snapshot But the issue is it's not automatic (I should manually login to do the modification) and its size is much more than the cloud image. Like, from 500 megabytes which is cloud image, goes around 3 gigabytes which is the snapshot. Any ways to reach what I'm looking for? Or even any better ways to do that? Regards, Ahmad

1 0

[ovn][wallaby][migration] Live migration more than 10s switchover
by Kamil Madac 13 Oct '25

13 Oct '25

Hello community, We are running a Wallaby TripleO installation with OVN networking. During live migration, we’re experiencing a connectivity outage lasting between *10 and 40 seconds* on the provider network to which the migrating VM is connected. I don’t see any errors in the ovn-controller, nova, or neutron logs. Is this behavior normal for the Wallaby release? We don’t see this issue in our Kolla-Ansible deployment running OpenStack 2024.2. I found that OVN multi-chassis port bindings were not yet implemented in Wallaby, but still — more than 10 seconds of downtime during live migration seems excessive. Has anyone observed similar behavior with older OpenStack releases, or is there any way to tune or optimize the switchover to reduce the outage duration? Thanks for any advice. Best regards, Kamil

1 0

[horizon] Help review the patch https://review.opendev.org/c/openstack/horizon/+/961099
by Dong Ma 13 Oct '25

13 Oct '25

Hi, We’ve submitted a patch (https://review.opendev.org/c/openstack/horizon/+/961099) adding microversion support for Nova live migration. Appreciate any reviews from the core team so we can get it merged soon. Thanks, -- Dong Ma — vexxhost

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2026.1/R-24)
by Goutham Pacha Ravi 13 Oct '25

13 Oct '25

Hello Stackers, We're twenty-four weeks away from the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. In a couple of weeks, the community will be gathering to design and discuss features and bug fixes for this release [2]. PTLs and project liaisons are requested to finalize their project schedules for the PTG and strive to use the first two days solely for wider cross-project discussions. At the end of this week, a portion of our community will be participating in the OpenInfra Summit happening at the École Polytechnique Campus in Paris-Saclay, France [3]. There's a meet-and-greet session planned with the OpenStack Technical Committee on Sunday, October 19th starting at 17:05 UTC in the Becquerel room. If you're attending the summit, do try to add this to your calendar. During the past week, the TC didn't make any major governance updates. A few are currently undergoing community review. === Weekly Meeting === The last weekly meeting of the OpenStack TC occurred on October 7th, 2025 simultaneously over IRC [4] and video [5]. We had a small list of attendees and a short agenda. We noted that the governance changes to officially mark Venus and Vitrage as inactive are in progress. The retirement of Monasca is still held up, and the team is waiting for a response from a potential new maintainer. Discussions were held on the new APAC-friendly TC meeting slot, with the plan to review the poll results and schedule the first meeting shortly after the OpenStack Summit, likely on a monthly or bi-weekly cadence. I'll follow up with more details about this. We also discussed the need to refresh the TC Liaisons for several project teams (Freezer, Oslo, Release Management, and Requirements) and are seeking volunteers on the TC. We called for topics for the PTG. The TC will join project teams in analyzing the User Survey results [6]. The next meeting of the OpenStack Technical Committee will be hosted on OFTC's #openstack-tc channel on October 14th, 2025 at 1700 UTC. Please find the agenda for this meeting on the wiki [7]. I hope you're able to join us there. === Governance Proposals === ==== Merged ==== - Allow .gitignore in legacy repositories | https://review.opendev.org/c/openstack/governance/+/963867 - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 ==== Open For Review ==== - Mark Vitrage project-team inactive | https://review.opendev.org/c/openstack/governance/+/963227 - Mark Venus project-team inactive | https://review.opendev.org/c/openstack/governance/+/963228 - Retire ironic-inspector from bare metal program | https://review.opendev.org/c/openstack/governance/+/963470 - 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 === Upcoming Events === - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-22: OpenInfra Meetup, Jakarta Selatan: https://www.meetup.com/openinfraid/events/31140538 - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ - 2025-11-04: OpenInfra Board meeting: https://board.openinfra.org/ - 2025-11-15: Celebrating 15 years of OpenStack, Montréal - 2025-11-15: KCD+OpenInfra Days, Hangzhou: https://sessionize.com/kcd-hangzhou-and-oicd-2025/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) [1] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [2] OpenInfra Project Teams Gathering: https://ptg.openinfra.org/ [3] OpenInfra Summit: https://summit2025.openinfra.org/ [4] TC Meeting IRC Log, Oct 7th 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-10-07-17.01.html [5] TC Meeting Video Recording, Oct 7th 2025: https://youtu.be/s_j3LPg-f1M [6] OpenStack User Survey: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [7] TC Meeting Agenda, Oct 14th 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[glance] image upload fails "Unsupported Media Type", "Multiple formats detected: iso,gpt"
by Eugen Block 13 Oct '25

13 Oct '25

Good morning, after our recent upgrade to Epoxy we had troubles uploading images to Glance: openstack image create --disk-format raw --file .../opensuse/Leap-16.0-offline-installer-x86_64.install.iso --progress --public test-ebl [=============================>] 100% HttpException: 415: Client Error for url: http://controller.domain:9292/v2/images/e23d802e-d927-4f34-ae2d-1d6f54d6206…, Unsupported Media Type And in the logs this is reported: 2025-10-11 01:16:56.585 65675 ERROR glance.api.v2.image_data [None req-086ad005-a455-471a-bb0d-9dfe5e27eacf 89c5dcc8793d4867bae22d50e51e16b3 90c403f317ee47feb0dad58461e76fb1 - - default default] Multiple formats detected: iso,gpt: glance.common.exception.InvalidImageData: Multiple formats detected: iso,gpt This is the official openSUSE Leap 16 ISO file. For now I disabled the check by setting: [image_format] require_image_format_match = false The docs state that this is likely a bug: > Disabling this may be required in the case of false match (or > mismatch) issues, but those are bugs that should be filed and fixed. I tried a couple of different ISO files (Ubuntu, openSUSE, incl. older files), all fail with the same error. Uploading raw images seemed to work fine. ISOs are supported file formats according to the docs, could anyone shed some light on this? Thanks! Eugen

2 6

[neutron] Bug deputy Oct 6 - Oct 12
by Rodolfo Alonso Hernandez 13 Oct '25

13 Oct '25

Hello Neutrinos: This is the bug report from the last week (Oct 6 - Oct 12) High: * [VPNAAS] vpnaas AttributeError: 'dict' object has no attribute 'router' ( https://bugs.launchpad.net/neutron/+bug/2127169) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963493 * [VPNAAS] vpnaas no config update in ipsec.conf ( https://bugs.launchpad.net/neutron/+bug/2127166) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963490 * [VPNAAS] Libreswan config broken when used with new AEAD ciphers ( https://bugs.launchpad.net/neutron/+bug/2127159) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963489 * [VPNAAS] ovn-vpn-agent fails to delete vpn service ( https://bugs.launchpad.net/neutron/+bug/2127157) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963487 * OVN CI jobs on ironic are broken ( https://bugs.launchpad.net/neutron/+bug/2127038) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron/+/963390 (fixed). Medium: * ovn_dhcp4_global_options doesn't support keys with a list of values ( https://bugs.launchpad.net/neutron/+bug/2126923) Not assigned. Undecided: * Neutron not able to create external ports for virtual routers ( https://bugs.launchpad.net/neutron/+bug/2126913) Still deciding if this is a configuration issue. Regards.

1 0

Unable to create new instance while the computes are up
by Ahmad Milad Pour 13 Oct '25

13 Oct '25

Hello there, I asked the ChatGPT to help me to install the openstack on region, and to run a compute server. The ".sh" files are the installation. The "common_ask.sh" file is I run on both servers. The "region_ask.sh" is the file to install openstack and the region. The "compute_ask.sh" is the file to run the compute. The logs and errors are in the "region_details.txt" file. Would you please help me why the server I create has error and cannot be up? The way to create new instance is in the last lines of the "region_ask.sh" which is "openstack server create ...". Regards Ahmad

4 3

[tacker] Cancelling weekly IRC meeting
by Yasufumi Ogawa 12 Oct '25

12 Oct '25

Hi team, Due to a holiday and most of the core members aren't join, I'm cancelling tomorrow's meeting. Regards, Yasufumi

1 0

[OpenStack Ansible] [Deployment] Networking design
by holywine＠outlook.com 11 Oct '25

11 Oct '25

Hello, I am trying to build a minimum usable production-level cloud with OpenStack Ansible following online reference. The idea it shoud be able to scale up without radical change afterwards. Online reference: https://docs.openstack.org/project-deploy-guide/openstack-ansible/2025.1/ openstack-ansible version: stable/2025.1 Target hosts (Ubuntu 24.04LTS): 1) Infra1: Controller 1 + networking 2) Infra2: Controller 2 3) Compute 1: Compute 1 + storage 1 4) Compute 2: Compute 2 + storage 2 Deploy host: dev-host (Ubuntu 24.04LTS) Network: Each sever has two network adapter, say enp11s0f0 and enp11s0f1 (different server may have different port name, en0 and en1 for short). Public IP (en1) : Infra1 - 10.2.46.70/24, fixed IP permanently assigned by provider. Infra2, Compute 1, Compute 2 - 10.2.46.XX/24, dynamic IP temporary assigned for SW installation Private IP (en0): Infra1: 172.29.236.11/22, VLAN 10 172.29.240.11/22, VLAN 30 Infra2: 172.29.236.12/22, VLAN 10 172.29.240.12/22, VLAN 30 Compute 1: 172.29.236.13/22, VLAN 10 172.29.240.13/22, VLAN 30 172.29.244.13/22, VLAN 20 Compute 2: 172.29.236.14/22, VLAN 10 172.29.240.14/22, VLAN 30 172.29.244.14/22, VLAN 20 VLAN 10 - management network VLAN 30 - tunnel network VLAN 20 - storage network Target: Since only Infra1:en1 is available with fixed public IP, It would be the only Internet connection without any port bonding. What have been done: 1) All ordinary IPs and VLANs setting (as above Network part) - The settings are verified and working (verified by ping and curl) 2) user_variables.yml haproxy_keepalived_external_vip_cidr: "10.2.46.70/24" haproxy_keepalived_internal_vip_cidr: "172.29.236.11/22" haproxy_keepalived_external_interface: enp11s0f1 haproxy_keepalived_internal_interface: br-mgmt 3) openstack_user_config.yml internal_lb_vip_address: 172.29.236.11 external_lb_vip_address: 10.2.46.70 Based on experiences as network engineer previously and a lot of readings from books and online guidance esp. the OpenStack Ansible deployment reference, I understand there should/could be something extra to be done. Can anybody please give me a clue on what else to be done or it is enough to make it working? Sorry for disturbing if any but netwoking seems to be the most complicated part for OpenStack deployment. The online examples are hard to be comprehend and customized. One small example: Ubuntu seems to be promoting netplan, while the examples are all with /etc/network/interfaces file (difficult to adapte with Ubuntu24.04). Thanks a lot for help in advance!

2 4

[release] Release countdown for week R-24
by Thierry Carrez 10 Oct '25

10 Oct '25

Welcome back to the release countdown emails! These will be sent at major points in the 2026.1 "Gazpacho" development cycle, which should conclude with a final release on April 1st, 2026 (not a joke). Development Focus ----------------- At this stage in the release cycle, focus should be on planning the 2026.1 "Gazpacho" development cycle, assessing Gazpacho community goals and approving Gazpacho specs. General Information ------------------- The 2026.1 "Gazpacho" development cycle will be a classic 26-week-long cycle. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/gazpacho/schedule.html By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… By default, all your team deliverables from the 2025.2 "Flamingo" release are continued in 2026.1 "Gazpacho" with a similar release model. Upcoming Deadlines & Dates -------------------------- OpenInfra Summit Europe: October 17th-19th, 2025 OpenStack PTG (virtual): October 27th-31st, 2025 Gazpacho-1 milestone: November 13th, 2025 -- Thierry Carrez (ttx)

1 0