March 2025 - openstack-discuss - lists.openstack.org

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-1)
by Goutham Pacha Ravi 25 Mar '25

25 Mar '25

Hello Stackers, We're one week away from the coordinated release of OpenStack 2025.1 ("Epoxy") [1]. Project teams shipped release candidates over the past week and will keep these updated if any release-critical bugs are identified. Teams are also preparing for the virtual OpenInfra Project Teams Gathering (PTG) [2], which begins on April 7. OpenStack project teams are encouraged to schedule cross-project meetings during the first two days. The OpenStack Technical Committee will meet with contributors to chart out our tasks to aid the next release, 2025.2 "Flamingo." The TC sessions are scheduled at the beginning and end of the PTG. We hope to discuss governance, community goals, and other work affecting the entire community. Please find the etherpad of the OpenStack TC's discussions [3], and feel free to propose new topics! In the past week, the TC appointed its chair (me!) and vice-chair (Dmitriy Rabotyagov / noonedeadpunk). We thank the members of the TC and the community for their continued faith in our work. Additionally, a proposal has been made to change the Vulnerability Management Team's (VMT) work, which will affect all project teams [4]. The proposal aims to place all project teams under VMT's oversight. Your feedback on this proposal is welcome! === Weekly Meeting === The OpenStack TC met on OFTC's #openstack-tc channel for its weekly meeting on 2025-03-18 [5]. We began with a discussion around the former openstack-operators mailing list. This mailing list was merged with the openstack-discuss mailing list after extensive prior discussion. The TC received some feedback in recent months from operators who wished to revive a dedicated list for operator discussions. Some operators feel project maintainers don’t engage with their problems, and discussions now occur on other platforms. Mailing list engagement among operators is still present but could be improved. There will be an Operators Discussion at the PTG, and the TC will raise this concern to better understand operator feedback. The TC appreciated the work project teams did in conjunction with the release team to get release candidates posted across the board. We reviewed the state of the CI and welcomed the donation of cloud resources that aided in Zuul's scalability around this critical time of the release. The next meeting of the OpenStack Technical Committee is today, 2025-03-25. It will be held at 18:00 UTC in the #openstack-tc channel on OFTC. Please find the agenda on the meeting's wiki page [6]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== - Add 2025.2 TC chair and vice-chair | https://review.opendev.org/c/openstack/governance/+/944174 - Add separate freezer-api deliverable | https://review.opendev.org/c/openstack/governance/+/944781 ==== Open for Review ==== - [resolution] Extend scope of VMT to cover all project teams | https://review.opendev.org/c/openstack/governance/+/944817 - Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 === Upcoming Events === - 2025-04-01 - 2025-04-04: KubeCon+CloudNativeCon EU: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/ - 2025-04-02: OpenStack 2025.1 ("Epoxy") Release - 2025-04-03: OpenInfra LIVE - Epoxy release - 2025-04-08: OpenInfra Board Meeting: https://board.openinfra.org/ - 2025-04-07 - 2025-04-12: OpenInfra PTG Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] 2025.2 "Flamingo" PTG: https://openinfra.org/ptg/ [3] TC PTG Etherpad: https://etherpad.opendev.org/p/apr2025-ptg-os-tc [4] VMT proposal: https://review.opendev.org/c/openstack/governance/+/944817 [5] TC Meeting IRC Log 2025-03-18: https://meetings.opendev.org/meetings/tc/2025/tc.2025-03-18-18.00.log.html [6] TC Meeting Agenda, 2025-03-25: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Fwd: [Bug 2103448] Re: Extending `hosts` to also accept new `target_hosts` variable
by Dominic Dumrauf 24 Mar '25

24 Mar '25

