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

[tempest] dynamically defined tests
by jerome.defavereau＠uclouvain.be 11 Mar '25

11 Mar '25

Hi, I'm currently trying to use tempest to run a simple series of tests on each of my hypervisors. I would like to have a separate test for each hypervisor instead of a single test for all. For that I need to dynamically define tests. I wrote a simple plugin to run the tests and then I use "sertattr" in a loop to define one "test_" method per hypervisor. The plugin is listed properly, as well as the tests, but when I run them using a regexp or the full test path I get "The test run didn't actually run any tests". I was able to run them using: "python -m unittest discover -s ./multi_hypervisor_tempest_plugin" but tempest run fails. Would anyone have wisdom to share ? Thanks !

1 0

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

10 Mar '25

Hello Stackers, We're three weeks away from the coordinated 2025.1 "Epoxy" release [1]. The release will be published on 2025-04-02. This week, we're expecting to publish release candidates for all project deliverables that follow the "cycle-with-rc" release model [2]. In the past week, the OpenStack TC appointed project team leaders for Barbican (Mauricio Harley/mharley), Masakari (Suzhengwei/suzhengwei), and Zaqar (Hao Wang/wanghao) project teams. There's a pending appointment to the OpenStack Charms project [3] that we'll wrap up this week. The Oslo team re-nominated DPL liaisons, and the TC is going through the process of naming its chair and vice-chair for its current term. The community convened alongside Southern California Linux Expo (SCaLE) 2025 for an OpenInfra Days North America event. The event was well attended and featured close to 40 sessions spread across two days. You can watch most of the recorded proceedings as they were streamed live on both days [4][5][6]. We also celebrated OpenStack's 15th birthday with cake! If you missed this one, please check out upcoming birthday celebrations organized by different local user groups around the world [7]. === Weekly Meeting === The OpenStack Technical Committee (TC) held its weekly meeting primarily via video call [8], with action items and minutes documented in IRC [9]. The agenda covered past action items, PTL election results, leaderless projects, and a discussion on the format of TC meetings. A number of new Project Team Leads who will take charge of several OpenStack project teams next week are not core reviewers of the deliverables their teams manage. The general consensus was that a PTL does not have to be a core reviewer, as long as they collaborate effectively with the cores. PTLs should focus on driving consensus rather than making unilateral decisions—whether technical or otherwise. The TC trusts that if no one else nominates or objects, a lone PTL nominee has the support of the team. I personally believe that new and relatively new contributors can bring energy to the PTL role by being inquisitive and enthusiastic. I hope that the core team nurtures these qualities to integrate them into the fold sooner rather than later. The TC discussed why certain project teams that were deemed "leaderless" at the end of this past election consistently require appointments. We're learning from volunteers who have stepped up to lead each of these teams whether they would suggest any changes to the election process. Finally, we spent some time discussing whether the TC's monthly video meetings were useful and what the downsides were. We'll revisit this topic at the upcoming Project Teams Gathering with a wider audience. The next meeting of the OpenStack Technical Committee is today, 2025-03-11. Please find the agenda on the meeting's wiki page [10]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== Add suzhengwei as PTL for Masakari | https://review.opendev.org/c/openstack/governance/+/943226 Appoint Hao Wang as PTL for OpenStack Zaqar | https://review.opendev.org/c/openstack/governance/+/943338 Switch back Oslo to DPL model | https://review.opendev.org/c/openstack/governance/+/942793 Appoint Mauricio Harley as PTL for Barbican | https://review.opendev.org/c/openstack/governance/+/942907 Add gouthamr's nomination for 2025.2 TC chair | https://review.opendev.org/c/openstack/governance/+/943204 Add TC chair nomination folder for 2025.2 | https://review.opendev.org/c/openstack/governance/+/943203 ==== Open for Review ==== Appoint Felipe Reyes as PTL for OpenStack Charms | https://review.opendev.org/c/openstack/governance/+/943254 Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === Upcoming Events === 2025-03-11: OpenInfra Board Meeting: https://board.openinfra.org/ 2025-04-02: OpenStack 2025.1 ("Epoxy") Release 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] cycle-with-rc release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] Appoint Felipe Reyes as PTL for OpenStack Charms: https://review.opendev.org/c/openstack/governance/+/943254 [4] OpenInfraDays @ SCaLE 2025, Thursday Stream 1: https://www.youtube.com/watch?v=W9OmGdtJAAE [5] OpenInfraDays @ SCaLE 2025, Thursday Stream 2: https://www.youtube.com/watch?v=prIwZshr55U [6] OpenInfraDays @ SCaLE 2025, Friday: https://www.youtube.com/watch?v=Fv0Bdw6pBlk [7] Celebrating 15 years of OpenStack: https://www.openstack.org/blog/celebrating-15-years-of-openstack/ [8] TC Meeting Video Recording, 2025-03-04: https://youtu.be/NMDrz1N6ogo [9] TC Meeting IRC Log 2025-03-04: https://meetings.opendev.org/meetings/tc/2025/tc.2025-03-04-18.00.log.html [10] TC Meeting Agenda, 2025-03-11: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

