April 2025 - openstack-discuss - lists.openstack.org

OpenInfra Days Korea 2025 발표자 모집 안내
by Seongsoo Cho 14 Apr '25

14 Apr '25

안녕하세요 오픈인프라 한국 사용자모임 대표 조성수입니다. OpenInfra Days Korea 2025 발표자 모집이 시작되어 공지합니다. 미래를 여는 열쇠, 오픈인프라 ( Open Infrastructure, the Key to the Future ) 최근 클라우드 시장의 다양한 변화와 함께 오픈스택과 오픈인프라의 열기가 다시 뜨거워지고 있습니다. 특히 AI, HPC, 5G와 같은 떠오르는 첨단 기술들의 뒤에는 그 모든 가능성을 현실로 만드는 기반, 오픈인프라가 있습니다. 유연하고 확장 가능한 오픈인프라는 변화하는 기술 흐름에 민첩하게 대응하며 AI와 같은 고도화된 기술이 안정적으로 작동할 수 있도록 뒷받침합니다. 화려한 기술의 이면에서, 미래를 향한 문을 열고 있는 진짜 열쇠는 오픈인프라입니다. 지금 이 순간에도, 오픈인프라는 기술의 가능성을 넓히고, 세상을 연결하며, 더 나은 내일을 만들어가고 있습니다. OpenInfra Days Korea 2025에서 미래를 여는 열쇠를 함께 제안하고 함께 만들어보시기 바랍니다. 우리 손으로 기술의 내일을 열어가는 여정에 발표자 여러분들을 초대합니다 행사 일시 : 2025년 8월 26일 (화) 장소 : 서울 aT센터 발표자 모집 일정 : 4월 14일 (월) ~ 6월 15일 (일) 발표자 선정 안내 : 6월 30일 (월) 발표 시간 : 30분 문의 : program(a)openinfradays.kr 지원하러 가기 : https://2025.openinfradays.kr 이후 모든 공지는 https://forum.openinfra-kr.org 의 공지 게시판을 참고해주시기 바랍니다. -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

1 1

[ironic][networking][ops] PTG - Networking cases in Ironic
by Iury Gregory 11 Apr '25

11 Apr '25

Greetings everyone, During this week's PTG, we discussed networking aspects and the challenges we've encountered getting everyone on the same page. Ultimately, our biggest challenge is competing needs *and* requirements. The best way to describe the challenge is as a giant venn diagram where some interests overlap such that there are logical relationships and paths forward which can be drawn. But then there are also broadly useful themes to discuss, and requirements visit which then can also cloud the discussion. At the end of the day, the challenge is not to boil the ocean, but to focus on the distinct cases while also maybe draw the appropriate boundaries to defer specific items or have the necessary plan or idea of a plan in our back pocket before proceeding forward. So we tried bucketing in the form of hands raised during the PTG[0] to begin to give us some initial data points in an unscientific model of +1s. - Standalone operators who need non-neutron networking (mvp: tag/untag pots): +6 - Neutron Integrated Operators who are just using switches and need better existing ML2 plugin support: +3 - 3rd party SDN integration (w/neutron): +2 - Ironic additional capabilities at the front-end (dynamic portgroup assembly/weightable scheduling of specific ports): +7 If you have specific interest in any of these buckets, please reach out to Ironic contributors by replying to this mailing list post, messaging us on IRC, or even leaving some additional comments on our etherpad[0] from the PTG. That being said, the challenge is sort of how to get started and begin to make velocity. Consensus at the PTG was to sort of take a "two specific focus areas" approach and allow sub-teams to self organize. The key aspect is to get both subteams to talk to each other on a regular basis to ensure there is any coss-collaboration, reviews, and other overall awareness is highlighted for the purposes of collaboration. Discussion has also yielded that there is some consensus in trying to keep that sync as a higher bandwidth video call. Thoughts? - The Ironic Team [0]: https://etherpad.opendev.org/p/ironic-ptg-april-2025 -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic Core* *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[release] Release countdown for week R-24
by Thierry Carrez 11 Apr '25

11 Apr '25

Welcome back to the release countdown emails! These will be sent at major points in the 2025.2 "Flamingo" development cycle, which should conclude with a final release on October 1st, 2025. Development Focus ----------------- At this stage in the release cycle, focus should be on planning the 2025.2 "Flamingo" development cycle, assessing Flamingo community goals and approving Flamingo specs. General Information ------------------- The 2025.2 "Flamingo" cycle is a standard 26-week development cycle. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/flamingo/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.1 Epoxy release are continued in 2025.2 Flamingo with a similar release model. Upcoming Deadlines & Dates -------------------------- Flamingo-1 milestone: May 15, 2025 -- Thierry Carrez (ttx)

