- openstack-discuss - lists.openstack.org

Floating IP randomly becomes unreachable from external network (OSA AIO 30.0.2, Ubuntu 24.04)
by christophel＠silival.com 28 Jun '25

28 Jun '25

Hello, I’m currently running an OpenStack-Ansible All-In-One deployment (version 30.0.2) on Ubuntu 24.04. The environment hosts several virtual machines across multiple tenant networks. Each VM is assigned a floating IP from a public 172.x.x.x range, which allows access from the controller host and external clients. The issue From time to time, a VM becomes unreachable via its floating IP. The instance is still: Running normally. Reachable from other VMs on the same internal tenant network using its private IP (10.x.x.x). Associated with the same security groups and port configuration as before. This happens without any apparent trigger or configuration change. I can still ping and SSH to other VMs’ floating IPs, so the problem is isolated to one instance at a time. Workaround The only way I’ve found to restore external access is: Disassociate and delete the current floating IP. Allocate a new floating IP from the same pool. Associate it to the same VM port. Once the new floating IP is set, the VM becomes immediately reachable again. This has now occurred several times across different VMs. I’m concerned it will keep happening randomly. Question Has anyone encountered similar behavior with floating IPs in an OpenStack-Ansible AIO setup? Is there a known root cause, or any specific logs or areas I should investigate? If this mailing list is not the right place for this type of question, I’d also appreciate guidance on where to report it or who to contact. Thanks in advance for your help, Christophe.

3 7

[openstack]Detach and Attach Openstack Instance interfaces wont work
by Nguyễn Hữu Khôi 27 Jun '25

27 Jun '25

Hello. It is not a problem from Openstack but I think it will impact to our users https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2115545 Nguyen Huu Khoi

1 0

[manila] Python-manilaclient functional tests hack-a-ton - Jun 30th - Jul 4th
by Carlos Silva 27 Jun '25

27 Jun '25

Hello zorillas and interested stackers, Our Flamingo hack-a-ton starts next Monday at 15:00 UTC. We've been closing the gaps on OSC for a while now, and we are getting close to wrap everything up prior to the removal of the manilaclient and fully focus on OSC. On this hack-a-ton, we will focus on adding more functional test coverage to the OSC commands. Hackathon Plan: * Task Assignments: participants are encouraged to create, claim, and edit Taiga cards for their chosen implementations. Recent additions can serve as inspiration. Please contact Carlos (carloss) to be added to the Taiga board. Additionally, please add yourself as a "watcher" to two other Taiga cards being implemented by others to serve as a code reviewer. * Code Submission Window: Code can be submitted between June 30th, 15:00 UTC, and July 4th, 15:00 UTC, to be considered part of this hackathon. * Kick-off Session: A one-hour kick-off session will be held on June 30th at 15:00 UTC. This session will cover environment setup and also how to implement and run tests in your environment. The doc was kindly prepared by Vida (vhari) and is already available [2] in case you'd like a headstart. * Mid-point Status Check: The Manila upstream weekly meeting hour will serve as a mid-point status check. [1] https://gist.github.com/silvacarloss/295ca27bc1d76aed6564ab05ebdea2c7 [2] https://docs.google.com/document/d/1n44DXYvn_HDvr-NIuL3k3SE_UxoH15swMn0zPbc… Looking forward to working with you! Regards, carloss

1 1

migrating to ovn
by Mario David 27 Jun '25

27 Jun '25

hi all after today's meetup I have compiled information/documentation about migrating to OVN here https://github.com/mariojmdavid/migrate-to-ovn feel free to check, comment, criticize, you can open issues or contribute the process is far from full bulletproof I have this openstack infra up and running in production, but there are a few points I am in doubt, and will need further discussion namely about the net namespace (I was used with ip netns exec qrouter.... on the nodes running the l3-agent), as well as how to properly configure SRIOV but will get there best Mario

1 0

Help Name the OpenStack 2026.1 "G" Release
by Allison Price 27 Jun '25

27 Jun '25

Hi everyone, It’s time to name the OpenStack 2026.1 “G” release. Below is a poll that will be open until this Friday, June 27 at 1700 UTC. Please submit your preferences and we will let you know once the winner has been identified. https://civs1.civs.us/cgi-bin/vote.pl?id=E_17c91bf2dbfe3a77&akey=d3d789cac3… Cheers, Allison

1 1

[release] Release countdown for week R-13, Jun 30 - Jul 04
by Elõd Illés 27 Jun '25

27 Jun '25

Development Focus ----------------- The Flamingo-2 milestone is next week, on July 3rd, 2025! 2025.2 Flamingo-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/flamingo/schedule.html for details. General Information ------------------- Libraries need to be released at least once per milestone period. The release team will soon propose releases for any library that has not been otherwise released since milestone-1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new '2025.2 Flamingo' deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables/flami… and need to have done a release by milestone-2. Changes proposing those deliverables for inclusion in 2025.2 Flamingo have been posted, please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in 2025.2 Flamingo, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Flamingo-2 Milestone: July 3rd, 2025 Előd Illés irc: elodilles @ #openstack-release

1 0

[neutron][os-ken] Bug on the BGP loop prevention
by anas.jouhdy＠gmail.com 27 Jun '25

