August 2024 - openstack-discuss - lists.openstack.org

[neutron] Bug deputy report - week of Aug 5
by Slawek Kaplonski 11 Aug '24

11 Aug '24

Hi, I was bug deputy this week. It was a pretty quiet week. Here is a summary of the new bugs reported: *Critical* - https://bugs.launchpad.net/neutron/+bug/2076430 - rally job broken with recent keystone change and fails with ValueError: Cannot convert datetime.date(2024, 8, 7) to primitive - not assigned yet but it seems that gtema, xek and ykarel are taking care of it already *High* - https://bugs.launchpad.net/neutron/+bug/2076328 -SubnetsSearchCriteriaTest.test_list_pagination_page_reverse_with_href_links fails sporadically - *not assigned yet*, seems like intermittent gate failure, it was marked as Low by Lajos but as it is causing gate failures, I changed it to *High* - https://bugs.launchpad.net/neutron/+bug/2076405 - # neutron-fwaas stable/2023.1 periodic jobs are failing, assigned to Lajos, fix already proposed and merged https://review.opendev.org/c/openstack/neutron-fwaas/+/926047 *Low* - https://bugs.launchpad.net/neutron/+bug/2076181 - Accidentally no-allocation-pool for subnet leads to poor diagnosis of build-in dhcp service issues - *not assigned*, marked as low-hanging-fruit as the only thing which would be needed here is just improve exception message slightly *RFE* - https://bugs.launchpad.net/neutron/+bug/2076122 - dns integration: support multiple domains per instance -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[oslo] Feature freeze is apporching
by Daniel Bengtsson 09 Aug '24

09 Aug '24

Hi there, Just a friendly reminder that oslo's feature freeze[1] will happen. Oslo observes a feature freeze that is earlier than other projects. And it's coming up soon. Aug. 15th is the Oslo feature freeze date for this cycle. That leaves about one week for features to be merged in Oslo libraries. After that, any features to be merged will require a feature freeze exception, which can be requested on the list. Feel free to ping us on IRC if you need code review. [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… -- Daniel Bengtsson Software Engineer

1 0

What is the expected behaviour of openstack user with reader access ?
by abitha.ramu32＠gmail.com 09 Aug '24

09 Aug '24

I have created new user with reader access, As expected it was supposed to view the resources created in openstack. but the user with reader access can create/update/modify the resource

2 1

[release] Release countdown for week R-7
by Thierry Carrez 09 Aug '24

09 Aug '24

Development Focus ----------------- We are entering the last weeks of the 2024.2 "Dalmatian" development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-AC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Contributor and allowed to vote. This is done by adding extra-acs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-AC freeze on August 15th, 2024. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, August 15th, 2024. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 22nd, 2024). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (August 29th, 2024) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, August 29th, 2024. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before the end of the RC1 target week (September 13, 2024) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 26, 2024) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to one week after Feature freeze (September 5th, 2024). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… jeremy [at] openstack.org/fungi on IRC is available if you need help selecting or writing your highlights. Upcoming Deadlines & Dates -------------------------- Extra-AC freeze: August 15th, 2024 (R-7 week) Oslo feature freeze: August 15th, 2024 (R-7 week) Non-client library freeze: August 22nd, 2024 (R-6 week) Client library freeze: August 29th, 2024 (R-5 week) Dalmatian-3 milestone: August 29th, 2024 (R-5 week) Cycle highlights deadline: September 5th, 2024 (R-4 week) -- Thierry Carrez (ttx)

1 0

[Glance] Cancelling Weekly Meeting (Aug 8)
by Pranali Deore 08 Aug '24

08 Aug '24

Hello, I'm not feeling well, won't be able to chair today's meeting, so cancelling the same. See you next week! Thanks, Pranali Deore

1 0

Deployment Caracal with OVN not working (same test setup with Bobcat runs perfectly)
by Maurer Remo (murm) 07 Aug '24

07 Aug '24