1 0

[octavia] Purging ERROR'ed amphora and load balancers stuck in transitional states
by Paul Browne 11 Apr '25

11 Apr '25

Hello Octavia users, For a while I've been trying to find a systematic way to remove Octavia LBs+Amphora that have become stuck in ERROR or transitional PENDING_* states ; $ openstack loadbalancer amphora list -f value | grep ERROR a2323f14-3aaa-418a-8249-111aaa9c21fe 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe ERROR MASTER 10.8.0.242 192.168.3.247 e5b236ba-e7ee-4ed7-9f58-57ce7a408489 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe ERROR BACKUP 10.8.0.190 192.168.3.247 6b556f28-93c9-49dd-b6ee-4379288e7957 d5e402fe-2c4b-49af-a700-532cb408cee5 ERROR MASTER 10.8.0.39 192.168.3.126 c669db5d-8686-4d5c-9e95-e02030b34301 d5e402fe-2c4b-49af-a700-532cb408cee5 ERROR BACKUP 10.8.0.174 192.168.3.126 $ openstack loadbalancer list -f value | grep -vi active 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe k8s-clusterapi-cluster-default-ci-6386871107-kube-upgrade-kubeapi 3a06571936a0424bb40bc5c672c4ccb1 192.168.3.247 PENDING_UPDATE amphora d5e402fe-2c4b-49af-a700-532cb408cee5 k8s-clusterapi-cluster-default-ci-6386871107-latest-kubeapi 3a06571936a0424bb40bc5c672c4ccb1 192.168.3.126 PENDING_DELETE amphora These resources are marked immutable and so cannot be failed over or deleted; $ openstack loadbalancer amphora failover a2323f14-3aaa-418a-8249-111aaa9c21fe Load Balancer 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe is immutable and cannot be updated. (HTTP 409) (Request-ID: req-6e66c4e8-c3d3-4549-a03c-367017c8c8b3) $ openstack loadbalancer failover 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe Invalid state PENDING_UPDATE of loadbalancer resource 1fa7bd54-f60c-420c-94f3-d4c02f03d4fe (HTTP 409) (Request-ID: req-84b44212-e7a8-4101-a16f-18c774c0577e) The backing Nova instances for these Amphora do seem to exist and be in good working order. Is there any API way to purge these out of Octavia's service state, or would (very careful) DB hackery be required here? Many thanks, Paul Browne ******************* Paul Browne Research Computing Platforms University Information Services Roger Needham Building JJ Thompson Avenue University of Cambridge Cambridge United Kingdom E-Mail: pfb29(a)cam.ac.uk<mailto:pfb29@cam.ac.uk> Tel: 0044-1223-746548 *******************

4 6

Bug deputy week 15 (April 7 - April 11)
by Sahid Orentino Ferdjaoui 11 Apr '25

11 Apr '25

Hello Guys, Here is a quick summary of Neutron related bugs this week == neutron-server error with ml2_distributed_port_bindings https://bugs.launchpad.net/neutron/+bug/2106374/ Status: LOW This issue appears to be related to tenant network/database handling. It throws an unexpected database exception which ideally should be handled more gracefully. Possibly a low-hanging fruit, that is said more investigation may be needed to understand the root cause. == [ovn-octavia-provider] Loadbalancer member list show operating status as ONLINE when member is created for a SHUTOFF state vm https://bugs.launchpad.net/neutron/+bug/2106357/ Status: LOW This seems to be a corner case where a stopped VM can be added to a load balancer, and it incorrectly appears as ONLINE. Unfortunately, I didn’t get the chance to reproduce it this week, apologies for that. == ovn-sb leader constantly changing https://bugs.launchpad.net/neutron/+bug/2106690/ Status: INCOMPLETE but reported is active and will share more detail soon Seem like point of instability with OVN SB database leader election. Waiting for more details. == [OVN] No network type availability zone https://bugs.launchpad.net/neutron/+bug/2106719/ Status: NEW This one may require someone with better picture of ML2/OVN and AZ to properly evaluate and move forward. == after running ``os-nova-install.yml`` lost instances connectivity https://bugs.launchpad.net/neutron/+bug/2106793 Status: INCOMPLETE at that point The issue seems to occur after a Nova restart, where instances lose network connectivity. Needs more info and confirmation. == Unable to enable/disable src_nat per external gateway https://bugs.launchpad.net/neutron/+bug/2106776 Status: TRIAGED This is related to OVN and occurs in scenarios involving multiple external gateways. == Have a good day! I unfortunately wont be available for driver meeting. s.

1 0

Question about patch to fix problem
by Franck VEDEL (UGA) 10 Apr '25

10 Apr '25

