openstack-discuss

openstack-discuss@lists.openstack.org

August 2025

  • 80 participants
  • 93 discussions

10 Feb '26
Hello.I am deploying OpenStack 2025.1 with Kolla-Ansible 2025.1 (master branch)using the latest images. However, when I created a RabbitMQ(4.0.x) clusterwith 3 nodes, it took too long—around 12 minutes(it stucked at DB: virginnode -> run peer discovery). I then changed the images to RabbitMQ version3.13.7, and it worked well.My OS: Ubuntu 24.01Nguyen Huu Khoi
2 2
0 0
[openstack][octavia]Resize a Load Balancer
by Nguyễn Hữu Khôi 27 Jan '26

27 Jan '26
Hello.I see that patchhttps://review.opendev.org/c/openstack/octavia/+/890215Could I ask why we cannot merge it?Nguyen Huu Khoi
3 6
0 0
The tl;dr on this is that I'm opening a broad community discussionon how we can, collectively through improved communication, betterbring together our established contributors with casual andprospective contributors who struggle to find successful patterns ofcontribution, so that we might all support each other in order tobenefit OpenStack as a whole. Read on for details...OpenStack's TC has requested that foundation staff, when inconversation with representatives of member organizations, encourageparticipation in the project and collect feedback on any relatedchallenges those organizations encounter in their attempts to do so.In order to better understand the feedback and brainstorm achievablerecommendations for the broader community[*], Community Managers onthe foundation staff started to work with a small focus group ofestablished contributors with a solid understanding of whatsuccessful patterns of contribution look like. It also came to lightthat established contributors experience many of the same sorts ofchallenges, even more so if they don't have the luxury of focusingfull-time upstream, and so success often comes down to knowing howto effectively navigate those challenges. The community's goal withthis exercise is to improve everyone's experience, and your help isneeded to do that!The most common themes reported by those struggling to contributeare not related to tooling or workflow confusion, but instead seemto come down to basic communication challenges. Ideas so far toaddress these gaps include:* Review bandwidth - Ensure contributors and companies understand the importance and benefits of code review - Incentivize and credit meaningful "+1" reviews more - Understand that the volume of changes and limited reviewer bandwidth often means proposals aren't reviewed quickly (or at all), and their proponents may need some additional tenacity and engagement with the team to get their work noticed - Utilize "review dashboards" as a way to find stale changes which have fallen through the cracks* Review strategy and etiquette - Be clear about the meaning of votes on changes, especially negative ones, and set explicit timelines for things like "procedural -2" or WIP blocks when their approval needs to be delayed - Focus on comments and requests that affect whether or not the change can be merged after the fixes are submitted, rather than requesting trivial adjustments to an unsuitable change which has more fundamental problems - Reciprocate with reviews of changes from new reviewers you see leaving insubstantial reviews, demonstrating to them what deeper and more meaningful reviewing looks like* Mentoring newcomers - Established contributors with sufficient bandwidth can help mentoring newcomers, potential core reviewers and new leaders - Mentoring can happen as part of internship programs as well as by helping newcomers determined to become active contributors; both ways should be embraced and utilizedWhat challenges are you facing? And, how would you improve them?Two weeks from now, we'll have a forum session at the OpenInfraSummit Asia in Suwon[**] where our community can refine thesepossible approaches and integrate others, as well as bring attentionto them and promote their application. I've also proposed a similarforum session for OpenInfra Days North America in Indianapolis amonth after that, where we can hopefully continue this conversation.The goal for this multi-stage effort is to improve the contributionexperience for established participants, casual contributors andnewcomers alike. While it's easy to jump to blaming in thesesituations, it will be far more productive if we can focus on thechallenges and experiences that we would each like to remove orimprove for ourselves and others in our community. As we find waystogether to improve our efficiency, we can reduce the load on allcontributors and lower the barriers for people to join andparticipate.[*]https://etherpad.opendev.org/p/r.2205024e55689bccb82c20c960853cb5[**]https://2024.openinfraasia.org/a/schedule#view=calendar&title=Bridging%20th…-- Jeremy Stanley
2 14
0 0
Hi OpenStack Community,I am currently facing an issue with the Load Balancer (Octavia) service in my OpenStack deployment and would appreciate your guidance or suggestions on how to troubleshoot and resolve it.Environment Details:OpenStack Version: 2023.1 (Antelope)Operating System: Ubuntu 22.04Octavia Backend: AmphoraNetwork Type: VXLANDeployment Tool: Kolla Ansible Issue Summary:After creating a Load Balancer, the Amphora instance is successfully launched. However, approximately 18 minutes later, the Load Balancer transitions to an ERROR state.Error Observed:octavia.common.exceptions.ComputeWaitTimeoutException: Waiting for compute id a222527f-8336-4fb1-8e9e-0e3ac6e8d580 to go active timeout.octavia.amphorae.driver_exceptions.exceptions.AmpConnectionRetry: Could not connect to amphora, exception caught:HTTPSConnectionPool(host='192.168.200.247', port=9443): Max retries exceeded with url: // (Caused by NewConnectionError: Failed to establish a new connection: [Errno 113] No route to host)What I’ve Tried:Created a VXLAN-based internal network:openstack subnet create --network octavia-mgmt-net --subnet-range 192.168.200.0/24 octavia-mgmt-subnetopenstack router create octavia-routeropenstack router add subnet octavia-router octavia-mgmt-subnetopenstack router set octavia-router --external-gateway <public-network-id>Manually configured OVS interface:ovs-vsctl add-port br-int octavia-mgmt -- set interface octavia-mgmt type=internalip addr add 192.168.200.1/24 dev octavia-mgmtip link set octavia-mgmt upSecurity groups are open (allowing all ingress and egress).Verified OVS bridge setup – interface appears correctly on br-int.Behavior Noticed:Amphora instance gets created but fails to communicate with the controller after a while,so health checks fails.The controller cannot reach the Amphora management IP (192.168.200.x).Logs show heartbeat/connection issues (No route to host, timeouts).Request for Help:I would appreciate any of the following:Suggestions to verify if the management network is properly routed from controller to Amphora.Best practices for setting up the Octavia management network using VXLAN.Troubleshooting steps for verifying health manager connectivity to Amphora.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."
4 3
0 0
LXB Removal and OVN migration
by Ricardo Cano 09 Nov '25