Dear all I'm running multiple Openstack production clusters for years. Currently, our clusters hold approx 600 instances mainly for educational purposes. We're deploying the environment using Kolla-Ansible. Host OS Ubuntu Jammy, using the Jammy-Kolla containers. At the moment we're running Bobcat and are testing the Upgrade to Caracal (2024.1). To make the problem reproduceable I set up a one node testenvironment. Host OS: Ubuntu Jammy running on KVM. Kolla-Ansible Version: 18.1.1.dev1 Ansible-Version: 9.8.0 (ansible-core 2.16.9) Kolla config: * passwords.yml from caracal template, values filled in with kolla-genpwd * multinode from caracal template. Control, network and compute node set to the hostname of the testserver. Everything else left as is. * globals.yml from caracal template. Changes (I'm not listing the network config entries): * kolla_base_distro: "ubuntu" * neutron_plugin_agent: "ovn" Deployment runs smoothly. Post deploy tests: * "openstack compute service list", shows all services up (nova-scheduler, nova-conductor, nova-compute) * "openstack network agent list", shows all network agents up (OVN Controller Gateway agent, OVN Metadata agent) To setup network, flavors, etc, I'm running an adapted init_runonce script, creating an external (flat) and an internal (geneve) network and a router. Spinning up an instance leads to a fatal error on nova: --- Dashboard --- Error: Failed to perform requested operation on instance "test", the instance has an error status: Please try again later [Error: Build of instance 38488604-3d83-4676-b0c2-a4218696eba3 aborted: Failed to allocate the network(s), not rescheduling.]. --- --- /var/log/kolla/nova/nova-compute.log --- ... 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [None req-14f0d15f-5892-406b-a750-698ec54d9b70 ec93e00940164f30b5076a93c0a24722 499b452a194d4cbeb401302eaef1304a - - default default] [instance: 38488604-3d83-4676-b0c2-a4218696eba3] Instance failed to spawn: nova.exception.VirtualInterfaceCreateException: Virtual Interface creation failed 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] Traceback (most recent call last): 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/virt/libvirt/driver.py", line 8002, in _create_guest_with_network 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] with self.virtapi.wait_for_instance_event( 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/usr/lib/python3.10/contextlib.py", line 142, in __exit__ 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] next(self.gen) 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/compute/manager.py", line 559, in wait_for_instance_event 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] self._wait_for_instance_events( 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/compute/manager.py", line 471, in _wait_for_instance_events 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] actual_event = event.wait() 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/compute/manager.py", line 436, in wait 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] instance_event = self.event.wait() 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/eventlet/event.py", line 124, in wait 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] result = hub.switch() 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/eventlet/hubs/hub.py", line 310, in switch 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] return self.greenlet.switch() 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] eventlet.timeout.Timeout: 300 seconds 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] During handling of the above exception, another exception occurred: 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] Traceback (most recent call last): 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/compute/manager.py", line 2885, in _build_resources 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] yield resources 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/compute/manager.py", line 2632, in _build_and_run_instance 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] self.driver.spawn(context, instance, image_meta, 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/virt/libvirt/driver.py", line 4642, in spawn 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] self._create_guest_with_network( 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/virt/libvirt/driver.py", line 8028, in _create_guest_with_network 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] raise exception.VirtualInterfaceCreateException() 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] nova.exception.VirtualInterfaceCreateException: Virtual Interface creation failed 2024-08-07 15:33:02.742 7 ERROR nova.compute.manager [instance: 38488604-3d83-4676-b0c2-a4218696eba3] 2024-08-07 15:33:02.753 7 INFO nova.compute.manager [None req-14f0d15f-5892-406b-a750-698ec54d9b70 ec93e00940164f30b5076a93c0a24722 499b452a194d4cbeb401302eaef1304a - - default default] [instance: 38488604-3d83-4676-b0c2-a4218696eba3] Terminating instance ... --- The same configuration works without error under Bobcat (kolla-ansible: 17.4.0, ansible: 8.4.0) When I upgrade a running Bobcat configuration to Caracal, I run into the same issue. When running the upgrade with "--skip-tags openvswitch" the upgraded environment runs perfectly (with the bobcat openvswitch containers). As soon as I upgrade those, the deployment is broken again. I clouldn't find a bug on launchpad which points to this issue. I coudn't find any info in the release notes of caracal which solves my problem. Does anyone struggling on the same issue as well? Do you have any hint? I'm appreciating any comment, help, ... Thanks Remo Maurer

2 1

[oslo][freezer][watcher][requirement][release] Resetting the DPL model liaisons
by Ghanshyam Mann 06 Aug '24

06 Aug '24

Hi, DPL projects, To keep the DPL model/liaisons up to date, TC defined the new policy to reset the DPL state/liaisons every cycle[1]. If the project wants to continue the DPL model, they can opt-in the same; otherwise, they fall into the PTL model/election process. I am resetting the DPL model for all the existing 5 DPL projects[2]. If needed, feel free to opt-in the DPL model for the next cycle. [1] https://governance.openstack.org/tc/reference/distributed-project-leadershi… [2] this series - https://review.opendev.org/c/openstack/governance/+/925834/1 -gmann

1 0

Firewall as a Service - kolla ansible 2023.1
by Thamanna Farhath 06 Aug '24

06 Aug '24

Hello OpenStack Community, I hope this message finds you well. My name is Thamanna , and I am currently working with the OpenStack Kolla-Ansible deployment version 2023.1. I am interested in deploying Firewall as a Service (FWaaS) within our OpenStack environment. However, I have noticed that FWaaS is not available in the Kolla-Ansible 2023.1 version. Could anyone please provide guidance on the following points? 1. Is there an official or recommended way to integrate FWaaS with Kolla-Ansible 2023.1? 2. Are there any specific configurations or additional components required to enable FWaaS? 3. Has anyone in the community successfully deployed FWaaS with this version, and if so, could you share your experience and any potential challenges faced? 4. Are there alternative approaches or tools that you would recommend for deploying FWaaS in an OpenStack environment? Any help or pointers to relevant documentation would be greatly appreciated. Thank you in advance for your assistance! Best regards, Thamanna mailto:thamanna.f@zybisys.com 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."

3 5

Live migration fails
by Szabo, Istvan (Agoda) 06 Aug '24

06 Aug '24

Hi, I have couple of compute nodes where the live migration fails with existing vms. When I quickly spawn a vm and try live migration it works so I assume shouldn't be a big problem with the compute node. However I have many existing vms where it fails with a servername not found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 ERROR nova.conductor.tasks.migrate [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Unable to find record for source node servername on servername: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Failed to compute_task_migrate_server: Compute host servername could not be found.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Setting instance to ACTIVE state.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.672 227612 ERROR oslo_messaging.rpc.server [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Exception during message handling: ComputeHostNotFound: Compute host am-osfecn-4025 Tried with this command: nova live-migration --block-migrate id. Any idea? Thank you. ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 16

nova db queries
by engineer2024 06 Aug '24

06 Aug '24

Hi, I am trying to execute a query on nova db in a custom code file in nova. During the execution of a function like 'instance_get_all_by_filters_sort' from nova/db/main/api.py , I see this --- try: query_prefix = sqlalchemyutils.paginate_query( query_prefix, models.Instance, limit, sort_keys, marker=marker, sort_dirs=sort_dirs, ) except db_exc.InvalidSortKey: raise exception.InvalidSortKey() instances = query_prefix.all() --- So, my question is how does query_prefix.all() know the mysql db connection url to connect to for executing the query ? Thanks elinux

2 1