openstack ansible lxc containers
by engineer2024 10 Mar '25

10 Mar '25

Using the lxc-container-create playbook, how to. create a container with a specific name and specific release ? openstack-ansible lxc-containers-create.yml -e "container_name=testing" -e "lxc_container_distribution=ubuntu" -e "lxc_container_release=jammy" --limit 'test' is throwing an error. it is trying to attach to the 'testing' container when it does not exist in the first place. I want the playbook to create one with that name ? So, what's the workaround ? --- module_stderr": "lxc-attach: testing: attach.c: get_attach_context: 405 Connection refused - Failed to get init pid\nlxc-attach: testing: attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", ----

2 1

[telemetry] Nominate Juan Larriba to Telemetry core
by Takashi Kajinami 10 Mar '25

10 Mar '25

Hi, As some of you may know, current telemetry core team is quite small due to some cores shifting their focus recently. (As far as I see Matthius and I are the cores around the community recently). On the other hand we have seen revived interest in adding new features to telemetry services. To make sure these effort may receive appropriate feedback, I'd like to nominate Juan as a new Telemetry project core. He has been contributing the project for some time, and I've recently seen his consistent presence to review patches. In addition he volunteered to be a Telemetry PTL for the next cycle with his continued interest to keep the project active. If I don't hear any objections for one week, I'll add Juan to the group. Also, I'd like to take this chance to mention that we are really happy to see anyone who is interested in helping the project and appreciate any help to review proposed changes or maintain the project (so that we can invite them to the core group as well). Thank you, Takashi Kajinami -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 4

[neutron] bug deputy report for 2025w10
by Bence Romsics 10 Mar '25

10 Mar '25

Hi Neutron Team! Last week we had the following new bug reports: Gate failures: * https://bugs.launchpad.net/neutron/+bug/2100776 test_securitygroup(ovs-openflow) fullstack test random failure with Time out exception unassigned * https://bugs.launchpad.net/neutron/+bug/2101165 Random failure in test_established_tcp_session_after_re_attachinging_sg unassigned * https://bugs.launchpad.net/neutron/+bug/2101166 Random failure in dvr ovs grenade jobs to ping vm post upgrade unassigned * https://bugs.launchpad.net/neutron/+bug/2100806 Intermittent test_batch_notifier failure fix proposed: https://review.opendev.org/c/openstack/neutron/+/943212 High: * https://bugs.launchpad.net/neutron/+bug/2101150 User who is not owner of the SG can create/delete rules in the shared SG assigned to Slawek * https://bugs.launchpad.net/neutron/+bug/2101063 [OVN] min-bw QoS policy cannot be defined alone, exception raised fix proposed: https://review.opendev.org/c/openstack/neutron/+/943664 Medium: * https://bugs.launchpad.net/neutron/+bug/2101140 [OVN] Make LSP up/down events processing resilient to IDL disconnections fix proposed: https://review.opendev.org/c/openstack/neutron/+/943404 * https://bugs.launchpad.net/neutron/+bug/2101162 [OVN] Use HA_Chassis_Group for tunnelled gateway network LRPs WIP fix: https://review.opendev.org/c/openstack/neutron/+/938134 * https://bugs.launchpad.net/neutron/+bug/2100938 Assign HA_Chassis_Group to all LRPs for tunnelled gateway assigned to Rodolfo Eventlet removal: * https://bugs.launchpad.net/neutron/+bug/2101076 [eventlet-removal] Remove the usage of eventlet in the MacVTap agent unassigned RFEs: * https://bugs.launchpad.net/neutron/+bug/2100770 [RFE] Make alembic_migration scripts in neutron idempotent * https://bugs.launchpad.net/neutron/+bug/2073254 nova-compute optional wait for vif-plugged in ovn usecase Further triage needed: * https://bugs.launchpad.net/neutron/+bug/2101077 neutron-bgp-agent dies with debug log + json Info requested from reporter on reproduction method * https://bugs.launchpad.net/neutron/+bug/2100752 Severe Packet Loss During Live Migration Due to Premature Route Advertisement in Neutron BGP Dynamic Routing Edit Lajos promised to triage this Cheers, Bence

1 0

using compute_monitors option for nova
by Jiatong Shen 07 Mar '25

07 Mar '25

Hello Experts, I hope this email finds you well. I am researching the "compute_monitors" option for nova and would like to find out what it can do. By some googling I find that by enabling this option, the compute_nodes table will store extra metrics and reflect the vcpu usage on the compute node. My question is is it possible to also save memory usage? Besides, is this option still supported in the long term? Thank you very much for the help. -- Best Regards, Jiatong Shen https://docs.openstack.org/ocata/config-reference/compute/config-options.ht…

2 2

[dev][ptl][release] Cycle highlights reminder (2025.1/Epoxy)
by Jeremy Stanley 07 Mar '25

07 Mar '25