Hi all, Could I interest someone in reviewing the *bifrost* - *bug* https://bugs.launchpad.net/bifrost/+bug/2103448 and its - *proposed solution* https://review.opendev.org/c/openstack/bifrost/+/944810 ? Many thanks and feel free to let me know how I can help. Cheers, Dominic ---------- Forwarded message --------- From: Afonne-CID <2103448(a)bugs.launchpad.net> Date: Wed, Mar 19, 2025 at 4:30 PM Subject: [Bug 2103448] Re: Extending `hosts` to also accept new `target_hosts` variable To: <dominic.dumrauf.git(a)gmail.com> Thanks for the bug and also proposing a change. You can get some eyes on your proposed change by asking about it in the #openstack-bifrost channel on IRC (if you haven't already). I personally think it LGTM. On the change, instead of "Bug #2103448: ", use 'Closes-Bug: #2103448' so that it directly references this report and gets automatically tracked and closed by the bot once resolved. ** Changed in: bifrost Status: New => Triaged ** Changed in: bifrost Importance: Undecided => Medium ** Changed in: bifrost Assignee: (unassigned) => Dominic Dumrauf (dumrauf) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/2103448 Title: Extending `hosts` to also accept new `target_hosts` variable Status in Bifrost: Triaged Bug description: Many thanks for providing a single `install.yaml` playbook which installs `bifrost` in one go. Great work! It seems the hosts are fixed to target in the playbook. Would it be possible to make the playbook work with other inventories by introducing a new variable `target_hosts` as in PR https://review.opendev.org/c/openstack/bifrost/+/944810 ? The proposed change should be backwards compatible. To manage notifications about this bug go to: https://bugs.launchpad.net/bifrost/+bug/2103448/+subscriptions

1 0

[neutron] Bug deputy report for week 12 of 2025
by Jakub Libosvar 24 Mar '25

24 Mar '25

Hi all, I was the deputy for the last week. There are two bugs I left in “Undecided" that might not be in Neutron and need deeper understanding of what is going on. Undecided --------- - Race condition - Error creating instance if network is deleted by different process https://bugs.launchpad.net/neutron/+bug/2103500 It needs further investigation as it is unknown if the problem is with Neutron or Nova - Open vSwitch (Version 3.3.0) goes into deadlocked state https://bugs.launchpad.net/neutron/+bug/2103641 Based on the description of the bug it sounds like a problem with OVS rather than Neutron. High ---- - [FT] Random error in ``test_ovn_sb_sync_host_with_other_agent_type_not_deleted`` https://bugs.launchpad.net/neutron/+bug/2103424 Needs an assignee Wishlist -------- - [RFE][OVN] A L3 router tool https://bugs.launchpad.net/neutron/+bug/2103521

1 0

[heat][ptg] Topics for PTG April 2025
by Takashi Kajinami 24 Mar '25

24 Mar '25

Hi, I started updating the etherpard[1] for the heat sessions in upcoming PTG. If you are interested in joining the sessions then please add your name and your time zone. Also, please add any topics you want to discuss during these sessions. I'll reserve the slots based on these inputs, likely next week. [1] https://etherpad.opendev.org/p/apr2025-ptg-heat -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

[openstack][rabbitmq]rabbitmq is broken
by Nguyễn Hữu Khôi 23 Mar '25

23 Mar '25

Hello. I am using rabbitmq quorum queue in my system. After I reboot the controllers, Now it has this debug message and my system runs under error. "repairing leader record" Nguyen Huu Khoi

2 3

[mistral][heat][watcher][aodh] croniter being abandoned
by Thierry Carrez 22 Mar '25

22 Mar '25

Hi everyone, It was brought to my attention that the croniter maintainer has decided to abandon his project, due to not wanting to deal with his perceived exposure to the EU Cyber-Resilience act (CRA). https://pypi.org/project/croniter/#disclaimer The maintainer indicates that you should no longer use it and it may be "unpublished" any time after March 15, 2025. Croniter is being used in at least Mistral, Heat, Watcher, and Aodh as a dependency. While this is clearly an overreaction (the CRA only applies to "economic operators" putting "products with digital elements" on the market "in the course of a commercial activity"), we should probably prepare to migrate away from this dependency, or maintain a fork of it. -- Thierry Carrez (ttx)

5 8

[openstack-ansible] Weird install failure
by Sarah Thompson 22 Mar '25

22 Mar '25

