- openstack-discuss - lists.openstack.org

Fwd: PCI passthrough - flavor not found
by Francesco Di Nucci 28 Mar '25

28 Mar '25

Thanks, forwarding to the list as information; tried it and still got the same error -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci(a)na.infn.it -------- Forwarded Message -------- Subject: Re: PCI passthrough - flavor not found Date: Fri, 28 Mar 2025 11:10:25 +0200 From: Mike Currin <mike(a)idia.ac.za> To: Francesco Di Nucci <francesco.dinucci(a)na.infn.it> Hi, Forgot to reply to the list as well so ignore the one specifically to you, it's the same content though Regards Mike On Fri, Mar 28, 2025 at 11:08 AM Mike Currin <mike(a)idia.ac.za> wrote: Hi Francesco, We had something similar for our A100 GPUs, we had to add "device_type":"type-PF" vs PCI and then it worked. Maybe give that a go. I've seen it mentioned on the list before. Regards Mike On Fri, Mar 28, 2025 at 11:00 AM Francesco Di Nucci <francesco.dinucci(a)na.infn.it> wrote: Hi all, I am trying to setup PCI passthrough with Nova, following guides such as this <https://superuser.openinfra.org/articles/a-comprehensive-guide-to-configuri…> and this <https://medium.com/@thomasal14/gpu-passthrough-in-openstack-da2a98a16f7b>: * installed a GPU on a compute node, configured kernel etc and now it is using the vfio-pci driver * set [pci]/device_spec = { "vendor_id": "10de", "product_id": "1ff2" } on compute node (formerly [pci]/passthrough_whitelist) and restarted openstack-nova-* * On the controller node set [pci]/alias: { "vendor_id":"10de", "product_id":"1ff2", "device_type":"type-PCI", "name":"nvidia-t400" }, [filter_scheduler]/enabled_filters = PciPassthroughFilter, [filter_scheduler]/available_filters = nova.scheduler.filters.all_filters and restarted openstack-nova-* * Created a flavor with openstack flavor create --vcpus 4 --ram 8192 --disk 40 --property "pci_passthrough:alias"="nvidia-t400:1" gpu_flavor, it is shown with openstack flavor list * Created an image with --property img_hide_hypervisor_id=true * Tried to create an instance with openstack server create --flavor gpu_flavor --image Almalinux_GPU --key-name "My Key" --network my_network test-gpu (also with --availability-zone nova:my-gpu-node.example.com <http://my-gpu-node.example.com>) * VM creation fails with this errors on the controller node /nova-api.log/ HTTP exception thrown: Flavor gpu_flavor could not be found. /nova-scheduler.log/ Filter PciPassthroughFilter returned 0 hosts Filtering removed all hosts for the request with instance ID '131d5c1c-1927-42c0-bb48-618c05d31c2a'. Filter results: ['PciPassthroughFilter: (start: 19, end: 0)'] /nova-conductor.log/ Failed to schedule instances: nova.exception_Remote.NoValidHost_Remote: No valid host was found. There are not enough hosts available. If I understand correctly it's a cascading error generating from the flavor not found, even though it exists... Anyone has encountered something like this/has suggestions? Am I missing some config? Thanks in advance -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email:francesco.dinucci@na.infn.it -- Mike Currin email: mike(a)idia.ac.za Cloud Computing System Support Inter-University Institute for Data Intensive Astronomy (IDIA) University of Cape Town

1 0

[all][qa] QA tools (devstack/grenade/tempest) setup for new stable/2025.1 and current master
by Ghanshyam Mann 27 Mar '25

27 Mar '25

Hi All, The QA tools setup[1] for the new stable/2015.1 and the current master is completed. I would like to highlight a couple of things: * Recheck if devstack/gernade jobs on master or any backport were not running/testing correctly. * By default, grenade-skip-level-always is added in integrated gate templates as voting. As the current master is non-SLURP, Testing N-2 -> N upgrade is not mandatory, so the project can opt to make it non-voting or remove it from their integrated template[2]. [1] https://review.opendev.org/q/topic:%22qa-2025-1-release%22 [2] https://github.com/openstack/tempest/blob/f4a8698b97a5433b8e64df408aace2fb1… -gmann

1 0

[openstack-helm] health-probes timeout for neutron agents (l3 and dhcp) and nova compute
by Alberto Molina Coballes 27 Mar '25

27 Mar '25