Just a reminder in case anyone missed it: we've officially reached the deadline for merging 2025.1/Epoxy release highlights, but if anyone has something they want to mention then now is the time to write, push and approve it! The OpenInfra marketing machine is getting ready to digest what they find at https://releases.openstack.org/epoxy/highlights.html and put together a press release and package for news outlets. They're interested in whatever you're excited to include, but especially anything related to AI, digital sovereignty, security, or VMware feature parity. Please get your remaining highlights in ASAP!!! -- Jeremy Stanley

1 0

[horizon] Propose Jan Jašek to Horizon core
by Tatiana Ovchinnikova 07 Mar '25

07 Mar '25

Hello team, As it was discussed at our weekly meeting, I would like to add Jan Jašek to the OpenStack Horizon core team. Jan has been contributing to the Horizon project since 2022, and his impact is tremendous. His improvement and maintenance of Horizon test jobs made them significantly more stable, and Jan's reviews are always fast and valuable. Thank you Jan! Regards, Tatiana

1 0

[release] Release countdown for week R-3
by Thierry Carrez 07 Mar '25

07 Mar '25

Development Focus ----------------- The Release Candidate (RC) deadline is next Friday, March 14th, 2025. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2025.1 branch will be cut. This branch will track the 2025.1 Epoxy release. Once stable/2025.1 has been created, the master branch will be ready to switch to 2025.2 Flamingo development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2025.1 Epoxy plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2025.1 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2025.1 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be Flamingo development) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2025.1 Epoxy release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 14th, 2025 (R-3 week) Final RC deadline: March 28th, 2025 (R-1 week) Final 2025.1 Epoxy release: April 2nd, 2025 Project Teams Gathering (virtual): April 7th-11th, 2025 -- Thierry Carrez (ttx)

1 0

[openstack-helm] Inquiry: OpenStack-Helm Deployment in Production Environments
by Thamanna Farhath 07 Mar '25

07 Mar '25

Hello OpenStack Community, I hope this email finds you well. I am currently exploring OpenStack-Helm for deploying OpenStack and would like to understand its adoption in live production environments. Specifically, I am interested in knowing if any cloud providers have successfully deployed and are operating OpenStack using OpenStack-Helm in production. If there are any case studies, references, or experiences shared by operators who have implemented this deployment method, I would greatly appreciate any insights or guidance. Looking forward to your valuable input. 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 5

SRIOV on 2024.1 caracal
by Manohar Kundapura (makundap) 07 Mar '25

07 Mar '25