Hi all, I think I'm close to getting things working at this point, but I'm seeing a weird install failure during openstack.osa.setup_openstack: FAILED - RETRYING: [ostk-controller-heat-api-container-7d1e8599 -> ostk-controller-utility-container-db5068d8]: Add service users to roles (1 retries left).Result was: attempts: 5 censored: 'the output has been hidden due to the fact that ''no_log: true'' was specified for this result' changed: false retries: 6 Using module file /etc/ansible/ansible_collections/openstack/cloud/plugins/modules/role_assignment.py Pipelining is enabled. <ostk-controller> ESTABLISH SSH CONNECTION FOR USER: root <ostk-controller> SSH: ansible.cfg set ssh_args: (-C)(-o)(ControlMaster=auto)(-o)(ControlPersist=300) <ostk-controller> SSH: ANSIBLE_HOST_KEY_CHECKING/host_key_checking disabled: (-o)(StrictHostKeyChecking=no) <ostk-controller> SSH: ANSIBLE_REMOTE_PORT/remote_port/ansible_port set: (-o)(Port=22) <ostk-controller> SSH: ansible_password/ansible_ssh_password not set: (-o)(KbdInteractiveAuthentication=no)(-o)(PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey)(-o)(PasswordAuthentication=no) <ostk-controller> SSH: ANSIBLE_REMOTE_USER/remote_user/ansible_user/user/-u set: (-o)(User="root") <ostk-controller> SSH: ANSIBLE_TIMEOUT/timeout set: (-o)(ConnectTimeout=5) <ostk-controller> SSH: Set ssh_extra_args: (-o)(UserKnownHostsFile=/dev/null)(-o)(StrictHostKeyChecking=no)(-o)(ServerAliveInterval=64)(-o)(ServerAliveCountMax=1024)(-o)(Compression=no)(-o)(TCPKeepAlive=yes)(-o)(VerifyHostKeyDNS=no)(-o)(ForwardX11=no)(-o)(ForwardAgent=yes)(-T) <ostk-controller> SSH: found only ControlPersist; added ControlPath: (-o)(ControlPath="/root/.ansible/cp/d3dfd6cdfc") <ostk-controller> SSH: EXEC ssh -vvvvv -C -o ControlMaster=auto -o ControlPersist=300 -o StrictHostKeyChecking=no -o Port=22 -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=5 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o ServerAliveInterval=64 -o ServerAliveCountMax=1024 -o Compression=no -o TCPKeepAlive=yes -o VerifyHostKeyDNS=no -o ForwardX11=no -o ForwardAgent=yes -T -o 'ControlPath="/root/.ansible/cp/d3dfd6cdfc"' ostk-controller 'sudo lxc-attach --clear-env --name ostk-controller-utility-container-db5068d8 -- su - root -c '"'"'/bin/sh -c '"'"'"'"'"'"'"'"'/openstack/venvs/utility-30.1.0.dev46/bin/python && sleep 0'"'"'"'"'"'"'"'"''"'"'' <ostk-controller> rc=1, stdout and stderr censored due to no log <ostk-controller> Failed to connect to the host via ssh: <error censored due to no log> failed: [ostk-controller-heat-api-container-7d1e8599 -> ostk-controller-utility-container-db5068d8(192.168.100.117)] (item=None) => attempts: 5 censored: 'the output has been hidden due to the fact that ''no_log: true'' was specified for this result' changed: false fatal: [ostk-controller-heat-api-container-7d1e8599 -> {{ _service_setup_host }}]: FAILED! => censored: 'the output has been hidden due to the fact that ''no_log: true'' was specified for this result' changed: false These logs came from running ansible with -vvvvv as a parameter. Looking at the failed ssh, this root causes pretty straightforwardly: ssh -vvvvv -C -o ControlMaster=auto -o ControlPersist=300 -o StrictHostKeyChecking=no -o Port=22 -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=5 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o ServerAliveInterval=64 -o ServerAliveCountMax=1024 -o Compression=no -o TCPKeepAlive=yes -o VerifyHostKeyDNS=no -o ForwardX11=no -o ForwardAgent=yes -T -o 'ControlPath="/root/.ansible/cp/d3dfd6cdfc"' ostk-controller 'sudo lxc-attach --clear-env --name ostk-controller-utility-container-db5068d8 -- su - root -c '"'"'/bin/sh -c '"'"'"'"'"'"'"'"'/openstack/venvs/utility-30.1.0.dev46/bin/python && sleep 0'"'"'"'"'"'"'"'"''"'"'' If I manually ssh to ostk-controller and lxc-attach -n ostk-controller-utility-container-db5068d8, then run the command explicitly: root@ostk-controller-utility-container-db5068d8:~# /openstack/venvs/utility-30.1.0.dev46/bin/python && sleep 0 Python 3.10.12 (main, Feb 4 2025, 14:57:36) [GCC 11.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> KeyboardInterrupt >>> exit() So basically it's invoking an interactive python session, which of course times out, and after 5 retries the installation aborts. Something is obviously missing somewhere, most likely a parameter after the python command which specifies a python script to be run. Any ideas? Thanks all, Sarah