09 Nov '25
Hello openstack-discuss,With the removal of the linuxbridge mechanism driver, has anyonesuccessfully completed an in-place migrationfrom LinuxBridge to OVN?I did come across thishttps://www.jimmdenton.com/migrating-lxb-to-ovn/ and that looks goodas a one-shoit while biting the bullet and taking a full outage.However, I was wondering if it was possible to run lxb and ovnside-by-side and cut them over, say one network at a time.This particular deployment was stood up using openstack-ansible backin the rocky days (now running antelope) and it appears that openstackansible's default was lxb up until Zed.Any suggestions or recommendations on the best path forward?Also, will the dynamic routing agent work with ovn?
4 3
0 0
Hello i'm testing using Openstack-helm to install all componentbut after the installation complete i can't upload the OS image through both openstack CLI or Horizon it stuck at Queueingand when i checking Glance Api logit shows2024-11-07 07:31:19.362 7 INFO glance.api.v2.image_data [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token.2024-11-07 07:31:19.400 7 ERROR glance.api.v2.image_data [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Failed to upload image data due to internal error: OSError: unable to receive chunked part2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Caught error: unable to receive chunked part: OSError: unable to receive chunked part2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi Traceback (most recent call last):2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1302, in __call__2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi action_result = self.dispatch(self.controller, action,2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1345, in dispatch2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return method(*args, **kwargs)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 415, in wrapped2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return func(self, req, *args, **kwargs)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/api/v2/image_data.py", line 299, in upload2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi with excutils.save_and_reraise_exception():2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 227, in __exit__2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.force_reraise()2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 200, in force_reraise2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise self.value2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/api/v2/image_data.py", line 162, in upload2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi image.set_data(data, size, backend=backend)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/notifier.py", line 492, in set_data2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi with excutils.save_and_reraise_exception():2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 227, in __exit__2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.force_reraise()2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 200, in force_reraise2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise self.value2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/notifier.py", line 443, in set_data2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.repo.set_data(data, size, backend=backend,2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/quota/__init__.py", line 322, in set_data2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.image.set_data(data, size=size, backend=backend,2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/location.py", line 596, in set_data2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self._upload_to_store(data, verifier, backend, size)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/location.py", line 487, in _upload_to_store2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi multihash, loc_meta) = self.store_api.add_with_multihash(2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/multi_backend.py", line 397, in add_with_multihash2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return store_add_to_backend_with_multihash(2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/multi_backend.py", line 479, in store_add_to_backend_with_multihash2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi (location, size, checksum, multihash, metadata) = store.add(2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/driver.py", line 294, in add_adapter2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi metadata_dict) = store_add_fun(*args, **kwargs)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/capabilities.py", line 176, in op_checker2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return store_op_fun(store, *args, **kwargs)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/_drivers/filesystem.py", line 764, in add2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise errors.get(e.errno, e)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/_drivers/filesystem.py", line 746, in add2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi for buf in utils.chunkreadable(image_file,2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/common/utils.py", line 73, in chunkiter2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi chunk = fp.read(chunk_size)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 294, in read2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi result = self.data.read(i)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 121, in readfn2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi result = fd.read(*args)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/format_inspector.py", line 956, in read2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi chunk = self._source.read(size)2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1045, in read2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi data = uwsgi.chunked_read()2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi OSError: unable to receive chunked part2024-11-07 07:31:19.426 7 ERROR glance.common.wsgiCeph Cluster Status:NAME DATADIRHOSTPATH MONCOUNT AGE PHASE MESSAGE HEALTH EXTERNAL FSIDceph /var/lib/rook 3 82m Ready Cluster created successfully HEALTH_OK 5cf8b9bb-13e1-4c31-b47d-9e7d92c3c05dCeph osd status:ID CLASS WEIGHT REWEIGHT SIZE RAW USE DATA OMAP META AVAIL %USE VAR PGS STATUS TYPE NAME-1 0.35156 - 360 GiB 3.3 GiB 493 MiB 0 B 2.8 GiB 357 GiB 0.91 1.00 - root default-5 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 964 MiB 119 GiB 0.92 1.01 - host instance-lu-1 2 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 964 MiB 119 GiB 0.92 1.01 195 up osd.2-3 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 - host instance-lu-2 0 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 195 up osd.0-7 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 - host instance-lu-3 1 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 197 up osd.1 TOTAL 360 GiB 3.3 GiB 493 MiB 0 B 2.8 GiB 357 GiB 0.91MIN/MAX VAR: 1.00/1.01 STDDEV: 0.01now i'm able to create Empty Volume using horizon(can't create volume using default cirros image )and i can start an Instance without volume and mount the empty volume in(Ceph also can detect when i use that volume)is there something i need to set when starting glance?because i'm following the Openstack-helm installation document to install openstack with helm
5 8
3 0

29 Oct '25
Hello Koller.I want to ask if we can overwrite config for a group of nodes. For example,compute01 >> compute10 will have the same nova configurationcompute11 >> compute20 will have the same nova configuration.It will be very nice if we support this way.Thank you. RegardsNguyen Huu Khoi
4 7
0 0
Hey folks,I wanted to raise attention to a relatively old issue, which has had apatch around since January [1]. Basically a regression [2] was introducedand backported to 2024.1 as part of an attempt to fix QManager execution incontainers.However, it does not account for the possibility of os.getpgrp()returning 0 in some edge cases, which makes, for instance, impossible tosync database for Nova during upgrades, if QManager is used.Thus I'm asking to kindly review the [1] as it appears to be a blocker forsome upgrades involving affected versions of oslo.messaging. I have notspotted this patch right away, so I proposed an alternative [3], but I'mhappy to abandon it in favor of [1].Thanks in advance for upcoming reviews :)[1]https://review.opendev.org/c/openstack/oslo.messaging/+/939540[2]https://review.opendev.org/c/openstack/oslo.messaging/+/928034[3]https://review.opendev.org/c/openstack/oslo.messaging/+/958528
2 3
0 0
[openstack][nova]qemu system wont release memory
by Nguyễn Hữu Khôi 29 Sep '25

29 Sep '25
Hello. I have an OpenStack instance that was using 14GB out of 16GB of memory.Later, when it was using only 4GB, I checked the QEMU process on thecompute node, and it was still consuming 14GB, this means memory isn'treleased when usage decreases. Do we have solutions for this? I use Ubuntu 24.04 instances.Nguyen Huu Khoi
2 4
0 0

29 Sep '25
Hi all,Following on the good session we had last time discussing migrating out of LinuxBridge between operators, it was proposed to meet again in June.To find a good time slot, please respond to the following survey:https://newdle.cern.ch/newdle/TtbH8DbvFor reference, the notes from last meeting:https://etherpad.opendev.org/p/neutron-lb-ovn-migrationBest,Daniel FailingCERN Cloud Infrastructure
2 3
0 0