Hi Everyone, I have the 2024.1 Caracal multi node setup working. Now I am trying to enable SRIOV on this setup by following the below link, https://docs.openstack.org/neutron/2024.1/admin/config-sriov.html Observing the below issue while running the “neutron-sriov-agent” service on compute node and it is restarting on every 2 seconds. Kindly let me know if I need to enable any configs specific to “neutron-sriov-agent” service. # tail -f /var/log/neutron/neutron-sriov-agent.log 2025-03-06 15:02:42.968 9311 INFO neutron.common.config [-] Logging enabled! 2025-03-06 15:02:42.969 9311 INFO neutron.common.config [-] /usr/bin/neutron-sriov-nic-agent version 24.0.0 2025-03-06 15:02:42.969 9311 DEBUG neutron.common.config [-] command line: /usr/bin/neutron-sriov-nic-agent --config-file=/etc/neutron/neutron.conf --config-file=/etc/neutron/plugins/ml2/sriov_agent.ini --log-file=/var/log/neutron/neutron-sriov-agent.log setup_logging /usr/lib/python3/dist-packages/neutron/common/config.py:123 2025-03-06 15:02:42.970 9311 DEBUG neutron.agent.common.utils [-] Std library socket module is patched by eventlet. Requesting std library socket module from eventlet. __init__ /usr/lib/python3/dist-packages/neutron/agent/common/utils.py:91 2025-03-06 15:02:42.971 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Physical Devices mappings: {'vf_inside': ['enp216s0f0'], 'vf_outside': ['enp216s0f1']} 2025-03-06 15:02:42.971 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Exclude Devices: {} 2025-03-06 15:02:42.972 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Resource provider bandwidths: {} 2025-03-06 15:02:42.972 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Resource provider inventory defaults: {'allocation_ratio': 1.0, 'min_unit': 1, 'step_size': 1, 'reserved': 0} 2025-03-06 15:02:42.972 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [-] Resource provider hypervisors: {'enp216s0f1': 'u36c01p06-ostest-cmp2.openstack.local', 'enp216s0f0': 'u36c01p06-ostest-cmp2.openstack.local'} 2025-03-06 15:02:42.973 9311 DEBUG neutron.plugins.ml2.drivers.mech_sriov.agent.eswitch_manager [-] Number of VFs configured on device enp216s0f0: 8 get_numvfs /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/eswitch_manager.py:134 2025-03-06 15:02:42.973 9311 DEBUG neutron.plugins.ml2.drivers.mech_sriov.agent.eswitch_manager [-] Number of VFs configured on device enp216s0f1: 8 get_numvfs /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/eswitch_manager.py:134 2025-03-06 15:02:42.976 9311 DEBUG neutron.agent.securitygroups_rpc [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Init firewall settings (driver=noop) init_firewall /usr/lib/python3/dist-packages/neutron/agent/securitygroups_rpc.py:124 2025-03-06 15:02:42.976 9311 INFO neutron.plugins.ml2.drivers.mech_sriov.agent.sriov_nic_agent [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] RPC agent_id: nic-switch-agent.u36c01p06-ostest-cmp2 2025-03-06 15:02:42.981 9311 INFO neutron.agent.agent_extensions_manager [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Loaded agent extensions: [] 2025-03-06 15:02:43.037 9311 WARNING oslo.messaging._drivers.impl_rabbit [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true': amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.038 9311 INFO oslo.messaging._drivers.impl_rabbit [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] [7d2d8221-cd72-4203-b717-46c9d4fac7a9] Retrying to declare the exchange (q-agent-notifier-port-update_fanout) as non durable 2025-03-06 15:02:43.041 9311 ERROR oslo.messaging._drivers.impl_rabbit [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Failed to declare consumer for topic 'q-agent-notifier-port-update': Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true': amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.046 9311 ERROR oslo.messaging._drivers.impl_rabbit [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Unable to connect to AMQP server on 10.10.4.19:5671 after inf tries: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true': amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 CRITICAL neutron [None req-617911dd-c075-4154-967b-a8ad1c334d34 - - - - - -] Unhandled error: oslo_messaging.exceptions.MessageDeliveryFailure: Unable to connect to AMQP server on 10.10.4.19:5671 after inf tries: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 ERROR neutron Traceback (most recent call last): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 421, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron self.queue.declare() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 605, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron self._create_exchange(nowait=nowait, channel=channel) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 612, in _create_exchange 2025-03-06 15:02:43.047 9311 ERROR neutron self.exchange.declare(nowait=nowait, channel=channel) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 180, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron return (channel or self.channel).exchange_declare( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/channel.py", line 612, in exchange_declare 2025-03-06 15:02:43.047 9311 ERROR neutron self.send_method( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 66, in send_method 2025-03-06 15:02:43.047 9311 ERROR neutron return self.wait(wait, returns_tuple=returns_tuple) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 86, in wait 2025-03-06 15:02:43.047 9311 ERROR neutron self.connection.drain_events(timeout=timeout) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 522, in drain_events 2025-03-06 15:02:43.047 9311 ERROR neutron while not self.blocking_read(timeout): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 528, in blocking_read 2025-03-06 15:02:43.047 9311 ERROR neutron return self.on_inbound_frame(frame) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/method_framing.py", line 53, in on_frame 2025-03-06 15:02:43.047 9311 ERROR neutron callback(channel, method_sig, buf, None) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 534, in on_inbound_method 2025-03-06 15:02:43.047 9311 ERROR neutron return self.channels[channel_id].dispatch_method( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 143, in dispatch_method 2025-03-06 15:02:43.047 9311 ERROR neutron listener(*args) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/channel.py", line 281, in _on_close 2025-03-06 15:02:43.047 9311 ERROR neutron raise error_for_code( 2025-03-06 15:02:43.047 9311 ERROR neutron amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 ERROR neutron 2025-03-06 15:02:43.047 9311 ERROR neutron During handling of the above exception, another exception occurred: 2025-03-06 15:02:43.047 9311 ERROR neutron 2025-03-06 15:02:43.047 9311 ERROR neutron Traceback (most recent call last): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1036, in ensure 2025-03-06 15:02:43.047 9311 ERROR neutron ret, channel = autoretry_method() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/connection.py", line 524, in _ensured 2025-03-06 15:02:43.047 9311 ERROR neutron return fun(*args, **kwargs) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/connection.py", line 600, in __call__ 2025-03-06 15:02:43.047 9311 ERROR neutron return fun(*args, channel=channels[0], **kwargs), channels[0] 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1025, in execute_method 2025-03-06 15:02:43.047 9311 ERROR neutron method() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1262, in _declare_consumer 2025-03-06 15:02:43.047 9311 ERROR neutron consumer.declare(self) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 431, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron self._declare_fallback(err, conn, consumer_arguments) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 396, in _declare_fallback 2025-03-06 15:02:43.047 9311 ERROR neutron self.queue.declare() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 605, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron self._create_exchange(nowait=nowait, channel=channel) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 612, in _create_exchange 2025-03-06 15:02:43.047 9311 ERROR neutron self.exchange.declare(nowait=nowait, channel=channel) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/kombu/entity.py", line 180, in declare 2025-03-06 15:02:43.047 9311 ERROR neutron return (channel or self.channel).exchange_declare( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/channel.py", line 612, in exchange_declare 2025-03-06 15:02:43.047 9311 ERROR neutron self.send_method( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 66, in send_method 2025-03-06 15:02:43.047 9311 ERROR neutron return self.wait(wait, returns_tuple=returns_tuple) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 86, in wait 2025-03-06 15:02:43.047 9311 ERROR neutron self.connection.drain_events(timeout=timeout) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 522, in drain_events 2025-03-06 15:02:43.047 9311 ERROR neutron while not self.blocking_read(timeout): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 528, in blocking_read 2025-03-06 15:02:43.047 9311 ERROR neutron return self.on_inbound_frame(frame) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/method_framing.py", line 53, in on_frame 2025-03-06 15:02:43.047 9311 ERROR neutron callback(channel, method_sig, buf, None) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/connection.py", line 534, in on_inbound_method 2025-03-06 15:02:43.047 9311 ERROR neutron return self.channels[channel_id].dispatch_method( 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/abstract_channel.py", line 143, in dispatch_method 2025-03-06 15:02:43.047 9311 ERROR neutron listener(*args) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/amqp/channel.py", line 281, in _on_close 2025-03-06 15:02:43.047 9311 ERROR neutron raise error_for_code( 2025-03-06 15:02:43.047 9311 ERROR neutron amqp.exceptions.PreconditionFailed: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 ERROR neutron 2025-03-06 15:02:43.047 9311 ERROR neutron During handling of the above exception, another exception occurred: 2025-03-06 15:02:43.047 9311 ERROR neutron 2025-03-06 15:02:43.047 9311 ERROR neutron Traceback (most recent call last): 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/bin/neutron-sriov-nic-agent", line 10, in <module> 2025-03-06 15:02:43.047 9311 ERROR neutron sys.exit(main()) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/cmd/eventlet/plugins/sriov_nic_neutron_agent.py", line 27, in main 2025-03-06 15:02:43.047 9311 ERROR neutron agent_main.main() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py", line 568, in main 2025-03-06 15:02:43.047 9311 ERROR neutron agent = SriovNicSwitchAgent(device_mappings, 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py", line 181, in __init__ 2025-03-06 15:02:43.047 9311 ERROR neutron self.connection.consume_in_threads() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/rpc.py", line 345, in consume_in_threads 2025-03-06 15:02:43.047 9311 ERROR neutron server.start() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 267, in wrapper 2025-03-06 15:02:43.047 9311 ERROR neutron states[state].run_once(lambda: fn(self, *args, **kwargs), 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 188, in run_once 2025-03-06 15:02:43.047 9311 ERROR neutron post_fn = fn() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 267, in <lambda> 2025-03-06 15:02:43.047 9311 ERROR neutron states[state].run_once(lambda: fn(self, *args, **kwargs), 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 413, in start 2025-03-06 15:02:43.047 9311 ERROR neutron self.listener = self._create_listener() 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/server.py", line 150, in _create_listener 2025-03-06 15:02:43.047 9311 ERROR neutron return self.transport._listen(self._target, 1, None) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/transport.py", line 142, in _listen 2025-03-06 15:02:43.047 9311 ERROR neutron return self._driver.listen(target, batch_size, 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 709, in listen 2025-03-06 15:02:43.047 9311 ERROR neutron conn.declare_fanout_consumer(target.topic, listener) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1398, in declare_fanout_consumer 2025-03-06 15:02:43.047 9311 ERROR neutron self.declare_consumer(consumer) 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1273, in declare_consumer 2025-03-06 15:02:43.047 9311 ERROR neutron return self.ensure(_declare_consumer, 2025-03-06 15:02:43.047 9311 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_messaging/_drivers/impl_rabbit.py", line 1058, in ensure 2025-03-06 15:02:43.047 9311 ERROR neutron raise exceptions.MessageDeliveryFailure(msg) 2025-03-06 15:02:43.047 9311 ERROR neutron oslo_messaging.exceptions.MessageDeliveryFailure: Unable to connect to AMQP server on 10.10.4.19:5671 after inf tries: Exchange.declare: (406) PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'q-agent-notifier-port-update_fanout' in vhost 'neutron': received 'false' but current is 'true' 2025-03-06 15:02:43.047 9311 ERROR neutron Thanks, Manohar