2 1

[cinder][nova] force detach volume
by Arnaud Morin 22 Mar '25

22 Mar '25

Hey team, Is there any way to force detach a volume when the nova compute service is down? Like when the hypervisor is off, we want to detach the volume and attach it to another instance. Maybe I'm missing the way to do it, but detach action on nova side seems a synchronous task that I can't force without admin creds. Thanks for any help, Regards, Arnaud

4 6

[release] Release countdown for week R-1, Mar 24 - 28
by Elõd Illés 22 Mar '25

22 Mar '25

(re-sent this mail with the right week number in subject, sry :S) Development Focus ----------------- We are on the final mile of the 2025.1 Epoxy development cycle! Remember that the 2025.1 Epoxy final release will include the latest release candidate (for cycle-with-rc deliverables) or the latest intermediary release (for cycle-with-intermediary deliverables) available. March 28th, 2025 is the deadline for final 2025.1 Epoxy release candidates as well as any last cycle-with-intermediary deliverables. We will then enter a quiet period until we tag the final release on April 2nd, 2025. Teams should be prioritizing fixing release-critical bugs, before that deadline. Otherwise it's time to start planning the 2025.2 Flamingo development cycle, including discussing Forum and PTG sessions content, in preparation of Project Teams Gathering (virtual), April 7th-11th, 2025. Actions ------- Watch for any translation patches coming through on the stable/2025.1 branch and merge them quickly. If you discover a release-critical issue, please make sure to fix it on the master branch first, then backport the bugfix to the stable/2025.1 branch before triggering a new release. Please drop by #openstack-release with any questions or concerns about the upcoming release ! Upcoming Deadlines & Dates -------------------------- Final 2025.1 Epoxy release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 Előd Illés irc: elodilles @ #openstack-release

1 0

[release] Release countdown for week R-4, Mar 24 - 28
by Elõd Illés 22 Mar '25

22 Mar '25

Development Focus ----------------- We are on the final mile of the 2025.1 Epoxy development cycle! Remember that the 2025.1 Epoxy final release will include the latest release candidate (for cycle-with-rc deliverables) or the latest intermediary release (for cycle-with-intermediary deliverables) available. March 28th, 2025 is the deadline for final 2025.1 Epoxy release candidates as well as any last cycle-with-intermediary deliverables. We will then enter a quiet period until we tag the final release on April 2nd, 2025. Teams should be prioritizing fixing release-critical bugs, before that deadline. Otherwise it's time to start planning the 2025.2 Flamingo development cycle, including discussing Forum and PTG sessions content, in preparation of Project Teams Gathering (virtual), April 7th-11th, 2025. Actions ------- Watch for any translation patches coming through on the stable/2025.1 branch and merge them quickly. If you discover a release-critical issue, please make sure to fix it on the master branch first, then backport the bugfix to the stable/2025.1 branch before triggering a new release. Please drop by #openstack-release with any questions or concerns about the upcoming release ! Upcoming Deadlines & Dates -------------------------- Final 2025.1 Epoxy release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 Előd Illés irc: elodilles @ #openstack-release

1 0