Hi, We’re facing an issue when deploying OpenStack 2024.1 with OpenStack Helm and OVS, the health probes fail for neutron-l3-agent, neutron-dhcp-agent and nova-compute while the internal RPC communication between the nova and neutron components look fine: Neutron: openstack network agent list +--------------------------------------+--------------------+--------------------------------+-------------------+-------+-------+---------------------------+ | ID | Agent Type | Host | Availability Zone | Alive | State | Binary | +--------------------------------------+--------------------+--------------------------------+-------------------+-------+-------+---------------------------+ | 433c2b07-5c82-4545-991d-6d0de6044ae9 | DHCP agent | fig-virt-intdev-alberto-node-0 | nova | :-) | UP | neutron-dhcp-agent | | 56c050fa-e58e-46a6-8191-0d0d481de246 | Open vSwitch agent | fig-virt-intdev-alberto-node-0 | None | :-) | UP | neutron-openvswitch-agent | | 5ea28388-3fac-4ebb-bce4-6b210f8a3766 | Metadata agent | fig-virt-intdev-alberto-node-0 | None | :-) | UP | neutron-metadata-agent | | 6a4506ca-6fe4-489a-b370-6e426db40d50 | DHCP agent | fig-virt-intdev-alberto-node-1 | nova | :-) | UP | neutron-dhcp-agent | | 772a1d3a-b432-4ac3-8dfe-d3affc6f226d | Metadata agent | fig-virt-intdev-alberto-node-1 | None | :-) | UP | neutron-metadata-agent | | 7bd8360c-468a-4473-a470-abfb1ab435da | Open vSwitch agent | fig-virt-intdev-alberto-node-1 | None | :-) | UP | neutron-openvswitch-agent | | 9d362a63-5740-44ed-ac77-4548eee59205 | L3 agent | fig-virt-intdev-alberto-node-0 | nova | :-) | UP | neutron-l3-agent | | a2cc9dc4-1600-4c5d-a250-2e43cf062cf3 | L3 agent | fig-virt-intdev-alberto-node-1 | nova | :-) | UP | neutron-l3-agent | +--------------------------------------+--------------------+--------------------------------+-------------------+-------+-------+---------------------------+ The neutron-l3 and neutron-dhcp pods are not ready: k -n openstack get pods -l application=neutron |grep 'l3\|dhcp' neutron-dhcp-agent-default-fw5rm 0/1 Running 0 127m neutron-dhcp-agent-default-vh7c4 0/1 Running 0 127m neutron-l3-agent-default-4h5tp 0/1 Running 0 24m neutron-l3-agent-default-bdngv 0/1 Running 0 24m Because the health probes fail: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning Unhealthy 4m38s (x119 over 127m) kubelet Readiness probe failed: Health probe timed out. Agent is down or response timed out When trying to execute the health probe manually from the container, the probe fails with a timeout after 60 seconds (RPC_PROBE_TIMEOUT=60) neutron@fig-virt-intdev-alberto-node-1:/$ python /tmp/health-probe.py --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/dhcp_agent.ini --agent-queue-name dhcp_agent --use-fqdn Health probe timed out. Agent is down or response timed out The situation for nova is quite similar: openstack compute service list +--------------------------------------+----------------+---------------------------------+----------+---------+-------+----------------------------+ | ID | Binary | Host | Zone | Status | State | Updated At | +--------------------------------------+----------------+---------------------------------+----------+---------+-------+----------------------------+ | eaf4684c-88a4-47dd-b340-b7dbebf148ba | nova-conductor | nova-conductor-679d57f977-zbq92 | internal | enabled | up | 2025-03-27T13:11:33.000000 | | 9164d63f-608c-44cc-8a92-2f2bac07c622 | nova-scheduler | nova-scheduler-845f87b9b5-vq9p5 | internal | enabled | up | 2025-03-27T13:11:36.000000 | | 464cd394-8b26-49ad-8c82-f014ca00ec7e | nova-compute | fig-virt-intdev-alberto-node-1 | nova | enabled | up | 2025-03-27T13:11:33.000000 | | aa7e5f6d-2533-4953-bb8d-9f9bfb7fc6bd | nova-compute | fig-virt-intdev-alberto-node-0 | nova | enabled | up | 2025-03-27T13:11:33.000000 | +--------------------------------------+----------------+---------------------------------+----------+---------+-------+----------------------------+ And the nova-compute pods are not ready because the health probes fail: k -n openstack get pods -l component=compute NAME READY STATUS RESTARTS AGE nova-compute-default-t8w7x 1/2 Running 1 (70m ago) 3h31m nova-compute-default-vz7nf 1/2 Running 1 (70m ago) 3h31m To be sure that the OpenStack RPC is working fine, the health probes have been deleted for nova-compute, then nova-cell-setup is executed and the hypervisors are ready. Some VMs have been launched in this environment successfully (nova-compute), getting IP from the DHCP agent or adding floating IPs (l3-agent) and the OpenStack behaviour is normal. So I’m confused about the health-probes failing. Any idea on what can be wrong or what to check is welcome. Thanks! Alberto Note: This is a Kubernetes cluster running on two VMs (OpenStack). This virtual environment has been redeployed several times with some modifications and the issue is fully reproducible: the probes for nova-compute, neutron-l3-agent and neutron-dhcp-agent always fail.