3 2

[neutron] Drivers meeting canceled Friday, March 7th
by Brian Haley 06 Mar '25

06 Mar '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as discussed at this week's team meeting, since we are past feature freeze and should be focusing on getting in-flight things merged and bug fixes. Just a reminder there are still open specs that need review, list is at [0]. And just a reminder I am offline until next Tuesday. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

[openstack-helm] Are there any real users of the umbrella chart?
by Vladimir Kozhukalov 06 Mar '25

06 Mar '25

Hi team, This is to start the discussion about the future of the Openstack super (umbrella) chart [1]. My personal impression (maybe I am wrong) is that this chart is of extremely little interest. We continue to maintain this code (and spend testing resources) but maybe there are no real users of it. The chart deploys a compute-kit scheme but the same result can be achieved if one deploys multiple separate charts one-by-one. It seems convenient to have this single super chart that deploys Openstack with a single command, but IMO even small operators prefer using separate charts. Having said that, I would suggest removing this chart if it is not needed. [1] https://opendev.org/openstack/openstack-helm/src/branch/master/openstack -- Best regards, Kozhukalov Vladimir

3 2

Assistance Required: OpenStack Helm Deployment (Version 2023.1) Compatibility Issues
by Thamanna Farhath 05 Mar '25

05 Mar '25