Hello, A few days ago, I asked a question about applying a patch to resolve a problem in my OpenStack environment. I didn't get a response. My question was probably stupid and not appropriate for this list. I apologize. Having to resolve this problem, I searched high and low using search engines. It seems that the solution, with kolla-ansible, is to upgrade to Epoxy, which takes the patch into account. Since this update could cause other problems, I don't want to do it for the moment. Is there another solution? Is it possible to modify the code (it's simply a line to modify in a file (https://review.opendev.org/c/openstack/horizon/+/942946)) in the two Horizon containers in my cluster? I'm really sorry if this is a stupid question, but I've been searching and can't find a method for applying these patches. Franck

5 8

[kolla] IRC meeting cancelled - 9-th of April 2025
by Bartosz Bezak 10 Apr '25

10 Apr '25

Hi, Kolla IRC meeting today is cancelled due to ongoing Project Teams Gathering (PTG) this week. Best regards, Bartosz Bezak

2 3

[octavia] Point releases
by Mikhail Okhrimenko 10 Apr '25

10 Apr '25

Hello community! We found that the latest octavia bobcat release packages for different OS like Rocky Linux 9, Debian 12, Ubuntu 22.04 do not contain the latest bug fixes from the release notes https://docs.openstack.org/releasenotes/octavia/2023.2.html of version 13.0.0-37. And there is no tag with these fixes in the octavia repository https://github.com/openstack/octavia/tags. So could you please create a point release in the octavia repository so that we can build packages with these changes. We also noticed the same situation with the release versions of caracal and dalmatian.

4 3

[nova][NFS] Changing disk permission on reboot, permission denied
by Nell Jerram 10 Apr '25

10 Apr '25

Hi; I'm seeing a problem with a hard reboot operation, when /var/lib/nova/instances for the relevant compute node is on an NFS share exported from another compute node. I'm hoping someone here might be able to point to where to debug this next. 3 compute nodes: A, B and C. A exports its /var/lib/nova/instances over NFS v4. B and C mount that at /var/lib/nova/instances. (This is the kind of setup that I understand to be required for live migration to be possible.) If I create a VM on A, wait for it to be ACTIVE, then `nova reboot --hard testvm1`, it's fine, i.e. it reboots and returns to ACTIVE state. If I create a VM on B, wait for it to be ACTIVE, then `nova reboot --hard testvm2`, it goes permanently into ERROR state. The Nova compute log has Stderr: "qemu-img: Could not open '/var/lib/nova/instances/02bf258b-41bc-451a-9d3c-af6741c6060f/disk': Could not open '/var/lib/nova/instances/02bf258b-41bc-451a-9d3c-af6741c6060f/disk': Permission denied\n": nova.exception.InvalidDiskInfo: Disk info file is invalid: qemu-img failed to execute on /var/lib/nova/instances/02bf258b-41bc-451a-9d3c-af6741c6060f/disk : Unexpected error while running command. and the ownership on that file is in fact now: -rw-r----- 1 root root 29491200 Apr 7 18:27 disk Before the reboot operation it was: -rw-r----- 1 libvirt-qemu kvm 29491200 Apr 7 18:25 disk There isn't a similar ownership change when rebooting a VM on node A, so presumably this is something to do with NFS being involved. But I believe I've followed standard NFS setup advice, and my user and group IDs are the same on all compute nodes: $ getent group nova nova:x:1003:libvirt-qemu $ getent passwd nova nova:x:1002:1003::/home/nova:/bin/bash $ getent passwd libvirt-qemu libvirt-qemu:x:64055:109:Libvirt Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin $ getent group kvm kvm:x:109:nova Any clues on how to debug or fix this next? Many thanks - Nell

3 9

Re: [openstack-magnum ui] Cannot choose an external network ID when creating a cluster template
by Eugen Block 10 Apr '25

10 Apr '25

Please don't drop the list from your responses. Zitat von Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com>: > Hello, They r different, > I check and see this happen because horizon switched to SDK > > https://github.com/openstack/horizon/commit/56f0e2685e2692467442d5be846b863… > > and Magnum-UI still keep old > > https://github.com/openstack/magnum-ui/blob/master/magnum_ui/static/dashboa… > > Thank you for replying to me. > > Nguyen Huu Khoi > > > On Thu, Apr 10, 2025 at 5:11 PM Eugen Block <eblock(a)nde.ag> wrote: > >> Could it be this bug? >> >> https://bugs.launchpad.net/horizon/+bug/2077329 >> >> Zitat von Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com>: >> >> > Hello, When I create a cluster template, I cannot choose an external >> > network ID, it disappears from horizon. >> > My env: >> > >> > Ubuntu 22.04 >> > Openstack 2024.2 >> > >> > Thank you. Regards >> > Nguyen Huu Khoi >> >> >> >>

2 1