27 Jun '25

Hi, As it is my first message here, do not hesitate to tell me if something is wrong with the ticket ! I think there is a bug in this file https://opendev.org/openstack/os-ken/src/branch/master/os_ken/services/prot… on the method "_is_looped_path_attrs" on line 1655. In the case we found a loop, we should return True instead of None. For example in my case, I have an Openstack BGP speaker that advertise correctly the reachable subnets in Openstack. The external peer (Cumulus switch in my case) re-advertise the IP prefix of the subnets to my Openstack BGP speaker when it learns them. This rightfully raise an error in the log thanks to this method "_is_looped_path_attrs" telling that the update coming from the external peer will be ignored as the local AS was found in the AS Path but after that, the debug log implies that the path was still added to the potential path that can reach the subnet. This then become an issue when we detach our subnet from the router, because only the local path will be removed and the route will not be withdrawn (because the new best path will be the "false" route learned back from Cumulus) Do not hesitate to ask for precision !

3 2

Ops Radio!
by Chris Morgan 27 Jun '25

27 Jun '25

We'll do another Ops Radio today at 13:00 UTC which is in about 20 minutes from now as I write. See https://etherpad.opendev.org/p/openstack_ops_radiohour "*What is "OpenStack Ops Radio Hour"? * A casual setting for operators, engineers, and contributors to come together, share knowledge, and collaborate on the complexities of managing and deploying OpenStack environments." -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[cinder] Volume to Image Upload with Multi-Store Backends (Cinder + Glance)
by Maximilian Stinsky-Damke 27 Jun '25

27 Jun '25

Greetings, I'm in the process of setting up a new OpenStack deployment where both Cinder and Glance are configured with multiple Ceph-based backends using the multi-store functionality. Basic operations (create, delete, snapshot, upload, etc.) work fine for each store in both services. However, I'm encountering issues when trying to upload a Cinder volume to Glance as an image in this setup. My understanding is that when the volume type does not include image_service:store_id, Cinder should upload the image to the default Glance store. However, in my case, this upload fails with the following error: ERROR oslo_messaging.rpc.server FileNotFoundError: [Errno 2] No such file or directory: '/etc/ceph/ceph.client.cinder.keyring' I'm having trouble understanding why Cinder is trying to access this particular keyring. Each of my Cinder backends has its own Ceph config and keyring pointing to the appropriate cluster, and everything else works correctly. Here are my specific questions: 1. Should Cinder not be uploading the volume to Glance via the API, without needing direct access to the Glance Ceph store? 2. If Cinder is expected to access the Glance backend directly (e.g., to optimize data movement), how does it determine which Ceph config and keyring to use? 3. Is there any documentation or configuration guidance available on how to tell Cinder which credentials to use when interacting with Glance stores? Any insights or pointers would be greatly appreciated. Best regards, Max

3 4

[Cinder][Nova] - Volume retype fails with libvirt error about active block job
by Karl Kloppenborg 26 Jun '25

26 Jun '25

Hi Cinder + Nova Teams. Live migrating between two storage backends, most VM’s move successfully, but we’re seeing several VM’s fail the retype with the following error: https://gist.github.com/inventionlabsSydney/137121e8a4772ea3562776c10f43371a Libvirt logs show the following: 2025-06-26 06:55:48.906+0000: 2509009: error : qemuDomainBlockJobAbort:13723 : invalid argument: disk sda does not have an active block job 2025-06-26 06:57:08.879+0000: 2509006: error : qemuDomainBlockJobAbort:13723 : invalid argument: disk sda does not have an active block job 2025-06-26 06:57:09.053+0000: 2509009: error : qemuDomainBlockJobAbort:13723 : invalid argument: disk sda does not have an active block job 2025-06-26 23:24:19.954+0000: 2509008: error : qemuDomainBlockJobAbort:13723 : invalid argument: disk sda does not have an active block job 2025-06-26 23:24:20.130+0000: 2509009: error : qemuDomainBlockJobAbort:13723 : invalid argument: disk sda does not have an active block job Has anyone else encountered similar to this, we cannot seem to find any difference between VM’s that are working and VM’s that fail this retype. Openstack details: Version Epoxy. Compiled against library: libvirt 10.0.0 Using library: libvirt 10.0.0 Using API: QEMU 10.0.0 Running hypervisor: QEMU 8.2.2 Migration backends: From: Ceph. To: PowerFlex. Karl Kloppenborg Chief Technology Officer m: +61 437 239 565 resetdata.com<https://resetdata.com/> [cid:reset_69557fc2-1d63-4932-b5fd-93bd4f39ca7b.png] ResetData supports Mandatory Client Related Financial Disclosures – Scope 3 Emissions Reporting For more information on the phasing of these requirements for business please visit; https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…<https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…> This email transmission is intended only for the addressee / person responsible for delivery of the message to such person and may contain confidential or privileged information. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you, nor may you use, review, disclose, disseminate or copy any information contained in or attached to it. Whilst this email has been checked for viruses, the sender does not warrant that any attachments are free from viruses or other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments. If you received this e-mail in error please delete it and any attachments and kindly notify us by immediately sending an email to contact(a)resetdata.com.au<mailto:contact@resetdata.com.au>

1 0