Hello OpenStack Community, I hope you are doing well. I am currently deploying OpenStack on top of a Kubernetes cluster using OpenStack Helm and aiming to install the 2023.1 (Antelope) version. However, I am facing difficulties in installing this specific version via Helm charts. Despite my attempts, I have not been able to successfully deploy the required OpenStack services for this release. Additionally, I am ensuring that the dependent services, such as RabbitMQ, align with the compatibility requirements of OpenStack 2023.1. As per the OpenStack documentation, RabbitMQ 3.11 is the recommended version, but I encountered issues while deploying it. Instead, I found that RabbitMQ 3.12 works without any issues. I would like to know: Is there a way to install OpenStack 2023.1 properly using Helm charts, or should I consider using a newer OpenStack version? Will using RabbitMQ 3.12 instead of 3.11 cause any potential issues with OpenStack services, or is it safe to proceed with this version? Are there any known workarounds or recommendations for deploying OpenStack 2023.1 using Helm? I would appreciate any guidance, best practices, or documentation references that could help resolve these challenges. Looking forward to your valuable insights. 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 6

[nova][libvirt][qemu] Internal error: process exited while connecting to monitor
by Roby G 04 Mar '25

04 Mar '25

Hello everyone, After upgrading to Antelope i´m getting following errors when creating new volume-backed instance. Volumes are stored in a ceph pool. - nova: 27.4.0 - libvirt: 8.0.0 - qemu: 6.2.0 - Operating system: Ubuntu 22.04 ``` ERROR nova.virt.libvirt.driver [instance: f8fa30f3-3dc8-43bd-bc29-8ed23b15b1f2] Failed to start libvirt guest: libvirt.libvirtError: internal error: process exited while connecting to monitor: 2025-03-04T15:15:34.416946Z qemu-system-x86_64: -blockdev {"driver":"rbd","pool":"cinder","image":"volume-6dfe3084-ef9d-4107-8b69-b0036fefbed0","server":[{"host":"1.2.3.4","port":"1234"},{"host":"1.2.3.5","port":"1234"},{"host":"1.2.3.6","port":"1234"}],"user":"cinder","auth-client-required":["cephx","none"],"key-secret":"libvirt-1-storage-auth-secret0","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}: error connecting: Permission denied libvirtd[50229]: internal error: process exited while connecting to monitor: 2025-03-04T15:15:34.416946Z qemu-system-x86_64: -blockdev {"driver":"rbd","pool":"cinder","image":"volume-6dfe3084-ef9d-4107-8b69-b0036fefbed0","server":[{"host":"1.2.3.4","port":"1234"},{"host":"1.2.3.5","port":"1234"},{"host":"1.2.3.6","port":"1234"}],"user":"cinder","auth-client-required":["cephx","none"],"key-secret":"libvirt-1-storage-auth-secret0","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}: error connecting: Permission denied libvirtd[50229]: internal error: qemu unexpectedly closed the monitor: 2025-03-04T15:15:34.416946Z qemu-system-x86_64: -blockdev {"driver":"rbd","pool":"cinder","image":"volume-6dfe3084-ef9d-4107-8b69-b0036fefbed0","server":[{"host":"1.2.3.4","port":"1234"},{"host":"1.2.3.5","port":"1234"},{"host":"1.2.3.6","port":"1234"}],"user":"cinder","auth-client-required":["cephx","none"],"key-secret":"libvirt-1-storage-auth-secret0","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}: error connecting: Permission denied os-cmt7 libvirtd[50229]: Unable to read from monitor: Connection reset by peer ``` Any fixes/tips? From The compute node accessing the ceph pool using `rbd` client, there are no permission errors. Are this errors related to qemu monitor?

1 0

PTG April 2025 Teams List
by Kendall Nelson 04 Mar '25

04 Mar '25

Hello Everyone! The list of teams participating in the upcoming virtual PTG (April 7-11, 2025) is now official! Projects + Teams - OpenInfra Foundation Teams - - OpenInfra Diversity and Inclusion Working Group - Kata Containers - OpenStack - - Services - - Blazar - Cinder - CloudKitty - Designate - Glance - Heat - Horizon - Ironic - Keystone - Kolla - Manila - Neutron - Nova - Octavia - OpenStack-Ansible - OpenStack SDK/CLI - Sunbeam - Swift - Tacker - Watcher - Other OpenStack Teams - Eventlet Removal - i18n SIG - OpenStack for AI Working Group - OpenStack Security SIG - OpenStack Technical Committee - Public Cloud SIG - VMware Migration Working Group - StarlingX - Adjacent Open Source Communities - - OceanBase If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign up for time via the PTGBot[1] once it is configured for the teams that are signed up to attend the event. Etherpads for agenda planning and note taking will be automatically generated as a part of that configuration. Otherwise, please don't forget to register[2] — it's FREE! Also, it does help us with event coordination and communication, so please take a moment to register. As usual, feel free to let me know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://opendev.org/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: http://ptg.openinfra.org/