1 0

[Glance]Cancelling Weekly Meeting (March 27)
by Mridula Joshi 27 Mar '25

27 Mar '25

Hello, Cancelling today's weekly meeting, As most of the members are not around. Apologies for the last min update. Thanks, Mridula Joshi

1 0

[designate] multiple zone catalogs with multiple zones
by Benedikt Trefzer 26 Mar '25

26 Mar '25

Hi List I'm trying to create an additional pool with a separate catalog zone. For the default pool, I can do an AXFR to the catalog domain, this works (either without tsig key or with a tsig). For the catalog of the second pool cannot be queried (Log sais Zone not found). In the DB I can see the zone. Questions: - Is it possible to have multiple pools with separate catalogs, does anyone have a running setup ? - Reading this [1] line in the code, I assume It's not possible having multiple zones without using tsig, correct ? Thanks a lot. Benedikt [1] https://opendev.org/openstack/designate/src/branch/master/designate/mdns/ha…

1 1

Nova features
by engineer2024 26 Mar '25

26 Mar '25

Where can I find the nova feature requests which are yet to be developed ? I am thinking of contributing to adding new features.

3 3

[largescale-sig] Next meeting: March 26, 16utc
by Thierry Carrez 26 Mar '25

26 Mar '25

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 16UTC to facilitate America timezones participation. In these troubled DST times, you should doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250326T16 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 1

#eventlet-removal Flamingo PTG
by Herve Beraud 26 Mar '25

26 Mar '25

Hello folks, We’re meeting again on the Project Teams Gathering in April (7-11th). The slot for the Eventlet Removal Initiative PTG is: Tuesday (Apr 8) 1400-1600 UTC The etherpad is: https://etherpad.opendev.org/p/apr2025-ptg-eventlet Please feel free to insert your topic proposals. Additional details can be found at https://ptg.opendev.org/ Regards, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[release][ptl][tc] OpenInfra Live for OpenStack 2025.1 ‘Epoxy’
by helena＠openinfra.dev 26 Mar '25

26 Mar '25

Hi everyone, Following the release of OpenStack 2025.1 ‘Epoxy’ next Wednesday, we'd like to go ahead and schedule the OpenInfra Live for Thursday, April 3 at 1400 UTC. If you would like to represent your project team’s updates in the Epoxy release as well as their plans for Flamingo, please let me know. If you are not familiar, you can find reference examples like 2024.2 Dalmation [1] and 2024.1 Caracal [2]. [1] https://www.youtube.com/watch?v=6igJNIJ9yFE [2] https://www.youtube.com/watch?v=3BgAXbFaVqw&t=1707s Thanks! Helena helena(a)openinfra.dev Community Programs Manager The OpenInfra Foundation [openinfraLogo-sm.png]

3 2

[neutron][ops][upgrade] l3-agent failure during upgrade to Zed
by Eugen Block 25 Mar '25

25 Mar '25

Hi *, maybe I missed some announcement or something, but usually, I read the release notes [0] before upgrading our OpenStack cloud. I didn't notice anything regarding DB schema upgrades. And after the upgrade from Yoga to Zed in a test environment went well, I tried the same in our production today. Note that I didn't have a router in my test cloud, so that's probably why I didn't notice anything. Unfortunately, there has been a schema change, that's why the l3-agent failed to start properly with this error: 2025-03-21 12:29:14.527 846393 CRITICAL neutron [None req-e225ff0a-82e1-473b-9eba-9a11caa7ace7 - - - - - -] Unhandled error: oslo_messaging.rpc.client.RemoteError: Remote error: OperationalError (pymysql.err.OperationalError) (1054, "Unknown column 'portforwardings.external_port' in 'SELECT'") Indeed, the upgraded control node didn't have "external_port" anymore in /usr/lib/python3/dist-packages/neutron/db/models/port_forwarding.py, while the not yet upgraded control node did. So the situation could only be resolved by proceeding with the upgrade. But that meant an interruption for our virtual routers, causing floating IPs to be unreachable for a couple of minutes. Note that we're using highly-available routers. I thought about setting "no-ha" for each router, but that can only be done for disabled routers, which is not an option, of course. And it doesn't really fit into the "rolling upgrade" concept, which has worked great so far. Since we moved to Ubuntu last September (while still on Victoria), we've been able to upgrade to Yoga without any issues. And while the interruption today was not too critical, I was still surprised that such an important change didn't even make it into the Zed release notes. Was that a mistake or did I miss something? Are there other places I need to check before attempting an upgrade? Thanks, Eugen [0] https://docs.openstack.org/releasenotes/neutron/zed.html