1 0

[neutron] LXB Removal and OVN migration
by Ricardo Cano 04 Mar '25

04 Mar '25

Hello openstack-discuss, With the removal of the linuxbridge mechanism driver, has anyone successfully completed an in-place migrationfrom LinuxBridge to OVN? I did come across this https://www.jimmdenton.com/migrating-lxb-to-ovn/ and that looks good as a one-shoit while biting the bullet and taking a full outage. However, I was wondering if it was possible to run lxb and ovn side-by-side and cut them over, say one network at a time. This particular deployment was stood up using openstack-ansible back in the rocky days (now running antelope) and it appears that openstack ansible'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?

7 8

LXB Removal and OVN migration
by Ricardo Cano 04 Mar '25

04 Mar '25

Hello openstack-discuss, With the removal of the linuxbridge mechanism driver, has anyone successfully completed an in-place migrationfrom LinuxBridge to OVN? I did come across this https://www.jimmdenton.com/migrating-lxb-to-ovn/ and that looks good as a one-shoit while biting the bullet and taking a full outage. However, I was wondering if it was possible to run lxb and ovn side-by-side and cut them over, say one network at a time. This particular deployment was stood up using openstack-ansible back in the rocky days (now running antelope) and it appears that openstack ansible'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?

2 1

Contributing to Openstack [Looking for Mentorship]
by jb03229422＠student.ku.edu.np 04 Mar '25

04 Mar '25

Dear Mentors, I have good experience in building openstack in multiple environments bare-metal, kolla-ansible and helm project for minimal deployment to good HA clusters. Now, I'm looking to get into code level and contribute to open-infra foundation. I'm not a someone beginner to coding, I have done programming in a good amount and hold a knowledge of paradigm and principles. Here's my github: https://github.com/jamesii-b I'm looking for mentor who can guide me what to do as a Contribution.. Even deploying first openstack is overwhelming on its own, Coding is more. Please have me. Trust me, I'll have utmost respect to your time and energy and get most of it. Knowledge I have: HPC, Openstack Deployment, Network & System, Parallel Programming, Python, Rust.

2 1

[tacker] Today's weekly meeting
by Yasufumi Ogawa 03 Mar '25

03 Mar '25

Hi tacker team, I might not be able to join today's meeting due to something urgent come up. Let me join the today's discussion by adding my comment on the etherpad later. Thanks, Yasufumi

1 0

[neutron] Bug deputy report for week of February 24th
by Brian Haley 03 Mar '25

03 Mar '25

Hi, I was the Neutron bug deputy last week. Below is a short summary about the reported bugs. -Brian Critical bugs ------------- * None High bugs --------- * https://bugs.launchpad.net/neutron/+bug/2100001 - [FT] Random errors in ``test_server.TestPluginWorker.test_start`` - https://review.opendev.org/c/openstack/neutron/+/942798 * https://bugs.launchpad.net/neutron/+bug/2100261 - [FT] Consistent errors in ``neutron-functional-with-pyroute2-master`` CI job - https://github.com/svinota/pyroute2/issues/1181 might be related - Rodolfo took ownership * https://bugs.launchpad.net/neutron/+bug/2100270 - [whitebox-neutron-tempest-plugin] Missing method ``configure_vlan_transparent`` imported from neutron-tempest-plugin - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/942776 * https://bugs.launchpad.net/neutron/+bug/2099981 - [ovn] Adding an IPv6 subnet to public network breaks all FIPs - Still trying to reproduce * https://bugs.launchpad.net/neutron/+bug/2099982 - [ovn] Removal of IPv6 subnet from the public network is not reflected in LRs - Might be related to above OVN bug 2099981 * https://bugs.launchpad.net/neutron/+bug/2100294 - [ovn] Changing gateway for IPv6 subnet updates wrong routes family - Might be related to above OVN bug 2099982 Medium ------ * https://bugs.launchpad.net/neutron/+bug/2099911 - Castellan as config source fails with "greenlet.error: cannot switch to a different thread" - https://review.opendev.org/c/openstack/neutron/+/942622 - But don't think that might be necessary with us removing eventlet * https://bugs.launchpad.net/neutron/+bug/2100505 - Neutron OVN external ports creation change HA chassis group master - FT reproducer patch confirms issue - Needs owner Low --- * https://bugs.launchpad.net/neutron/+bug/2100479 - Segments plugin: Not updating used IP addresses - https://review.opendev.org/c/openstack/neutron/+/935990 might fix? Wishlist -------- * https://bugs.launchpad.net/neutron/+bug/2099896 - [eventlet-removal] Remove the usage of eventlet in the Metadata agent - Needs owner * https://bugs.launchpad.net/neutron/+bug/2100268 - cleanup os-ken from the CLI part - Needs owner * https://bugs.launchpad.net/neutron/+bug/2100585 - [metadata] Unify metadata code - Eventlet follow-up

1 0

[manila] March 6th weekly meeting cancelled
by Carlos Silva 03 Mar '25

03 Mar '25

Hello zorillas, As a big part of our audience will not be able to join this week's weekly meeting, we are cancelling it. In case you have something to bring up, please ping on IRC. We will resume our upstream weekly meetings on March 13th. Thank you, carloss

1 0

Installation guide: service_user_token clarification
by Eugen Block 03 Mar '25

03 Mar '25

Hi *, to me it's still a bit unclear, what exactly is required to properly set up service user tokens. The Yoga release notes point to the nova configuration guide [0], which only briefly describes the concept. But looking at the latest installation guide [1], there's also only a very short section with a link to the config page. But there's no mention of a service role that has to be created. If this is the default since Yoga, shouldn't the installation guides cover the entire process, including creating all necessary roles or the [keystone_authtoken] section that should probably contain "service_token_roles = service"? I currently find it quite confusing. Thanks! Eugen [0] https://docs.openstack.org/nova/latest/admin/configuration/service-user-tok… [1] https://docs.openstack.org/nova/2024.2/install/controller-install-ubuntu.ht…

1 0

[release][PTLs] Reminder to 2025.1 Epoxy Cycle highlights
by Elõd Illés 03 Mar '25

03 Mar '25

Hi, This is a gentle reminder that this week is the week when 2025.1 Epoxy's Cycle highlights should be finalized (now that the Feature Freeze deadline has passed) so that they can be included in release marketing preparations. Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

Problems with Cinder and iSCSI
by Alexander Luedtke 02 Mar '25

02 Mar '25

Hello Everyone, I have a really strange problem with iSCSI, Cinder, Kolla setup. 1. What I want to do: I did setup with kolla 1 Controller, 4 Compute nodes and 2 storage nodes (iSCSI, Cinder, LVM). Kolla Deploying works fine, all Machines can find all others. 2. Problem: happens when I try to create an instance * Im creating an new instance what fails because the cinder volume couldn't be "mounted" on the compute node * What I checked then: o storage2 (the 2. cinder iscsi storage node) is available (by ping ) from the compute node o Port 3260 on storage2 is not reachable from compute node o so checking storage2 + the volume was created on LVM (checked with lvs) + Port 3260 is not available local too + it looks like that cinder creates an iSCSI target and deletes it after some seconds ... no reason shown (I activated debug mode in Kolla in the hope to see more but no ...) Did anyone have some similar behavior or can give me a hint where else to look ? Thanks a lot for your help ! best Alex Logfile of the storage2 node /var/log/kolla/cinder/cinder-volume.log: the following lines came 5-6 times and then nothing more. 2025-03-03 08:17:02.625 42 DEBUG cinder.volume.drivers.lvm [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Updating volume stats _update_volume_stats /var/lib/kolla/venv/lib/python3.12/site-packages/cinder/volume/drivers/lvm.py:227 2025-03-03 08:17:02.626 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C vgs --noheadings --unit=g -o name,size,free,lv_count,uuid --separator : --nosuffix cinder-volumes execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:349 2025-03-03 08:17:03.057 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C vgs --noheadings --unit=g -o name,size,free,lv_count,uuid --separator : --nosuffix cinder-vo lumes" returned: 0 in 0.432s execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:372 2025-03-03 08:17:03.059 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o vg_name,name,size --nosuffix --readonly ci nder-volumes execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:349 2025-03-03 08:17:03.483 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o vg_name,name,size --nosuffix --readonly cinder-volumes" returne d: 0 in 0.425s execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:372 2025-03-03 08:17:03.485 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o size,data_percent --separator : --nosuffix /dev/cinder-volumes/cinder-volumes-pool execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:349 2025-03-03 08:17:03.899 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o size,data_percent --separator : --nosuffix /dev/cinder-volumes/ cinder-volumes-pool" returned: 0 in 0.414s execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:372 2025-03-03 08:17:03.900 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o vg_name,name,size --nosuffix --readonly ci nder-volumes execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:349 2025-03-03 08:17:04.319 42 DEBUG oslo_concurrency.processutils [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C lvs --noheadings --unit=g -o vg_name,name,size --nosuffix --readonly cinder-volumes" returne d: 0 in 0.418s execute /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_concurrency/processutils.py:372 2025-03-03 08:17:04.320 42 DEBUG cinder.manager [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Notifying Schedulers of capabilities ... _publish_service_capabilities /var/lib/kolla/venv/lib/python3.12/site-packages/cinder/manager.py:202 2025-03-03 08:18:02.626 42 DEBUG oslo_service.periodic_task [None req-c3be57e8-eeac-4b14-99c7-f3f10474a3cf - - - - - -] Running periodic task VolumeManager.publish_service_capabilities run_periodic_tasks /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_service/periodic_task. py:210

1 0