3 9

[dev] New contributing organization help
by Dominik Danelski 25 Mar '25

25 Mar '25

Hello community, I work at a silver member of OpenInfra and will make code contributions on behalf of my employer. I am aware about the requirement to sign Contributor License Agreement listing me as the responsible person. Other than that, are there any additional requirements on identifying me as a corporate developer? For example contributor guide lists creating INDIVIDUAL Member account as one of the setup steps and it got me a bit worried. Kind regards Dominik Danelski @ CloudFerro

4 3

[kolla] Flamingo PTG
by Michał Nasiadka 25 Mar '25

25 Mar '25

Hello Koalas, We’re meeting again on the Project Teams Gathering in April (7-11th). The slots for Kolla/Kolla-Ansible/Kayobe PTG are: Tuesday - 07:00-08:00 UTC (general, Kolla and Kolla-Ansible) Wednesday - 07:00-08:00 UTC (general, Kolla and Kolla-Ansible) Friday - 14:00-15:00 UTC (Kayobe) If there’s a need of an additional afternoon (UTC) slot - please let us know. The ether pad is at the usual location: https://etherpad.opendev.org/p/kolla-flamingo-ptg Please insert your topic proposals and see you on the PTG. Additional details can be found at https://ptg.opendev.org/ Cheers, Michal

1 0

[publiccloud-sig] Next meeting of Public Cloud SIG upcoming - March 26th at 0800 UTC
by Felix Kronlage-Dammers 25 Mar '25

25 Mar '25

Hi everyone, This upcoming Wednesday (March 26th) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG I'll not be around but Artem (gtema) will be hosting the call. Thanks Artem! cheers felix -- Felix Kronlage-Dammers Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[openstack][rabbitmq]computes cannot register to nova 2025.0master
by Nguyễn Hữu Khôi 24 Mar '25

24 Mar '25

Hello. I deployed OpenStack 2025.1 Master with Kolla-Ansible, but the compute nodes cannot register with Nova. Error: Cannot update service status on host "compute05" due to an unexpected exception.: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 3dad7dbe8ea9429c83958b98bccc7094 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver Traceback (most recent call last): 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/virt/libvirt/driver.py", line 5687, in _set_host_enabled 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver service = objects.Service.get_by_compute_host(ctx, CONF.host) 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_versionedobjects/base.py", line 175, in wrapper 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver result = cls.indirection_api.object_class_action_versions( 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/rpcapi.py", line 240, in object_class_action_versions 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver return cctxt.call(context, 'object_class_action_versions', 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/rpc/client.py", line 190, in call 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver result = self.transport._send( 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/transport.py", line 123, in _send 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver return self._driver.send(target, ctxt, message, 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 800, in send 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver return self._send(target, ctxt, message, wait_for_reply, timeout, 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 789, in _send 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver result = self._waiter.wait(msg_id, timeout, 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 654, in wait 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver message = self.waiters.get(msg_id, timeout=timeout) 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 520, in get 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver raise oslo_messaging.MessagingTimeout( 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 3dad7dbe8ea9429c83958b98bccc7094 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver All services are in a "down" state, but this issue only occurs when using a three-controller cluster. When I use a single controller, everything works fine. My Env: OS: Ubuntu 22.04 OpenStack Version: 2025.1 Master Deployment Tool: Kolla-Ansible 19 Thank you. Nguyen Huu Khoi

3 7

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

24 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 22 Mar '25

22 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 21 Mar '25

21 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 21 Mar '25

21 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 21 Mar '25

21 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 21 Mar '25

21 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

[neutron] Drivers meeting canceled Friday, March 21st
by Brian Haley 20 Mar '25

20 Mar '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as I have a conflict and cannot attend. Let's just add any new RFE items to the agenda for the upcoming PTG [0] - I'll try and group them all together in our Thursday meeting slots if possible. Just a reminder there are still open specs that need review, list is at [1], would be good to get them merged. Have a nice weekend! -Brian [0] https://etherpad.opendev.org/p/apr2025-ptg-neutron [1] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0