May 2024 - openstack-discuss - lists.openstack.org

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

11 Apr '25

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

4 6

[tc][all][monasca ] Retiring the Monasca project
by Ghanshyam Mann 16 Feb '25

16 Feb '25

Hello everyone, As you might know, the Monasca project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Monasca retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

6 17

[ironic]About the OS supported by Diskimage-builder
by Junya Noguchi (Fujitsu) 03 Feb '25

03 Feb '25

To whom it may concern. My name is Junya Noguchi. I have some questions about the supported OS for Diskimage-builder operation. Please respond. References https://docs.openstack.org/ironic-python-agent-builder/latest/admin/dib.html Does it mean that the OS that says "work but receive only limited testing and support" works but is not supported? References https://docs.openstack.org/diskimage-builder/latest/ This document describes RHEL and other operating systems that are not supported in the previous question. Are these operating systems supported? Also, are there any plans to support more operating systems in the future? Best regards, Junya Noguchi

5 7

[glance][ops] proposal to remove the glance-scrubber
by Brian Rosmaita 19 Jan '25

19 Jan '25

Hello Glance users, The Glance project team wants to determine whether anyone is using the glance-scrubber utility [0]. If not, we are thinking of deprecating it this cycle to be removed in the appropriate future cycle. If you have not previously heard of the glance-scrubber, that's most likely because it's only useful for particular deployment configurations of which yours is not one. See the doc [0] for details if you are curious. Our suspicion is that the glance-scrubber may have outlived its usefulness for modern OpenStack configurations. (The last time I remember it being discussed at a PTG was during the snowstorm in Dublin, which I believe was the Rocky development cycle). On the other hand, the team also has some ideas for improving the scrubber, but there's no point doing that if it's not actually being used in the first place. So if removal of the glance-scrubber would negatively affect you, please respond to this email so we can get some data points. Thanks! [0] https://docs.openstack.org/glance/latest/cli/glancescrubber.html

2 2

[cinder][kubernetes] pvc stuck in reserved state
by Eugen Block 10 Jan '25

10 Jan '25

Hi, we have a couple of k8s clusters in our openstack environment (Victoria) and are facing some problems when pods get moved to different worker nodes. The PVCs get stuck in "reserved" state, and they only get attached after resetting the volumes to "available" state. First I thought it was due to the missing multiattach volume type which seems to work fine in our customer's cluster. I also found the "duplicate connector" error messages in the nova-compute.log: > Unable to update attachment.(Invalid volume: duplicate connectors > detected on volume But after adding the multiattach volume type and retyping the affected volumes, the PVCs still get stuck in "reserved" state while I don't see any error messages on the hypervisors anymore. So it seems that something has changed/improved, but now I don't have a trace where to look next. Could this be a cinder-csi driver issue or something? Our cinder backend is ceph (Pacific). Not sure which information could help so please ask for anything I can provide. Any pointers are highly appreciated! Thanks! Eugen

1 2

ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat.| Openstack tripleo wallaby version
by Swogat Pradhan 23 Dec '24

23 Dec '24

Hi, I am currently trying to deploy openstack wallaby using tripleo arch. I created the network jinja templates, ran the following commands also: #openstack overcloud network provision --stack overcloud --output networks-deployed-environment.yaml custom_network_data.yaml # openstack overcloud network vip provision --stack overcloud --output vip-deployed-environment.yaml custom_vip_data.yaml # openstack overcloud node provision --stack overcloud --overcloud-ssh-key /home/stack/sshkey/id_rsa overcloud-baremetal-deploy.yaml and used the environment files in the openstack overcloud deploy command: (undercloud) [stack@hkg2director ~]$ cat deploy.sh #!/bin/bash THT=/usr/share/openstack-tripleo-heat-templates/ CNF=/home/stack/ openstack overcloud deploy --templates $THT \ -r $CNF/templates/roles_data.yaml \ -n $CNF/workplace/custom_network_data.yaml \ -e ~/containers-prepare-parameter.yaml \ -e $CNF/templates/node-info.yaml \ -e $CNF/templates/scheduler-hints.yaml \ -e $CNF/workplace/networks-deployed-environment.yaml \ -e $CNF/workplace/vip-deployed-environment.yaml \ -e $CNF/workplace/overcloud-baremetal-deployed.yaml \ -e $CNF/workplace/custom-net-bond-with-vlans.yaml Now when i run the ./deploy.sh script i encounter an error stating: ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command.: tripleoclient.exceptions.InvalidConfiguration: Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command. 2022-04-19 13:47:16.582 735924 INFO osc_lib.shell [-] END return value: 1 Can someone tell me where the mistake is? With regards, Swogat Pradhan

4 4

[kolla] [openeuler] CI jobs status
by Michał Nasiadka 26 Nov '24

26 Nov '24

Hello Koalas, OpenEuler jobs in master (to be Antelope) are failing for a long time. If no one is interested in maintaining OpenEuler support in Kolla-Ansible - I will propose dropping it’s support on Wednesday Kolla meeting. Best regards, Michal

4 3

[horizon][ceph] object storage container storage policy missing
by Satish Patel 24 Nov '24

24 Nov '24

Folks, Openstack Release: Zed Recently I have integrated ceph RGW service with openstack/keystone and testing with command line tool "openstack container create foo1" and it works but when I go to Horizon UI I am seeing it doesn't have storage policy dropdown list and because of that I am not able to create container or upload file from Horizon GUI https://ibb.co/KhYW6Rd It works with commands like but not horizon. $ openstack container create foo1 +---------------------------------------+-----------+------------------------------------------------+ | account | container | x-trans-id | +---------------------------------------+-----------+------------------------------------------------+ | AUTH_d4d82849885e4126aef402c408ad2c5c | foo1 | tx00000c057454841b13497-0065b558b4-42ff2eb-ahm | +---------------------------------------+-----------+------------------------------------------------+ $ openstack container list +------+ | Name | +------+ | foo1 | +------+

2 2

[ironic] Having issue with deploying ISO image to node
by James Leong 17 Nov '24

17 Nov '24

Hi all, I am trying to play around with ironic, and I am having an issue with deploying an Ubuntu 20.04 ISO image onto my bare metal node. Since I am quite new to bare metal, I am not entirely sure what went wrong as I couldn't find any error messages shown on my log file (ironic-conductor, ironic-api, ironic_neutron_agent, and nova-compute-ironic). This might be my guess; the ironic inspection is hitting timeout, which is causing the deployment to timeout. However, I have no idea why the inspection is failing at timeout. Any help would be appreciated. Best, James

6 7

[nova][libvirtd] internal error: unable to execute QEMU command 'query-named-block-nodes'
by Satish Patel 22 Oct '24

22 Oct '24

Folks, I have a ceph cluster and recently I configured rbd-mirror to replicate all data to remove ceph cluster for disaster recovery. Yesterday for POC we did a hard cutover on ceph and point openstack to the new cluster. All other vms came back up fine but 2 vms stuck in this error state in libvirt logs 2024-01-31 22:44:37.591+0000: 474597: error : qemuMonitorJSONCheckErrorFull:399 : internal error: unable to execute QEMU command 'query-named-block-nodes': cannot read image start for probe: Permission denied If it's a wider issue than it should impact all the vms but why only two VM stuck and not starting and libvirt giving me this error in logs nova-compute logs also showing same error 2024-01-31 22:44:40.925 7 INFO nova.compute.manager [None req-b33485b5-8740-48ae-8b5b-a440de3f11a4 c48fcfb9347f413f92fcece065644b00 ca5c652478c7429e964257990800e9cb - - default default] [instance: 2de0f880-77c7-4d2c-9e01-898c57ad3693] Successfully reverted task state from powering-on on failure for instance. 2024-01-31 22:44:40.944 7 ERROR oslo_messaging.rpc.server [None req-b33485b5-8740-48ae-8b5b-a440de3f11a4 c48fcfb9347f413f92fcece065644b00 ca5c652478c7429e964257990800e9cb - - default default] Exception during message handling: libvirt.libvirtError: internal error: unable to execute QEMU command 'query-named-block-nodes': cannot read image start for probe: Permission denied

3 8

[kuryr][tc] Final call for Kuryr PTL/DPL liaisons
by Ghanshyam Mann 15 Oct '24

15 Oct '24

Hello Everyone, Kuryr project ends up being a leaderless project for the 2024.2 Dalmatian cycle[1]. There is no volunteer to serve as PTL or DPL liaisons yet. As the next step, I have proposed to mark this project Inactive: - https://review.opendev.org/c/openstack/governance/+/916945 If you would like to serve as a leader and help maintain this project, this is the right time to step up by replying to this email or commenting in gerrit change 916945. [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 Ref: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… -gmann

4 10

Kolla Ansible on Ubuntu 20.04 - cloud-init & other network issues
by Tobias McNulty 10 Oct '24

10 Oct '24

Hi, I'm attempting to use Kolla Ansible 14.6.0 to deploy OpenStack Yoga on a small 3-node Ubuntu 20.04 cluster. The nodes have 128 GB RAM each, dual Xeon processors, and dual 10G Intel NICs. The NICs are connected to access ports on a 10G switch with separate VLANs for the local and external networks. All the playbooks run cleanly, but cloud-init is failing in the Ubuntu 20.04 and 22.04 VMs I attempt to boot. The VM images are unmodified from https://cloud-images.ubuntu.com/, and cloud-init works fine if I mount a second volume with user-data. The error is a timeout attempting to reach 169.254.169.254. This occurs both when booting a VM in an internal routed network and directly in an external network. I tried various neutron plugin agents (ovn, linuxbridge, and openvswitch both with and without firewall_driver = openvswitch <https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutro…>) first with a clean install of the entire OS each time, all with the same result. Running tcpdump looking for 169.254.169.254 shows nothing. As a possible clue, the virtual NICs are unable to pass any traffic (e.g., to reach an external DHCP server) unless I completely disable port security on the interface (even if the associated security group is wide open). But disabling port security does not fix cloud-init (not to mention I don't really want to disable port security). Are there any additional requirements related to deploying OpenStack with Kolla on Ubuntu 20.04? This is a fairly vanilla configuration using the multinode inventory as a starting point. I tried to follow the Quick Start <https://docs.openstack.org/kolla-ansible/yoga/user/quickstart.html> as closely as possible; the only material difference I see is that I'm using the same 3 nodes for control + compute. I am using MAAS so it's easy to get a clean OS install on all three nodes ahead of each attempt. I plan to try again with the standard (non-HWE) kernel just in case, but otherwise I am running out of ideas. In case of any additional clues, here are my globals.yml and inventory file, along with the playbook I'm using to configure the network, images, VMs, etc., after bootstrapping the cluster: https://gist.github.com/tobiasmcnulty/7dbbdbc67abc08cbb013bf5983852ed6 Thank you in advance for any advice! Cheers, Tobias

5 9

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

[openstack][kolla-ansible]about upgrading openstack
by Nguyễn Hữu Khôi 04 Aug '24

04 Aug '24

Hello. I read this doc about upgrading openstack https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html But I would like to know if We install a new kolla-ansible(version to upgrade) on the new deployment host, apply changes with password.yml, global.yml and multinode and keep old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of kolla-ansible upgrade. Are these steps ok? Pls correct me if I am wrong. Thank you. Regards Nguyen Huu Khoi

3 8

[kolla-ansible][letsencrypt] containers are running but not getting certificates.
by Jonathan Proulx 03 Jul '24

03 Jul '24

Hi All, I'm trying to do a test multinode deploy using 2023.2 I have letsencrypt_webserver and letsencrypt_lego contsainers running and I'm seeing random traffic in the /var/log/kolla/letsencrypt/letsencrypt-webserver-access.log so fairly confident they're plumbed through to the public internet properly, but I don't seem to be getting certificates. how can I trigger a renewal attempt so I can maybe see what I've screwed up? Thanks, -Jon -- Jonathan Proulx (he/him) Sr. Technical Architect The Infrastructure Group MIT CSAIL

3 6

[barbican][openstack-helm][tacker] Request to Include Barbican Installation Guide in OpenStack-Helm Documentation
by JUSO WATARU(十楚　航) 20 Jun '24

20 Jun '24

Hello, We are presently in the process of enhancing the official OpenStack-Helm documentation by including a procedural guide for deploying Tacker using helmchart. Through discussions with members of the openstack-helm community, it has been emphasized that Barbican is an indispensable component for Tacker. Hence, it would be highly beneficial for users to have comprehensive instructions for installing Barbican with helmchart included in the official OpenStack-Helm documentation [1]. Consequently, we suggest that the Barbican community integrate the installation guide for the Barbican component into the official OpenStack-Helm documentation. This addition is poised to significantly enhance the clarity and accessibility of deployment procedures for users. We eagerly welcome your opinions and feedback on this proposal, as we aim to ensure that the documentation for openstack deployment with helmchart meets the needs of our community. [1] https://docs.openstack.org/openstack-helm/latest/install/openstack.html Regards, Wataru

2 2

Issue in Stack.sh
by Lohit S 13 Jun '24

13 Jun '24

How to fix this issue while stack.sh is executed +functions-common:_run_under_systemd:1655 sudo systemctl start devstack(a)q-svc.service +functions-common:run_process:1687 time_stop run_process +functions-common:time_stop:2421 local name +functions-common:time_stop:2422 local end_time +functions-common:time_stop:2423 local elapsed_time +functions-common:time_stop:2424 local total +functions-common:time_stop:2425 local start_time +functions-common:time_stop:2427 name=run_process +functions-common:time_stop:2428 start_time=1716869530330 +functions-common:time_stop:2430 [[ -z 1716869530330 ]] ++functions-common:time_stop:2433 date +%s%3N +functions-common:time_stop:2433 end_time=1716869534546 +functions-common:time_stop:2434 elapsed_time=4216 +functions-common:time_stop:2435 total=16163 +functions-common:time_stop:2437 _TIME_START[$name]= +functions-common:time_stop:2438 _TIME_TOTAL[$name]=20379 +lib/neutron:start_neutron_service_and_check:640 neutron_url= http://192.168.122.150:9696/ +lib/neutron:start_neutron_service_and_check:642 is_service_enabled tls-proxy +functions-common:is_service_enabled:2077 return 1 +lib/neutron:start_neutron_service_and_check:646 '[' '!' -z networking ']' +lib/neutron:start_neutron_service_and_check:647 neutron_url= http://192.168.122.150:9696/networking +lib/neutron:start_neutron_service_and_check:649 echo 'Waiting for Neutron to start...' Waiting for Neutron to start... +lib/neutron:start_neutron_service_and_check:651 local 'testcmd=wget --no-proxy -q -O- http://192.168.122.150:9696/networking' +lib/neutron:start_neutron_service_and_check:652 test_with_retry 'wget --no-proxy -q -O- http://192.168.122.150:9696/networking' 'Neutron did not start' 60 +functions-common:test_with_retry:2359 local 'testcmd=wget --no-proxy -q -O- http://192.168.122.150:9696/networking' +functions-common:test_with_retry:2360 local 'failmsg=Neutron did not start' +functions-common:test_with_retry:2361 local until=60 +functions-common:test_with_retry:2362 local sleep=0.5 +functions-common:test_with_retry:2364 time_start test_with_retry +functions-common:time_start:2407 local name=test_with_retry +functions-common:time_start:2408 local start_time= +functions-common:time_start:2409 [[ -n '' ]] ++functions-common:time_start:2412 date +%s%3N +functions-common:time_start:2412 _TIME_START[$name]=1716869535329 +functions-common:test_with_retry:2365 timeout 60 sh -c 'while ! wget --no-proxy -q -O- http://192.168.122.150:9696/networking; do sleep 0.5; done' +functions-common:test_with_retry:2366 die 2366 'Neutron did not start' +functions-common:die:285 local exitcode=0 [Call Trace] ./stack.sh:1322:start_neutron_service_and_check /home/lohit22/opensource/openstack/devstack/Org/devstack/lib/neutron:652:test_with_retry /home/lohit22/opensource/openstack/devstack/Org/devstack/functions-common:2366:die [ERROR] /home/lohit22/opensource/openstack/devstack/Org/devstack/functions-common:2366 Neutron did not start exit_trap: cleaning up child processes Error on exit

2 2

[openstack charm][tc] openstack-charms still need PTL appointment
by Ghanshyam Mann 11 Jun '24

11 Jun '24

Hello Felipe, openstack-charm team, I tried to reach out to you on IRC but could not connect. This is regarding openstack-charm PTL appointment for the 2024.2 cycle. I am not sure if you noticed or not but there are some comments for you to fix on your PTL appointment. Please check the below Gerrit change and fix the same or let us know if there is a change in the plan. - https://review.opendev.org/c/openstack/governance/+/914254 -gmann

2 3

[swift] clean up orphan segment parts
by Rafael Tavares Oliveira 07 Jun '24

07 Jun '24

Hey there! We've been using swift and we came across this bug https://bugs.launchpad.net/swift/+bug/1813202. We decided to work it out and have an ongoing patch to solve this issue alongside ronaldo.maia(a)luizalabs.com, we would like to share and get some feedback before we submit it. To solve this, we took inspiration in obj/expirer.py: In S3 controllers we register task objects in an internal account, each task object points to an orphaned slo object, which can be created in two situations, when a multipart-upload is not completed or when a multipart object is overwritten. These tasks will be checked by the daemon (a new one we made called "s3-slo-expirer") after some time and deleted from the base accounts. Rafael

2 2

[all][tc] Eventlet migration: Call to action
by Jay Faulkner 07 Jun '24

07 Jun '24

Hi all, As you may have read in Goutham's TC summary, the existing eventlet goal[0] is unlikely to gain consensus to merge. This appears to be due to the difference in needs between OpenStack projects, and belief that it's unlikely a single solution would serve them all. Our current situation is: 1) Eventlet usage must be discontinued. The temporary maintainers are just that -- temporary -- and we should not expect eventlet to continue to be a valid path moving forward. 2) We have basic agreement that shared tooling, such as oslo libraries, should not dictate a specific threading model. In lieu of specific technical leadership and guidance from the TC, this leaves it to individual projects to decide what threading model to use instead of eventlet monkey patching. The unmerged spec[0] may be a good starting point if you're wondering where to start. Importantly: do not let this work wait! It is a significant change and will take a long time to complete. Thanks, Jay Faulkner 0: https://review.opendev.org/c/openstack/governance/+/902585

6 7

Antelope Barbican/Keystone: failure to delete secrets (Keystone TrustNotFound)
by Michel Jouvin 05 Jun '24

05 Jun '24

Hi, I've been validating Yoga -> Antelope on our preprod cloud. It was working successfully but "suddenly" (i.e. without a kwown/identified change!) when deleting Magnum clusters, the deletion of Barbican secrets (after stack deletion) fail. In the Magnum log, I find the following error: ---- Failed to delete trust: keystoneauth1.exceptions.http.Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-a4400250-e8d5-46ec-a28a-dcb97a682512) (traceback skipped for readability) 2024-05-29 10:43:09.750 2078 INFO magnum.common.cert_manager.barbican_cert_manager [None req-94df560b-d6da-4fba-83a9-34e0b08c64c8 - - - - - -] Recursively deleting certificate container https://os-77023.lal.in2p3.fr:9311/v1/containers/edd8487a-6cf1-4f4c-9f53-17… from Barbican. 2024-05-29 10:43:09.750 2078 INFO barbicanclient.base [None req-94df560b-d6da-4fba-83a9-34e0b08c64c8 - - - - - -] Calculated Containers uuid ref: containers/edd8487a-6cf1-4f4c-9f53-173dfae7a8b2 2024-05-29 10:43:09.760 2078 ERROR barbicanclient.client [None req-94df560b-d6da-4fba-83a9-34e0b08c64c8 - - - - - -] 4xx Client error: Not Found: Secrets container not found. 2024-05-29 10:43:09.761 2078 ERROR magnum.common.cert_manager.barbican_cert_manager [None req-94df560b-d6da-4fba-83a9-34e0b08c64c8 - - - - - -] Error recursively deleting certificate container https://os-77023.lal.in2p3.fr:9311/v1/containers/edd8487a-6cf1-4f4c-9f53-17…: barbicanclient.exceptions.HTTPClientError: Not Found: Secrets container not found. ---- In Keystone log, I find with the same timestamp the following error that seems related to the one above: ---- 2024-05-29 10:43:09.690 1713 WARNING keystone.api._shared.authentication [None req-a4400250-e8d5-46ec-a28a-dcb97a682512 - - - - - -] Could not find trust: cf4b1b6082594025a1ff9e48df383566.: keystone.exception.TrustNotFound: Could not find trust: cf4b1b6082594025a1ff9e48df383566. 2024-05-29 10:43:09.693 1713 WARNING keystone.server.flask.application [None req-a4400250-e8d5-46ec-a28a-dcb97a682512 - - - - - -] Authorization failed. The request you have made requires authentication. from 134.158.77.23: keystone.exception.Unauthorized: The request you have made requires authentication. 2024-05-29 10:43:09.746 1723 ERROR keystone.server.flask.application [None req-8c76f304-c2a3-418c-8372-02c706ed356e 44d8cb3192b3485790ababe29991491a - 5b67a8641dd041089e018ceea9884eac - 5b67a8641dd041089e018ceea9884eac -] Could not find user: 527ec32509d849e8a49b41c3dc4c4c32.: keystone.exception.UserNotFound: Could not find user: 527ec32509d849e8a49b41c3dc4c4c32. ---- It is not clear for me if the ERROR is releated to the 2 warnings as the request is not the same but it seems to happen every time this way. In Barbican logs, there is not much things related except a 401 status for the request corresponding ot the TrustNotFound. I'm looking for advices on how to troubleshoot this. In particular, when the trust should be created and whether I should find somewhere a matching error at the time of the trust creation. It seems the error is only affecting deletion but I may be wrong. for the record, when starting Magnum there is an error complaining about /etc/magnum/keystone_auth_default_policy.json being not found but ignored it so far. And in Keystone an error seems to occur at Magnum cluster creation time: --- 2024-05-29 10:17:17.530 1711 WARNING py.warnings [None req-f484cc35-3e54-4d7f-8688-e6442c90344f a22b1199c74f4a819a49f3ac037a5e44 1dd67113c8bb4ef0a31dfca53335ffbd - - defaul t default] /usr/lib/python3.9/site-packages/oslo_policy/policy.py:1129: UserWarning: Policy "identity:list_services": "role:reader and system_scope:all" failed scope check. The token used to make the request was project scoped but the policy requires ['system'] scope. This behavior may change in the future where using the intended scope is re quired ---- Thanks in advance for any hint. Best regards, Michel

2 3

Antelope Magnum: creating a new cluster makes the/some others unhealthy
by Michel Jouvin 05 Jun '24

05 Jun '24

Hi, I have been playing with Magnum (Antelope), creating a lot of clusters with the same template and varying the number of masters and/or nodes, having ~10 clusters started in the same project. I observed recently that cluster configuration that used to work well were not working any more (CREATE_FAILED during the master deployment in general). I have not found any evidence of the cause digging in various logs but I observed that with the current list of active clusters, if add a new one (even with a configuration as minimal as 1 master and 1 node), not only its creation fails but also the other (or at least) running clusters become unhealthy. If I delete the failed cluster, the other clusters return to the healthy state. It seems very reproducible (I did it more than 10 times) but I still don't see any message in the logs that could help to identify the cause. I've the feeling (but may be wrong) that it is related to either an insufficient project quota or an insufficient limit on one of the OpenStack service. Any idea on a possible cause or any advice on where to look for some information? Thanks in advance. Michel

2 6

[all] SQLAlchemy minimum requirement
by Pierre Riteau 02 Jun '24

02 Jun '24

Hello everyone, Historically, many projects were using the following requirement for SQLAlchemy: SQLAlchemy!=1.1.5,!=1.1.6,!=1.1.7,!=1.1.8,>=1.0.10 These banned versions were present in global-requirements.txt until earlier this month [1]. The remaining projects with the above requirement must change it to fix their requirements-check job (ERROR: Requirement for package SQLAlchemy excludes a version not excluded in the global list). While fixing the requirement for blazar, I realised that OpenStack projects are using a wide range of minimum requirements. For example, networking-sfc had already bumped the minimum to SQLAlchemy 2.0 [2], although this is being reverted [3]. While all projects must be compatible with the upper constraint (currently 2.0.30), should we agree on a maximum version for the lower bound? The 2024.2 release targets Ubuntu Jammy, which includes python3-sqlalchemy 1.4.31, and Debian bookworm, which includes python3-sqlalchemy 1.4.46. Thanks, Pierre Riteau (priteau) [1] https://review.opendev.org/c/openstack/requirements/+/879743 [2] https://review.opendev.org/c/openstack/networking-sfc/+/920046 [3] https://review.opendev.org/c/openstack/networking-sfc/+/920868

2 1

The outbound unicast traffic of VMS with security group enabled is broadcast
by renwc＠chinatelecom.cn 31 May '24

31 May '24

hello everyone， Here is a description of a bug I encountered using openstack Security Group,If security groups are enabled for virtual nics on cloud hosts, The outgoing traffic of the VMS enabled in the security group should be sent in unicast mode, but it is eventually forwarded to all ports in the vlan on the ovs br-int bridge. Does the openstack open source community have a patch to fix this bug? Can you provide patch? The following is my debugging process in detail. The unicast packet sent by the remote virtual machine 172.83.160.63 to the local virtual machine 172.83.160.74 is passed to the br-ex->br-int-> VM, Because the security group is enabled on the VM NIC, The br-int cannot learn the entry whose port is patch-ex and mac address is vm2. Therefore those packets sent from vm1 to vm2 are broadcast in vlans because they fail to match mac address entries. 172.83.160.74 patch-int 172.83.160.63 vm1 --- ovs(br-int) ------ ovs(br-ex)--- tor(physical switch) ......vm2 patch-ex The following is the ovs kernel flow table. The mac address of vm1 is fa:16:3e:6c:f3:09,The mac address of vm2 is fa:16:3e:d2:14:b5, the action of the flow table is multiple ports. recirc_id(0x314123),in_port(8),ct_state(-new+est-rel-rpl),eth(src=fa:16:3e:d2:14:b5,dst=fa:16:3e:6c:f3:09),eth_type(0x0800),ipv4(proto=6,frag=no),tcp(dst=2048/0xf800), packets:60100, bytes:14257193, used:2.035s, flags:P., actions:push_vlan(vid=5,pcp=0),3,pop_vlan,push_vlan(vid=1732,pcp=0),1,pop_vlan,7,9,10,15,5,18 recirc_id(0x314123),in_port(8),ct_state(-new+est-rel+rpl-inv+trk),ct_zone(0x5),ct_mark(0),eth(src=fa:16:3e:d2:14:b5,dst=fa:16:3e:6c:f3:09),eth_type(0x0800),ipv4(frag=no), packets:1, bytes:54, used:2.037s, flags:., actions:push_vlan(vid=5,pcp=0),3,pop_vlan,push_vlan(vid=1732,pcp=0),1,pop_vlan,7,9,10,15,5,18 After careful debugging analysis, the openflow action in the flow table 82 added by neutron is the VM port instead of normal. As a result, the ovs br-int bridge cannot learn the mac entry of vm2. table=82, priority=77,ct_state=+new-est,tcp,reg5=0x9,tp_dst=0x4/0xfffc actions=ct(commit,zone=NXM_NX_REG6[0..15]),output:9 table=82, priority=77,ct_state=+est-rel-rpl,tcp,reg5=0x9,tp_dst=0x4/0xfffc actions=output:9 Looking forward to reply thanks. weichun ren

2 1

The outgoing unicast traffic from the VMS enabled in the security group is eventually forwarded to all ports.
by renwc＠chinatelecom.cn 30 May '24

30 May '24

Hello， Here is a description of a bug I encountered using openstack Security Group,If security groups are enabled for virtual nics on VMS, The outgoing traffic from the VMS enabled in the security group should be sent in unicast mode, but it is eventually forwarded to all ports in the vlan on the ovs br-int bridge. Does the openstack open source community have a patch to fix this bug? Can you provide patch fixed the issue? The following is my debugging process in detail. The unicast packet sent by the remote virtual machine 172.83.160.63 to the local virtual machine 172.83.160.74 is passed to the br-ex->br-int-> VM, Because the security group is enabled on the VM NIC, The br-int cannot learn the entry whose port is patch-ex and mac address is vm2. Therefore those packets sent from vm1 to vm2 are broadcast in vlans because they fail to match mac address entries. 172.83.160.74 patch-int 172.83.160.63 vm1 --- ovs(br-int) ------ ovs(br-ex)--- tor(physical switch) ......vm2 patch-ex The following is the ovs kernel flow table. The mac address of vm1 is fa:16:3e:6c:f3:09,The mac address of vm2 is fa:16:3e:d2:14:b5, the action of the flow table is multiple ports. recirc_id(0x314123),in_port(8),ct_state(-new+est-rel-rpl),eth(src=fa:16:3e:d2:14:b5,dst=fa:16:3e:6c:f3:09),eth_type(0x0800),ipv4(proto=6,frag=no),tcp(dst=2048/0xf800), packets:60100, bytes:14257193, used:2.035s, flags:P., actions:push_vlan(vid=5,pcp=0),3,pop_vlan,push_vlan(vid=1732,pcp=0),1,pop_vlan,7,9,10,15,5,18 recirc_id(0x314123),in_port(8),ct_state(-new+est-rel+rpl-inv+trk),ct_zone(0x5),ct_mark(0),eth(src=fa:16:3e:d2:14:b5,dst=fa:16:3e:6c:f3:09),eth_type(0x0800),ipv4(frag=no), packets:1, bytes:54, used:2.037s, flags:., actions:push_vlan(vid=5,pcp=0),3,pop_vlan,push_vlan(vid=1732,pcp=0),1,pop_vlan,7,9,10,15,5,18 After careful debugging analysis, the openflow action in the flow table 82 added by neutron is the VM port instead of normal. As a result, the ovs br-int bridge cannot learn the mac entry of vm2. table=82, priority=77,ct_state=+new-est,tcp,reg5=0x9,tp_dst=0x4/0xfffc actions=ct(commit,zone=NXM_NX_REG6[0..15]),output:9 table=82, priority=77,ct_state=+est-rel-rpl,tcp,reg5=0x9,tp_dst=0x4/0xfffc actions=output:9 Was the issue above fixed in the openstack ? Looking forward to reply thanks. Best Regards weichun ren

1 0

Re: [tc][all][senlin] Retiring the Senlin project
by Ghanshyam Mann 30 May '24

30 May '24

---- On Thu, 30 May 2024 11:43:00 -0700 Sang Tran Quoc wrote --- > > Dear Ghanshyam, > > Greeting! I’m Sang from Viet Nam and now I’m working at the FPT Smart Cloud (Silver member of OpenInfra) as the openstack team leader. We have teammate with about 10 members who maintains the senlin project on our production AutoScaling Feature (my presentation about senlin at last VietOpenInfra summithttps://www.youtube.com/watch?v=aYXDI4mwohQ&t=1s) It’s sad to hear about community retired this project from upstream so I would like to nominate our team to continue maintain this project and I will handle the PTL role for further roadmap, bugs fix and feature. > > Hopefully it’s not late, I’m look forward to hearing from you for further discuss about next chance for senlin project. ++ openstack-discuss ML Hi Sang, Thanks for reaching out and its good to hear about Senlin project usage and your interest in maintaining it. > Hopefully it’s not late, I’m look forward to hearing from you for further discuss about next chance for senlin project. Unfortunately, TC has already retired the Senlin project[1]. Since last cycle, we have been waiting for interested maintainers to step up. * No Leader in 2024.1 cycle ** https://etherpad.opendev.org/p/2024.1-leaderless * After TC discussion, Senlin has been marked as an 'inactive' project since '2024.1' cycle ** https://review.opendev.org/c/openstack/governance/+/902626 ** This was the time we were expecting someone to come forward and step up to maintain it. * No leader for Senlin in 2024.2 cycles also ** https://etherpad.opendev.org/p/2024.2-leaderless * Considering no leader for two cycles, no maintainer, and the process, TC initiated the retirement: ** https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… But this is not the end and Senlin can still re-become the official OpenStack project[2]. For that, you need to re-apply Senlin as a new project in OpenStack, please check the process: - https://governance.openstack.org/tc/reference/new-projects-requirements.html [1] - https://review.opendev.org/c/openstack/governance/+/919347 - https://review.opendev.org/q/topic:%22retire-senlin%22+ [2]https://governance.openstack.org/tc/reference/dropping-projects.html#re-b… -gmann > > > Thanks & Best Regards > > > Sang Tran Quoc (Mr.) > FPT Smart Cloud > FPT Tower, 10 Pham Van Bach Str., Cau Giay Dist., Ha Noi, Viet Nam > E: sangtq8(a)fpt.com > T: 0962949843 > W: https://fptcloud.com | https://fpt.ai > > > > > From:Ghanshyam Mann gmann(a)ghanshyammann.com> > Date: Saturday, 11 May 2024 at 09:06 > To: openstack-discuss openstack-discuss(a)lists.openstack.org> > Subject: Re: [tc][all][senlin] Retiring the Senlin project > ---- On Wed, 24 Apr 2024 13:39:33 -0700 Ghanshyam Mann wrote --- > > Hello everyone, > > > > As you might know, the Senlin project is not active and was marked 'inactive' > > since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer > > stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next > > step is to retire the project. > > > > I'm sending this email to propose the Senlin retirement and based on the response, > > I will proceed next. > > Seeing no response to this email or no volunteer to maintain this project, I have proposed > the retirement in governance: > > - https://review.opendev.org/c/openstack/governance/+/919347 > > -gmann > > > > > [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… > > [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 > > > > -gmann > > >

1 0

[neutron][all] OOM killer on coverage job
by Brian Haley 30 May '24

30 May '24

Hi, Neutron has been having issues with our coverage gate job triggering the OOM killer since last week [0], which I just confirmed by holding a node and looking in the logs. It started happening after the sqlalchemy 2.0 bump [1], but that just might be exposing the underlying issue. Running locally I can see via /proc/meminfo that memory is getting consumed: MemTotal: 8123628 kB MemFree: 1108404 kB And via ps it's the coverage processes doing it: PID %MEM RSS PPID TIME NLWP WCHAN COMMAND 4315 30.9 2516348 4314 01:29:07 1 - /opt/stack/neutron/.tox/cover/bin/python /opt/stack/neutron/.tox/cover/bin/coverage run --source neutron --parallel-mode -m stestr.subunit_runner.run discover -t ./ ./neutron/tests/unit --load-list /tmp/tmp0rhqfwhz 4313 30.0 2437500 4312 01:28:50 1 - /opt/stack/neutron/.tox/cover/bin/python /opt/stack/neutron/.tox/cover/bin/coverage run --source neutron --parallel-mode -m stestr.subunit_runner.run discover -t ./ ./neutron/tests/unit --load-list /tmp/tmpfzmqyuub (and the test hasn't even finished yet) Only workaround seems to be reducing concurrency [2]. Have any other projects seen anything similar? (and sorry for the html email) -Brian [0] https://bugs.launchpad.net/neutron/+bug/2065821 [1] https://review.opendev.org/c/openstack/requirements/+/879743 [2] https://review.opendev.org/c/openstack/neutron/+/920766

4 6

A bug about openstack security groups
by renwc＠chinatelecom.cn 29 May '24

29 May '24

hello everyone， Here is a description of a bug I encountered using openstack Security Group,If security groups are enabled for virtual nics on cloud hosts, The outgoing traffic of the VMS enabled in the security group should be sent in unicast mode, but it is eventually forwarded to all ports in the vlan on the ovs br-int bridge. Does the openstack open source community have a patch to fix this bug? Can you provide patch? The following is my debugging process in detail. The unicast packet sent by the remote virtual machine 172.83.160.63 to the local virtual machine 172.83.160.74 is passed to the br-ex->br-int-> VM, Because the security group is enabled on the VM NIC, The br-int cannot learn the entry whose port is patch-ex and mac address is vm2. Therefore those packets sent from vm1 to vm2 are broadcast in vlans because they fail to match mac address entries. 172.83.160.74 patch-int 172.83.160.63 vm1 --- ovs(br-int) ------ ovs(br-ex)--- tor(physical switch) ......vm2 patch-ex The following is the ovs kernel flow table. The mac address of vm1 is fa:16:3e:6c:f3:09,The mac address of vm2 is fa:16:3e:d2:14:b5, the action of the flow table is multiple ports. recirc_id(0x314123),in_port(8),ct_state(-new+est-rel-rpl),eth(src=fa:16:3e:d2:14:b5,dst=fa:16:3e:6c:f3:09),eth_type(0x0800),ipv4(proto=6,frag=no),tcp(dst=2048/0xf800), packets:60100, bytes:14257193, used:2.035s, flags:P., actions:push_vlan(vid=5,pcp=0),3,pop_vlan,push_vlan(vid=1732,pcp=0),1,pop_vlan,7,9,10,15,5,18 recirc_id(0x314123),in_port(8),ct_state(-new+est-rel+rpl-inv+trk),ct_zone(0x5),ct_mark(0),eth(src=fa:16:3e:d2:14:b5,dst=fa:16:3e:6c:f3:09),eth_type(0x0800),ipv4(frag=no), packets:1, bytes:54, used:2.037s, flags:., actions:push_vlan(vid=5,pcp=0),3,pop_vlan,push_vlan(vid=1732,pcp=0),1,pop_vlan,7,9,10,15,5,18 After careful debugging analysis, the openflow action in the flow table 82 added by neutron is the VM port instead of normal. As a result, the ovs br-int bridge cannot learn the mac entry of vm2. table=82, priority=77,ct_state=+new-est,tcp,reg5=0x9,tp_dst=0x4/0xfffc actions=ct(commit,zone=NXM_NX_REG6[0..15]),output:9 table=82, priority=77,ct_state=+est-rel-rpl,tcp,reg5=0x9,tp_dst=0x4/0xfffc actions=output:9 Looking forward to reply thanks. 任维春智能计算产品部/智能云网业务部邮箱：renwc(a)chinatelecom.cn 地址：北京市西城区西直门内大街118-1 中电信数智科技有限公司

1 0

[Diskimage-builder]Supported architectures for creating OS images in Diskimage-builder
by Junya Noguchi (Fujitsu) 29 May '24

29 May '24

To whom it may concern I am investigating which Linux distributions and versions for aarch64 are supported by Diskimage-builder. I found that many newer versions of Linux distributions are supported*, but there is no information about supported architectures in the commit messages. * References: Ubuntu: https://review.opendev.org/c/openstack/project-config/+/916050 RHEL: https://review.opendev.org/c/openstack/diskimage-builder/+/877347 SLES: https://review.opendev.org/c/openstack/diskimage-builder/+/619186 SUSE: https://review.opendev.org/c/openstack/diskimage-builder/+/908421 CentOS: https://review.opendev.org/c/openstack/tripleo-quickstart/+/843102 Does Diskimage-builder support building aarch64 images for those distributions? If not, a list of supported distros for aarch64, would be helpful. Best regards, Junya Noguchi.

2 4

[kolla] cancelling weekly meeting today (29th May 2024)
by Michał Nasiadka 29 May '24

29 May '24

Hello Koalas, We’re cancelling the weekly meeting today (29th May 2024) due to no show of majority key members. Let’s meet next week! Thanks for understanding, Michal

1 0

overcloud deploy fails in step 1 | tripleo | wallaby
by Swogat Pradhan 28 May '24

28 May '24

Hi, I am trying to run a stack update and am executing openstack overcloud deploy, but after reaching step 1 and prefetching the container images the deployment fails with following error: s 2024-05-16 19:58:54.138764 | 525400ff-fd40-2d4d-b69c-000000010c98 | OK | Pre-fetch all the containers | overcloud-controller-1 | item=172.25.201.68:8787/tripleomaster/openstack-cinder-backup:latest 2024-05-16 19:58:54.143338 | 525400ff-fd40-2d4d-b69c-000000010c98 | TIMING | Pre-fetch all the containers | overcloud-controller-1 | 0:23:18.464385 | 43.62s An exception occurred during task execution. To see the full traceback, use -vvv. The error was: KeyError: 'config' s/_base.py\", line 384, in __get_result\n raise self._exception\n File \"/usr/lib64/python3.6/concurrent/futures/thread.py\", line 56, in run\n result = self.fn(*self.args, **self.kwargs)\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 332, in run_container\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 318, in manage_container\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1659, in execute\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1572, in make_started\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1351, in different\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 692, in __init__\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 699, in defaultize\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 661, in __init__\nKeyError: 'config'\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee st2024-05-16 19:58:55.487682 | 525400ff-fd40-2d4d-b69c-000000010b27 | FATAL | Manage Puppet containers (generate config) for step 1 | overcloud-novacompute-3 | error={"changed": false, "module_stderr": "Traceback (most recent call last):\n File \"<stdin>\", line 102, in <module>\n File \"<stdin>\", line 94, in _ansiballz_main\n File \"<stdin>\", line 40, in invoke_module\n File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\n mod_name, mod_spec, pkg_name, script_name)\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 391, in <module>\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 387, in main\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 132, in __init__\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 370, in run\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 337, in check_failures\n File \"/usr/lib64/python3.6/concurrent/futures/_base.py\", line 586, in result_iterator\n yield fs.pop().result()\n File \"/usr/lib64/python3.6/concurrent/futures/_base.py\", line 425, in result\n return self.__get_result()\n File \"/usr/lib64/python3.6/concurrent/futures/_base.py\", line 384, in __get_result\n raise self._exception\n File \"/usr/lib64/python3.6/concurrent/futures/thread.py\", line 56, in run\n result = self.fn(*self.args, **self.kwargs)\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 332, in run_container\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 318, in manage_container\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1659, in execute\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1572, in make_started\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1351, in different\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 692, in __init__\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 699, in defaultize\n File \"/tmp/ansible_tripleo_container_manage_payload_sg7woby1/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 661, in __init__\nKeyError: 'config'\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} 2024-05-16 19:58:55.488510 | 525400ff-fd40-2d4d-b69c-000000010b27 | TIMING | Manage Puppet containers (generate config) for step 1 | overcloud-novacompute-3 | 0:23:19.809572 | 82.91s 2024-05-16 19:58:55.859707 | 525400ff-fd40-2d4d-b69c-000000010c98 | OK | Pre-fetch all the containers | overcloud-controller-1 | item=172.25.201.68:8787/tripleomaster/openstack-cinder-volume:latest 2024-05-16 19:58:55.864370 | 525400ff-fd40-2d4d-b69c-000000010c98 | TIMING | Pre-fetch all the containers | overcloud-controller-1 | 0:23:20.185418 | 45.34s 2024-05-16 19:58:57.659959 | 525400ff-fd40-2d4d-b69c-000000010c98 | OK | Pre-fetch all the containers | overcloud-controller-1 | item=172.25.201.68:8787/tripleomaster/openstack-iscsid:latest 2024-05-16 19:58:57.664429 | 525400ff-fd40-2d4d-b69c-000000010c98 | TIMING | Pre-fetch all the containers | overcloud-controller-1 | 0:23:21.985477 | 47.14s 2024-05-16 19:59:00.211286 | 525400ff-fd40-2d4d-b69c-000000010c98 | OK | Pre-fetch all the containers | overcloud-controller-1 | item=172.25.201.68:8787/tripleomaster/openstack-manila-share:latest 2024-05-16 19:59:00.216236 | 525400ff-fd40-2d4d-b69c-000000010c98 | TIMING | Pre-fetch all the containers | overcloud-controller-1 | 0:23:24.537284 | 49.69s 2024-05-16 19:59:02.113037 | 525400ff-fd40-2d4d-b69c-000000010c98 | OK | Pre-fetch all the containers | overcloud-controller-1 | item=172.25.201.68:8787/tripleomaster/openstack-aodh-evaluator:latest 2024-05-16 19:59:02.117498 | 525400ff-fd40-2d4d-b69c-000000010c98 | TIMING | Pre-fetch all the containers | overcloud-controller-1 | 0:23:26.438544 | 51.59s 2024-05-16 19:59:03.853383 | 525400ff-fd40-2d4d-b69c-000000010c98 | OK | Pre-fetch all the containers | overcloud-controller-1 | item=172.25.201.68:8787/tripleomaster/openstack-aodh-listener:latest 2024-05-16 19:59:03.858232 | 525400ff-fd40-2d4d-b69c-000000010c98 | TIMING | Pre-fetch all the containers | overcloud-controller-1 | 0:23:28.179287 | 53.33s 2024-05-16 19:59:05.665169 | 525400ff-fd40-2d4d-b69c-000000010c98 | OK | Pre-fetch all the containers | overcloud-controller-1 | item=172.25.201.68:8787/tripleomaster/openstack-aodh-notifier:latest 2024-05-16 19:59:05.670233 | 525400ff-fd40-2d4d-b69c-000000010c98 | TIMING | Pre-fetch all the containers | overcloud-controller-1 | 0:23:29.991278 | 55.14s An exception occurred during task execution. To see the full traceback, use -vvv. The error was: KeyError: 'config' /futures/_base.py\", line 384, in __get_result\n raise self._exception\n File \"/usr/lib64/python3.6/concurrent/futures/thread.py\", line 56, in run\n result = self.fn(*self.args, **self.kwargs)\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 332, in run_container\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 318, in manage_container\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1659, in execute\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1572, in make_started\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1351, in different\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 692, in __init__\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 699, in defaultize\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 661, in __init__\nKeyError: 'config'\n", "module_stdout": "", "msg": "MODULE FAILURE\2024-05-16 19:59:06.648301 | 525400ff-fd40-2d4d-b69c-000000010fc3 | FATAL | Manage Puppet containers (generate config) for step 1 | overcloud-controller-no-ceph-3 | error={"changed": false, "module_stderr": "Traceback (most recent call last):\n File \"<stdin>\", line 102, in <module>\n File \"<stdin>\", line 94, in _ansiballz_main\n File \"<stdin>\", line 40, in invoke_module\n File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\n mod_name, mod_spec, pkg_name, script_name)\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 391, in <module>\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 387, in main\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 132, in __init__\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 370, in run\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 337, in check_failures\n File \"/usr/lib64/python3.6/concurrent/futures/_base.py\", line 586, in result_iterator\n yield fs.pop().result()\n File \"/usr/lib64/python3.6/concurrent/futures/_base.py\", line 425, in result\n return self.__get_result()\n File \"/usr/lib64/python3.6/concurrent/futures/_base.py\", line 384, in __get_result\n raise self._exception\n File \"/usr/lib64/python3.6/concurrent/futures/thread.py\", line 56, in run\n result = self.fn(*self.args, **self.kwargs)\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 332, in run_container\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible/modules/tripleo_container_manage.py\", line 318, in manage_container\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1659, in execute\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1572, in make_started\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 1351, in different\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 692, in __init__\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 699, in defaultize\n File \"/tmp/ansible_tripleo_container_manage_payload_wnnokrwc/ansible_tripleo_container_manage_payload.zip/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py\", line 661, in __init__\nKeyError: 'config'\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} I do not have any idea why this is caused and how to fix it. Can someone please help? With regards, Swogat Pradhan

4 9

OpenInfra Summit Asia'24 CFP closes tomorrow (May 29)!
by Jeremy Stanley 28 May '24

28 May '24

I'll refer you back to my reminder from two weeks ago for details: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… The Summit CFP is still accepting talk proposals through tomorrow, May 29, 2024. If you're interested in presenting in Korea this September, the time to submit your abstract is now! https://openinfrafoundation.formstack.com/forms/openinfra_asia_summit_2024 As always, reply or find me (fungi) in the #openstack channel on the OFTC IRC network if you have questions. -- Jeremy Stanley

1 0

DevStack Setup
by Lohit S 28 May '24

28 May '24

Hi Team, I had tried to execute the ./stack.sh in devstack repo But I got the following error, How to fix this issue. +lib/neutron_plugins/ovn_agent:ovn_sanity_check:358 die 358 'The q-agt/neutron-agt service must be disabled with OVN.' +functions-common:die:285 local exitcode=0 +functions-common:die:286 set +o xtrace [Call Trace] ./stack.sh:979:stack_install_service /home/lohit22/opensource/openstack/devstack/Org/devstack/lib/stack:32:install_neutron /home/lohit22/opensource/openstack/devstack/Org/devstack/lib/neutron:551:install_ovn /home/lohit22/opensource/openstack/devstack/Org/devstack/lib/neutron_plugins/ovn_agent:373:ovn_sanity_check /home/lohit22/opensource/openstack/devstack/Org/devstack/lib/neutron_plugins/ovn_agent:358:die [ERROR] /home/lohit22/opensource/openstack/devstack/Org/devstack/lib/neutron_plugins/ovn_agent:358 The q-agt/neutron-agt service must be disabled with OVN. Error on exit World dumping... see /opt/stack/logs/worlddump-2024-05-26-053930.txt for details

3 7

[neutron] Bug deputy report for week of May 20th
by Brian Haley 28 May '24

28 May '24

Hi, I was 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/2066221 - [dalmatian] skip level grenade jobs fails at keystone-manage db_sync - https://review.opendev.org/c/openstack/neutron/+/920075 * https://bugs.launchpad.net/neutron/+bug/2066263 - functional tests broken with ovsdbapp 2.7.1 - https://review.opendev.org/c/openstack/neutron/+/920101 * https://bugs.launchpad.net/neutron/+bug/2066369 - Validation of the auto allocated topology for member/reader user don't works with new S-RBAC policies - https://review.opendev.org/c/openstack/neutron/+/920174 - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/920177 * https://bugs.launchpad.net/python-neutronclient/+bug/2067039 - openstack bgp [dragent|speaker] list filter commands dont return - Possibly related to the change to use OpenstackSDK code in https://review.opendev.org/c/openstack/python-neutronclient/+/868321 - Asked to make sure all libraries were updated - Might need further investigation by Lajos Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/2066989 - Virtual function is being attached to port regardless of the exclude_devices configuration - Asked for more information * https://bugs.launchpad.net/neutron/+bug/2067183 - Properly Use Network's DNS Domain in Assignment and DHCP - https://review.opendev.org/c/openstack/neutron/+/920459 - I'd like to discuss at Neutron meeting since we've broken things like this in the past Low bugs -------- * None Misc bugs --------- * None Wishlist bugs ------------- * https://bugs.launchpad.net/nova/+bug/2065790 - Nova fails to live migrate instance with dash separated MAC - Request for Neutron to always use :" in MACs, even if API given "-" - Will have to discuss at weekly meeting, I'm inclined to document around it

1 0

[publiccloud-sig] Reminder - next meeting May 29th - 0700 UTC
by Felix Kronlage-Dammers 28 May '24

28 May '24

Hi everyone, This Wednesday (May 29th, tomorrow) the next meeting of the public cloud sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG Likely we will pick up the discussions from our Forum Session at OID Berlin. See my summary that I sent to this list[1]. See you tomorrow! felix [1] <url: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…> -- Felix Kronlage-Dammers Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der 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

Re: [Octavia] octavia not setting up load balancers
by Jaime Ibar 28 May '24

28 May '24

Hi, I have set debug to true and I can see the following but not sure if they're related though Disabling service 'block-storage': Encountered an exception attempting to process config for project 'cinder' (service type 'block-storage'): no such option valid_interfaces in group [cinder]: oslo_config.cfg.NoSuchOptError: no such option valid_interfaces in group [cinder] Disabling service 'compute': Encountered an exception attempting to process config for project 'nova' (service type 'compute'): no such option valid_interfaces in group [nova]: oslo_config.cfg.NoSuchOptError: no such option valid_interfaces in group [nova] 2024-05-27 19:09:32.136 225246 WARNING openstack [None req-588327db-96d5-4377-ba72-b603731f9568 - c2270ba97baa40cbbb17f89d6980a2d6 - - default default] Disabling service 'image': Encountered an exception attempting to process config for project 'glance' (service type 'image'): no such option valid_interfaces in group [glance]: oslo_config.cfg.NoSuchOptError: no such option valid_interfaces in group [glance] Jaime On 27/05/2024 21:20, Winicius Allan wrote: > I understood. Is there any error log level message or anything like that? > > Em seg., 27 de mai. de 2024 às 15:19, Jaime Ibar <jim2k7(a)gmail.com> > escreveu: > > Hi Winicius, > > yes, I have the Octavia:health-mgr interface and it shows as > Active and up, in fact, I can ssh into the amphora from > the management network. > > Thanks > Jaime > > On Mon, 27 May 2024 at 18:54, Winicius Allan > <winiciusab12(a)gmail.com> wrote: > > Hi Jaime, > > In general, a load balancer stuck in the PENDING_CREATE state > could be a network problem. Do you have a network interface on > your control node that belongs to the same network as Amphora? > > Regards. > > Em seg., 27 de mai. de 2024 às 12:51, Jaime Ibar > <jim2k7(a)gmail.com> escreveu: > > Nope, I can't see anything. > > This is what I can see > > [...] > request url / request > /usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py:652 > request url https://172.16.4.56:9443// request > /usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py:655 > Connected to amphora. Response: <Response [200]> request > /usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py:677 > Amphora f3809732-80d8-4795-a5cb-cb36e63bc895 has API > version 1.0 _populate_amphora_api_version > /usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py:104 > > Update DB for loadbalancer id > Marking all listeners of loadbalancer > ce31155c-3484-4ff0-8740-fcd8c0915a1c ACTIVE execute > > Mark ACTIVE in DB for load balancer id: > [...] > > So all seems to be OK but nothing in the amphora. > > Thanks > Jaime > > On Mon, 27 May 2024 at 16:25, Oliver Weinmann > <oliver.weinmann(a)me.com> wrote: > > Ok, anything suspicious in the Octavia worker logs? > > Von meinem iPhone gesendet > >> Am 27.05.2024 um 17:17 schrieb Jaime Ibar >> <jim2k7(a)gmail.com>: >> >> >> Hi Oliver, >> >> thanks for the tip but after increasing the quotas, >> the problem persists :( >> >> Jaime >> >> On Mon, 27 May 2024 at 12:20, Oliver Weinmann >> <oliver.weinmann(a)me.com> wrote: >> >> Hi, >> >> Just a quick guess. Check the quotas for security >> groups of the service tenant. >> >> In our deployment we had a similar issue and saw >> errors indicating this in the logs. >> >> Cheers, >> Oliver >> >> Von meinem iPhone gesendet >> >> > Am 27.05.2024 um 13:16 schrieb Jaime Ibar >> <jim2k7(a)gmail.com>: >> > >> > >> > Hi all, >> > >> > I've been running Octavia with no issues so far >> and now it stopped working >> > with no reasons(no recent upgrades other that OS). >> > When I create a load balancer, sometimes the >> amphora is launched successfully >> > but some others is not. >> > When it's launched, no listeners, backends, >> pools are created and the load balancer >> > gets stuck in either, pending create or pending >> update state, and deleting all the >> > load balancer details from the database is the >> only option of getting rid of it. >> > >> > I can ssh into the amphora but I can't see any >> error, gunicorn is listening >> > on port 9443 but no haproxy instances are >> created(haproxy-<uuid>) on >> > /var/lib/octavia >> > >> > I'm running 2023.2 Bobcat version. >> > >> > Any ideas? >> > >> > TIA >> > Jaime >> > >> > -- >> > salu2 >> > >> > Jaime >> >> >> >> -- >> salu2 >> >> Jaime > > > > -- > salu2 > > Jaime > > > > -- > salu2 > > Jaime > -- Jaime

1 0

[Tempest] [Blazar] Connection Refused Error 111 on Blazar tempest plugin
by Tran, Kenny 28 May '24

28 May '24

First time asking a question on the mailing list, I am trying to set up tempest against a quick start yoga (kolla-ansible) deployment with Keystone, Zun, Heat, Blazar, and Nova (1 controller, 1 compute). Default tempest tests are behaving as expected but when I try to run the blazar plugin tests they fail with Errno 111 Connection Refused. I ran a tcpdump on the tempest server side and saw no issues. Tcpdump on controller showed a reset when trying to connect to keystone. Is this an issue with blazar not being able to authenticate against the openstack deployment? The default tempest tests succeed so I don't think my admin_password admin_username etc. are incorrect. Kenny Tran Iowa State University Student Computer Engineer 515-441-5237 | trantk(a)iastate.edu

2 1

[Octavia] octavia not setting up load balancers
by Jaime Ibar 27 May '24

27 May '24

Hi all, I've been running Octavia with no issues so far and now it stopped working with no reasons(no recent upgrades other that OS). When I create a load balancer, sometimes the amphora is launched successfully but some others is not. When it's launched, no listeners, backends, pools are created and the load balancer gets stuck in either, pending create or pending update state, and deleting all the load balancer details from the database is the only option of getting rid of it. I can ssh into the amphora but I can't see any error, gunicorn is listening on port 9443 but no haproxy instances are created(haproxy-<uuid>) on /var/lib/octavia I'm running 2023.2 Bobcat version. Any ideas? TIA Jaime -- salu2 Jaime

3 7

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-18)
by Goutham Pacha Ravi 27 May '24

27 May '24

Hello Stackers, We're 18 weeks away from the 2024.2 (Dalmatian) release [1]. The Call for Proposals for the upcoming Open Infra Summit is still open [2], but it will close in a couple of days (May 29th, 2024). If you're planning to attend, I encourage you to submit a talk! In the past week, the OpenStack Technical Committee continued its spring cleaning exercise – this time, the party was on PyPi. We also identified dates for the TC and PTL elections for the 2025.1 ("E") release cycle [3]. The nomination period for the TC and PTL elections will begin on 2024-08-14 at 23:45 UTC and will conclude on 2024-08-28 at 23:45 UTC. The elections will be held between 23:45 UTC on 2024-09-04 and 23:45 UTC on 2024-09-18. === Weekly Meeting === We identified 207 maintainers for removal across 146 PyPi packages [4]. The cleanup task is large and manual due to a lack of API. We've also identified packages where "openstackci" cannot remove maintainers due to a lack of ownership. This is likely a long-drawn effort. I'll keep you posted as we make progress. We had a few remaining project updates pending from the last release cycle, and one of them concerned the OpenStack Charms team. Since the TC didn't have context on the health of the team and its plans, we decided to gather some information on this mailing list. We're also excited to publish the first draft for the next election dates/process, courtesy of our Election Official, Ian Y. Choi (ianychoi). This election will be socialized with early and periodic notifications to address concerns expressed regarding the lack of visibility and poor voter turnout in past elections. This meeting, like all of our IRC meetings, was logged to eavesdrop [5]. Our next weekly IRC meeting is tomorrow! The agenda is pretty light [6], likely owing to the fact that a few TC members are returning from a long weekend holiday. === Governance Proposals === ==== Merged ==== Retire devstack-gate | https://review.opendev.org/c/openstack/governance/+/919629 ==== Open for review/discussion ==== Appoint ChunYang Wu as PTL of Trove | https://review.opendev.org/c/openstack/governance/+/920462 Clarify the project retirement vs. project's repository retirement | https://review.opendev.org/c/openstack/governance/+/919984 Simplifying house rules for project updates | https://review.opendev.org/c/openstack/governance/+/920318 Update to include docs and miscellaneous repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://2024.openinfraasia.org/ [3] https://review.opendev.org/c/openstack/election/+/920092 [4] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L52 [5] https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-21-18.00.log.html [6] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

How to assign an ip-address to a server on creation
by Nine, Harmon S 27 May '24

27 May '24

Hello. I'm using the openstack connection api in python to create a server. The server is getting created, but the "create_server" call is not assigning the ip-address to the server that is specified in the call. flavor_id = 'ed88b5d6-150d-4715-8de0-8a2df0a1746a' image_id = '399ae60e-7f73-476e-aad7-13aebcad84a1' networks = [{'uuid': '978ebb40-8ee4-4c0b-932e-83dce7e182dd'}] ip_addresses =[{'subnet_id': '978ebb40-8ee4-4c0b-932e-83dce7e182dd', 'ip_address': '10.0.0.153'}] # also tried ip_addresses = ['10.0.0.153'] instance = conn.compute.create_server( name='testmachine', flavor_id=flavor_id, image_id=image_id, ips=ip_addresses, networks=network_uuid_list, key_name='key_name' ) What is the format of the "ips" argument? Are there other arguments that need to be specified? Thanks for any help you can provide 🙂 -- Harmon

3 5

[kolla][OpenstackAnsible] 2024.1 Caracal cycle-trailing release deadline reminder
by Herve Beraud 27 May '24

27 May '24

Hello teams with trailing projects, The 2024.1 Caracal cycle-trailing release deadline is next week [1], and all projects following the cycle-trailing release model must release their 2024.1 Caracal deliverables by June 6th, 2024. The following trailing projects haven't been released yet for 2024.1 Caracal, convenience patches have been proposed: OSA team's deliverables: - https://review.opendev.org/c/openstack/releases/+/919484 - https://review.opendev.org/c/openstack/releases/+/919483 Kolla team's deliverables: - https://review.opendev.org/c/openstack/releases/+/919486 This is just a friendly reminder to allow you to release these projects in time. Please, ensure to provide feedback or to update these patches before the deadline. Do not hesitate to ping us if you have any questions or concerns. [1] https://releases.openstack.org/dalmatian/schedule.html#d-cycle-trail Thanks, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[nova][scheduler] nova scheduler to balance vms more randomly
by Satish Patel 27 May '24

27 May '24

Folks, I have noticed when I spin up a bunch of vms then they all go to the same hypervisor until it runs out of resources. I can understand that it's trying to fill the hypervisor before it picks the next one. But it's kind of dangerous behavior. For example one customer created 3 vms to build a mysql galera cluster and all those 3 nodes endup on the same hypervisor (This is dangerous). I would like openstack to pick the hypervisor more randomly if resources are available in the pool instead of trying to fill the hypervisor. How do I change that behavior? ( There is a feature called affinity but again I would like nova to place vm more randomly instead shaving all to a single node). I am not an expert in scheduler logic so please educate me if I am missing something here.

5 5

Difficulty Create/Upload Images
by Cakra Wirabuana 24 May '24

24 May '24

Hi everyone, I have a difficulty when creating image. I have downloaded the file with both .img and .iso formats and I have tried various format options (QCOW2, RAW, ISO, etc) but it still fails and a notification appears as in the image I attached to this email. Does anyone know the cause of this and what is the solution? If it turns out that I have to create an image via CLI, how do I do it? I am using Ubuntu 22.04.4 LTS. Thank you, Cakra Wirabuana [image: image.png]

2 1

[openstack][magnum] Error with QueuePool limit of size
by Nguyễn Hữu Khôi 23 May '24

23 May '24

Hello. I am using Magnum 18.0.0.0rc2.dev2 in OPS 2024.01 with Magnum-Cluster-API(0.17.0) from Vexxhost. But I have these errors as: Ignore error [QueuePool limit of size 1 overflow 50 reached, connection timed out, timeout 30.00 (Background on this error at: https://sqlalche.me/e/14/3o7r) when syncing up cluster status.: sqlalchemy.exc.TimeoutError: QueuePool limit of size 1 overflow 50 reached, connection timed out, timeout 30.00 Full log is in: https://paste.sh/gWg28T2s#zctJBJsW34bX9pG705VR5PMP Thank you. Nguyen Huu Khoi

2 2

[trove][tc] Next step on leaderless project Trove
by Ghanshyam Mann 23 May '24

23 May '24

Hi Wu, This is regarding the Trove project leader assignment. We saw your late candidacy for Trove PTL[1]. The TC has listed Trove as a late candidacy project[2] and can consider a PTL appointment. If you are still interested in serving as Trove PTL, please propose the PTL appointment request to TC. Example: https://review.opendev.org/c/openstack/governance/+/915108 [1] https://review.opendev.org/c/openstack/election/+/910488 [2] https://etherpad.opendev.org/p/2024.2-leaderless#L99 -gmann

1 1

cpu steal
by Gk Gk 22 May '24

22 May '24

Hi, If we create pinned vms, is there a chance of cpu steal in this scenario ? If so what could be the reason since we have dedicated cpu assigned to the guest ? What would happen if it is a physical cpu, directly assigned to the vm ? Does it experience cpu steal in this case as well ? Thanks GK

2 2

[Glance] Cancelling Weekly Meeting (23rd May)
by Pranali Deore 22 May '24

22 May '24

Hello, Since I won't be able to chair tomorrow's meeting due to my PTO, cancelling the same. See you next week! Thanks, Pranali Deore

1 0

[kolla-ansible] How to pin pip3 module in kolla-ansible
by Satish Patel 22 May '24

22 May '24

Folks, I have deployed kolla-ansible using public images so far everything is good until I hit this bug [1] requests pip module had a minor bug. Now my question is if I want to pin requests==2.31.0 version in kolla-ansible then what file should I be adding to the pin version? This is not an image building related module because it deployed on a metal host so nothing to do with building kolla images. It's a pure docker issue. 1. https://github.com/docker/docker-py/pull/3257

3 3

[tc][all][sahara] Retiring the Sahara project
by Ghanshyam Mann 21 May '24

21 May '24

Hello everyone, As you might know, the Sahara project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Sahara retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

3 9

[openstack][nova]about instance-state when resizing failed
by Nguyễn Hữu Khôi 21 May '24

21 May '24

Hello. I would like to know why we set instance-state to ERROR when resizing/migrating failed? I have a problem with resizing/migrating instances. I must reset state then shelve and unshelve instances to make it come back. Thank you for your time. Nguyen Huu Khoi

5 14

[openstack-ansible][Yoga] Unable to deploy masakari on openstack-ansible
by Danish Khan 21 May '24

21 May '24

Dear Team, My masakari playbook is failing with below error: TASK [pacemaker_corosync : Creates corosync config] **************************************************************************************************** Tuesday 21 May 2024 16:24:32 +0530 (0:00:00.369) 0:00:08.576 *********** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt' fatal: [bbs-p-swaas-compute1]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt'"} Below is few lines from /etc/ansible/roles/pacemaker_corosync/templates/corosync.conf.j2 {% if inventory_hostname in groups[pacemaker_corosync_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_corosync_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% elif pacemaker_remote_group in groups and inventory_hostname in groups[pacemaker_remote_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_remote_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% endif %} Regards, Danish Khan

2 3

[ops] Investigating Shelving/Unshelving of Instances in OpenStack with Asynchronous Functions
by Shubham Kumar Yadav 21 May '24

21 May '24

Hi, I have a customer using a Pyrhon script to shelve/unshelve instance periodicly in the openstack, *He use openstack's std library for python and thus call * if (novaC.servers.get(server).status=='ACTIVE'): (novaC, cinderC, server, 'stop') -> nova.servers.stop() while (novaC.servers.get(server).status!='SHUTOFF'): time.sleep(10) if (novaC.servers.get(server).status=='SHUTOFF'): controlServer(novaC, cinderC, server, 'shelve') -> nova.servers.shelve() seems that script uses async function, which I supose be the problem.It is possible from nova API manipulate async requests ?

1 0

[ops] help with manila ceph backend
by Shubham Kumar Yadav 21 May '24

21 May '24

Hi, im trying to install manila in my openstack cluster, but i see some logs in the manila-share pod which i dont understand much logs: *2024-05-20 07:30:13.731 8 ERROR manila.share.manager [None req-712d1a81-bbfe-4e90-a2c8-8b7ae3650eff - - - - - -] Error encountered during initialization of driver CephFSDriver@lab-11053-26006-ceph-1@cephfsnative1: manila.exception.ShareBackendException: Share backend error: Error reading ceph version to set the default target. Please check your Ceph backend is reachable. 2024-05-20 07:30:13.731 8 ERROR manila.share.manager Traceback (most recent call last): 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 362, in setup_default_ceph_cmd_target 2024-05-20 07:30:13.731 8 ERROR manila.share.manager ceph_major_version = self.ceph_mon_version['major'] 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 382, in ceph_mon_version2024-05-20 07:30:13.731 8 ERROR manila.share.manager output = rados_command(self.rados_client, "version", target=('mon', )) 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 402, in rados_client2024-05-20 07:30:13.731 8 ERROR manila.share.manager self._rados_client = rados.Rados( 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "rados.pyx", line 398, in rados.Rados.__init__ 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "rados.pyx", line 459, in rados.Rados.__setup 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "rados.pyx", line 540, in rados.Rados.conf_read_file 2024-05-20 07:30:13.731 8 ERROR manila.share.manager rados.ObjectNotFound: [errno 2] RADOS object not found (error calling conf_read_file) 2024-05-20 07:30:13.731 8 ERROR manila.share.manager 2024-05-20 07:30:13.731 8 ERROR manila.share.manager During handling of the above exception, another exception occurred: 2024-05-20 07:30:13.731 8 ERROR manila.share.manager 2024-05-20 07:30:13.731 8 ERROR manila.share.manager Traceback (most recent call last): 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/manager.py", line 366, in _driver_setup 2024-05-20 07:30:13.731 8 ERROR manila.share.manager self.driver.do_setup(ctxt) 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 269, in do_setup 2024-05-20 07:30:13.731 8 ERROR manila.share.manager self.setup_default_ceph_cmd_target() 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 366, in setup_default_ceph_cmd_target 2024-05-20 07:30:13.731 8 ERROR manila.share.manager raise exception.ShareBackendException(msg=msg) 2024-05-20 07:30:13.731 8 ERROR manila.share.manager manila.exception.ShareBackendException: Share backend error: Error reading ceph version to set the default target. Please check your Ceph backend is reachable. 2024-05-20 07:30:13.731 8 ERROR manila.share.manager 2024-05-20 07:30:14.305 7 ERROR manila.share.drivers.generic [None req-3ade5267-d42c-4ce1-abba-74b154cdd903 - - - - - -] Failed to get Nova VM. No server with a name or ID of 'None' exists.: manila.exception.ManilaException: Failed to get Nova VM. No server with a name or ID of 'None' exists. 2024-05-20 07:30:15.736 8 ERROR manila.share.manager [None req-712d1a81-bbfe-4e90-a2c8-8b7ae3650eff - - - - - -] Error encountered during initialization of driver CephFSDriver@lab-11053-26006-ceph-1@cephfsnative1: rados.ObjectNotFound: [errno 2] RADOS object not found (error calling conf_read_file)* i have added in manila conf(manifest) : [cephfsnative1]driver_handles_share_servers = Falseshare_backend_name = CEPHFSNATIVE1share_driver = manila.share.drivers.cephfs.driver.CephFSDrivercephfs_conf_path = /etc/ceph/ceph.confcephfs_protocol_helper_type = CEPHFScephfs_auth_id = manilacephfs_cluster_name = cephcephfs_filesystem_name = cephfs could you please help we understanding the issue and resolving it please. Hope to hear from you soon Thank you!

2 1

Subject: [tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-19)
by Goutham Pacha Ravi 20 May '24

20 May '24

Hello Stackers, We're counting down 19 weeks to the 2024.2 (Dalmatian) release [1], and it's been a week of spring cleaning at the OpenStack Technical Committee. This is likely the case with project repositories across the board. There have been a few governance changes in the past week that I'd like to brief you on. At the outset, we merged an update to the upper-constraints, allowing SQLAlchemy 2.0, dropping sqlalchemy-migrate, and bumping the version of Alembic [2]. If you happen to meet Stephen Finucane (sfinucane) in person, do buy him a beverage of his choice, or several. This was no small effort. Thanks, Stephen! Over the past several releases, we've seen decreased activity in some OpenStack projects. We tagged these projects as "Inactive" [3] during past release cycles. We pursued the retirement of some of these projects in the past week. A shout out to Ghanshyam Mann (gmann) for driving this effort! We followed our process on project team removals [4]. It's possible, however, that there are unexpected side effects of deleting code in these project repositories. This could be CI jobs failing in actively maintained projects because they relied on deleted code from retired repositories or documentation updates that we missed. Please bear with us as we learn and adjust, and do let us know if we could improve the tooling or our retirement process. === Weekly Meeting === Last week's IRC meeting coincided with the Sovereign Cloud Stack Summit (May 14th) and the Open Infra Day (May 15th) in Berlin, Germany. However, we had a quorum and were able to go through a number of important discussion items [5]. - We discussed the removal of eventlet and migration to other concurrency/threading patterns. The consensus remained that shared tooling like oslo libraries should not dictate a specific threading model. A suggestion was made for the TC to provide recommendations rather than enforce a specific model. We're looking for help with this! All projects currently relying on eventlet must be finding ways to remove their use of it, and we're looking to use your expertise to frame a recommendation across the board. - On the topic of cleaning up additional maintainers on OpenStack packages on PyPi, Clark Boylan (clarkb) and Jeremy Stanley (fungi) helped me isolate PyPi repositories that "openstackci" didn't have permissions to make edits. We have earmarked [6] packages where we'll be removing additional maintainers this week. There's more work to be done here. So please keep an eye on future updates. - Dan Smith (dansmith) revived an old effort to setup OSC as a service on devstack; the patch has now merged [7]. Please consider using it locally and on CI jobs if you would like the speedup. There are some CI changes popping up already [8]. Our next weekly IRC meeting is tomorrow. The agenda for this meeting is up [9]. Please join us, and remember, you can always add new meeting items! === Governance Proposals === ==== Merged ==== Retire Solum project | https://review.opendev.org/c/openstack/governance/+/919211 Retire Murano project | https://review.opendev.org/c/openstack/governance/+/919358 Retire Sahara project | https://review.opendev.org/c/openstack/governance/+/919374 Retire Senlin project | https://review.opendev.org/c/openstack/governance/+/919347 Retire ec2-api project | https://review.opendev.org/c/openstack/governance/+/919394 Neutron: Retire networking-ovn | https://review.opendev.org/c/openstack/governance/+/919700 ==== Open for review/discussion ==== Migrate eventlet usages to asyncio | https://review.opendev.org/c/openstack/governance/+/902585 Clarify the project retirement vs project's repository retirement | https://review.opendev.org/c/openstack/governance/+/919984 Retire devstack-gate | https://review.opendev.org/c/openstack/governance/+/919629 Update to include docs and miscellaneous repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833 And finally, the OpenStack Technical Committee serves you! We're always willing to chat with you and would love feedback. === How to contact the TC === You can reach out to the TC in multiple ways: 1. Email: you can send an email with the tag [tc] on this email list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel. 3. Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 1800 UTC [9]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://review.opendev.org/c/openstack/requirements/+/879743 [3] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [4] https://governance.openstack.org/tc/reference/dropping-projects.html [5] https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-14-18.00.log.html [6] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L52 [7] https://review.opendev.org/c/openstack/devstack/+/676016 [8] https://review.opendev.org/q/topic:%22ocaas%22 [9] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Issue in Devstack Setup
by Lohit S 20 May '24

20 May '24

Hi Team, I had tried to set the DevStack in the local Linux Ubuntu machine. During that time I had executed the ./stack.sh file. Following issue is generated. How to fix this issue. Collecting fixtures>=3.0.0 (from stestr>=1.0.0->os-testr) Using cached fixtures-3.0.0-py2.py3-none-any.whl.metadata (19 kB) Collecting PyYAML>=3.10.0 (from stestr>=1.0.0->os-testr) Using cached PyYAML-5.4.1.tar.gz (175 kB) Installing build dependencies ... done Getting requirements to build wheel ... error error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> [54 lines of output] running egg_info writing lib3/PyYAML.egg-info/PKG-INFO writing dependency_links to lib3/PyYAML.egg-info/dependency_links.txt writing top-level names to lib3/PyYAML.egg-info/top_level.txt Traceback (most recent call last): File "/opt/stack/data/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module> main() File "/opt/stack/data/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main json_out['return_val'] = hook(**hook_input['kwargs']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/stack/data/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel return hook(config_settings) ^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=['wheel']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires self.run_setup() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 311, in run_setup exec(code, locals()) File "<string>", line 271, in <module> File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/__init__.py", line 104, in setup return distutils.core.setup(**attrs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 184, in setup return run_commands(dist) ^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 200, in run_commands dist.run_commands() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands self.run_command(cmd) File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 967, in run_command super().run_command(command) File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 988, in run_command cmd_obj.run() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 321, in run self.find_sources() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 329, in find_sources mm.run() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 550, in run self.add_defaults() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 588, in add_defaults sdist.add_defaults(self) File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/sdist.py", line 102, in add_defaults super().add_defaults() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/command/sdist.py", line 250, in add_defaults self._add_defaults_ext() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/command/sdist.py", line 335, in _add_defaults_ext self.filelist.extend(build_ext.get_source_files()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<string>", line 201, in get_source_files File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/cmd.py", line 107, in __getattr__ raise AttributeError(attr) AttributeError: cython_sources [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. +inc/python:pip_install:1 exit_trap +./stack.sh:exit_trap:549 local r=1 ++./stack.sh:exit_trap:550 jobs -p +./stack.sh:exit_trap:550 jobs= +./stack.sh:exit_trap:553 [[ -n '' ]] +./stack.sh:exit_trap:559 '[' -f '' ']' +./stack.sh:exit_trap:564 kill_spinner +./stack.sh:kill_spinner:459 '[' '!' -z '' ']' +./stack.sh:exit_trap:566 [[ 1 -ne 0 ]] +./stack.sh:exit_trap:567 echo 'Error on exit' Error on exit +./stack.sh:exit_trap:569 type -p generate-subunit +./stack.sh:exit_trap:572 [[ -z /opt/stack/logs ]] +./stack.sh:exit_trap:575 /opt/stack/data/venv/bin/python3 /home/lohit/OpenSource/openstack/Org/devStack/devstack/tools/worlddump.py -d /opt/stack/logs World dumping... see /opt/stack/logs/worlddump-2024-05-14-161809.txt for details +./stack.sh:exit_trap:584 exit 1

5 7

[magnum] Cancelling meeting 22 May
by Jake Yip 20 May '24

20 May '24

Hi all, I will have to cancel this week's meeting due to work commitments. Regards, Jake

1 0

Heat problem
by Mohamed Ridha ZOUAREG 19 May '24

19 May '24

Hi, I'm trying to run a magnum cluster on Linux:Ubuntu 22.04 Openstack 2023.1 I've installed all the principal services + cinder And I'm facing now a problem with kub master creation after checking heat engine logs I found this one : Resource ResourceGroup "kube_masters" [010ab794-10cc-10cc-4348-b154-06fc729c6357] Stack "test-ix2mxcfq6vy6" [d38b91a2-0fa2-42d9-be3f-d815d18a3de8] is locked or does not exist And also heat.common.exception.ResourceFailure: resources[0]: Stack CREATE cancelled

1 0

Fwd: Problem with magnum cluster creation
by Mohamed Ridha ZOUAREG 19 May '24

19 May '24

Hi, I'm trying to run a magnum cluster on Linux:Ubuntu 22.04 Openstack 2023.1 I've installed all the principal services + cinder And I'm facing now a problem with kub master creation after checking heat engine logs I found this one : Resource ResourceGroup "kube_masters" [010ab794-10cc-10cc-4348-b154-06fc729c6357] Stack "test-ix2mxcfq6vy6" [d38b91a2-0fa2-42d9-be3f-d815d18a3de8] is locked or does not exist And failure resource[0] as you can see in the photos

1 0

[mistral] Reusing “pypi.org/projects/mistral”
by Renat Akhmerov 18 May '24

18 May '24

Hi! I’m Renat who originally created the Mistral Workflow project and I was a PTL for many cycles. I’ve not been in the loop for more than 3 years now so I’m not sure what’s going on in the community now. Neither in OpenStack, nor particularly in Mistral. I heard the rumors though that Mistral upstream life is not longer active. I’d love to hear some feedback on that. The reason I’m asking is that I’ve been asked to let other folks with a big business to reuse the pypi name “mistral”. Seemingly, there’s no many unique active users now, but there are some probably. So before answering to them “no”, I’d like to understand if it’s really impossible (broken OpenStack CI pipelines, other businesses potentially suffering etc etc). Would it make sense also to consider moving “mistral” to something like “mistral-workflow” on pypi? Would appreciate any input. Thanks Renat Akhmerov

4 4

Horizon UI Theme.
by Michael Knox 17 May '24

17 May '24

I am looking to do a custom theme with Horizon. I looked some on github etc, but I am noticing on the login screen a "header" bar and I can't see where it's coming from. Even the default theme has it. It looks like something in the class for "login" or maybe it's the "container", I am not a CSS guy, more suited to crayons. Any pointers would be appreciated. Cheers. Knox.

3 4

[release] Release countdown for week R-19, May 20-24
by Elõd Illés 17 May '24

17 May '24

Development Focus ----------------- We are now past the Dalmatian-1 milestone. Teams should now be focused on feature development. General Information ------------------- Our next milestone in this development cycle will be Dalmatian-2, on July 4th, 2024. This milestone is when we freeze the list of deliverables that will be included in the 2024.2 Dalmatian final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the deliverables/dalmatian directory of the openstack/releases repository. Now is also generally a good time to look at bugfixes that were introduced in the master branch that might make sense to be backported and released in a stable release. If you have any question around the OpenStack release process, feel free to ask on this mailing-list or on the #openstack-release channel on IRC. Upcoming Deadlines & Dates -------------------------- Dalmatian-2 Milestone: July 4th, 2024 Előd Illés irc: elodilles @ #openstack-release

1 0

[neutron] bug deputy report for week of 2024-05-13
by Bence Romsics 17 May '24

17 May '24

Hi Team, I'm sending this deputy report on Friday already, because this weekend and the whole next week I'll be away from computers. In the last 5 days the following new bugs were reported. We have 3 unassigned, please have a look! [critical] * https://bugs.launchpad.net/neutron/+bug/2065821 cover job started to fail with Killed unassigned, gate failure [high] * https://bugs.launchpad.net/neutron/+bug/2065701 set_gateway_mtu fails if one of the lrp is deleted while it's running fix and backports are in progress: https://review.opendev.org/q/topic:bug/2065701 * https://bugs.launchpad.net/neutron/+bug/2065707 Trunk plugin fails to push trunk object through OVO rpc endpoint on AFTER_DELETE fix in progress: https://review.opendev.org/c/openstack/neutron/+/919858, https://review.opendev.org/c/openstack/neutron/+/9198589 [medium] * https://bugs.launchpad.net/neutron/+bug/2065743 CLI arguments for rbac create are misleading and possibly incorrect unassigned, fix needed both in neutron and openstackclient [ovn-octavia-provider] * https://bugs.launchpad.net/neutron/+bug/2065566 [ovn-octavia-provider] Return DELETED on member_delete for non-existing members fix in progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/919482 * https://bugs.launchpad.net/neutron/+bug/2065822 [ovn-octavia-provider] functional job fails with "oslo_db.exception.DBReferenceError: (sqlite3.IntegrityError) FOREIGN KEY constraint failed when inserting port bindings unassigned, low frequency gate failure [taas] * https://bugs.launchpad.net/tap-as-a-service/+bug/2065924 [OSP][TaaS][sqlalchemy] sqlalchemy updated to 2.0 breaks TaaS fix in progress: https://review.opendev.org/c/openstack/tap-as-a-service/+/919934 [needs further analysis] * https://bugs.launchpad.net/neutron/+bug/2065577 [ml2/ovs]Empty binding_levels=[] cause ovs-agent skipped to process port Cheers, Bence

1 0

[publiccloud-sig] Summary Foundation Forum @ OpenInfra Day Berlin 2024
by Felix Kronlage-Dammers 17 May '24

17 May '24

Hi, this Wednesday the OpenInfra Day Berlin 2024 happened. Thanks to the various people (such as Nils Magnus, Kurt Garloff, Robert Holling and Friederike Zelke) who were involved in organizing this event. As part of the OpenInfra Day there was a Forum-style session on Interoperability between clouds. The session was initiated by Josephine Seifert, Artem Goncharov, Tobias Rydberg, Adrien Cunin and myself. The etherpad is here: https://etherpad.opendev.org/p/Interop-Forum The intro slides to the session are here: https://input.scs.community/p/KWywBKwBW#/ The 45 minutes we had quickly passed in the discussion - it (once again) did show that this is a topic that does need to be dealt with and it is not enough to just do it every now and then (doh!) - these topics will be picked up as part of the Public-Cloud SIG. However, the Public-Cloud SIG needs more people joining (which was another part of the idea of this session: make advertisement for our work in the Public-Cloud SIG and get more people to join). Tobias and I will see that we will schedule some Public-Cloud SIG calls that are timezone-friendly for the US-/Canada people as well. The next regular call of the Public-Cloud SIG will be on May 29th at 0700 UTC (but a reminder will be sent out couple days in advance). felix

1 0

[nova] May 22th meeting is CANCELLED
by Sylvain Bauza 17 May '24

17 May '24

As said above, the weekly nova meeting on May 22 2024 is CANCELLED. You can join us in #openstack-nova if you have some questions. Thanks, -Sylvain

1 0

[ptl][tc] OpenStack packages PyPi additional external maintainers audit & cleanup
by Ghanshyam Mann 16 May '24

16 May '24

Hi PTLs, As you might know or have seen for your project package on PyPi, OpenStack deliverables on PyPi have additional maintainers, For example, https://pypi.org/project/murano/, https://pypi.org/project/glance/ We should keep only 'openstackci' as a maintainer in PyPi so that releases of OpenStack deliverables can be managed in a single place. Otherwise, we might face the two sets of maintainers' places and packages might get released in PyPi by additional maintainers without the OpenStack project team knowing about it. One such case is in Horizon repo 'xstatic-font-awesome' where a new maintainer is added by an existing additional maintainer and this package was released without the Horizon team knowing about the changes and release. - https://github.com/openstack/xstatic-font-awesome/pull/2 To avoid the 'xstatic-font-awesome' case for other packages, TC discussed it in their weekly meetings[1] and agreed to audit all the OpenStack packages and then clean up the additional maintainers in PyPi (keep only 'openstackci' as maintainers). To help in this task, TC requests project PTL to perform the audit for their project's repo and add comments in the below etherpad. - https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup Thanks to knikolla to automate the listing of the OpenStack packages with additional maintainers in PyPi which you can find the result in output.txt at the bottom of this link. I have added the project list of who needs to check their repo in etherpad. - https://gist.github.com/knikolla/7303a65a5ddaa2be553fc6e54619a7a1 Please complete the audit for your project before March 15 so that TC can discuss the next step in vPTG. [1] https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-11-16.00.log.html#… -gmann

18 27

openstack / sahara Project
by Moein Engineer 15 May '24

15 May '24

Hello Greetings We have decided to use platform openstack / sahara to set up a big data cluster in our company. Has the support and development of project openstack / sahara ended? I checked the last commit is for the last 6 months and for version 19. If project openstack / sahara is not developed and ends, what project has replaced it? Regards

2 1

openstack / sahara
by Moein 15 May '24

15 May '24

1 0

Logscraper host and OpenSearch service upgrade
by Daniel Pawlik 15 May '24

15 May '24

Hello, We would like to notify you that the OpenSearch service [1] would be updated to a newer version on 2024-05-15 at 01:00 PM UTC. This procedure might take a while, depending of the cluster size. During that time, the OpenSearch service would not be available. If anyone has any doubts, please reply to the email. Dan [1] - https://opensearch.logs.openstack.org/_dashboards/app/home

1 1

[kolla-ansible] support for FWaaS/LBaaS?
by garcetto 15 May '24

15 May '24

good morning, does kolla support fwaas or lbaas? thank you

3 4

Antelope compute: failure to live migrate VMs from Yoga compute
by Michel Jouvin 15 May '24

15 May '24

Hi, In a Yoga cloud, I upgraded all the core services and 1 compute to Antelope (directly from Yoga, using a SLURP upgrade). This cloud has 4 compute servers, all using the same HW (Dell FX2/FC630 with Broadwell CPUs). After the upgrade, any attempt to live migrate a VM from a Yoga compute to the Antelope compute fails with the following error in destination/Antelope nova-compute.log: nova.exception.MigrationPreCheckError: Migration pre-check error: Unacceptable CPU info: CPU doesn't have compatibility. This looks weird. I don't see anything in the release notes related to this problem, except a mention that the API used to do the comparison has changed ("This change replaces the usage of older API, compareCPU(), with the new one, compareHypervisorCPU()."). "virsh capabilities" reports the same thing for a Yoga and an Antelope compute, except the addition of a feature 'flush-l1d' in Antelope and the addition of 2 new attributes in the '<cpu>' section: <signature family='6' model='79' stepping='1'/> <maxphysaddr mode='emulate' bits='46'/> I tend to think that additions are not a problem in general and so it doesn't seem to explain the problem I'm facing. Anybody with a similar experience? It seems to me a different problem that the one that has been faced in the past (before Nova 20 if I'm right) and described in several posts, with CPU model improperly detected (in particular Broadwell vs. Icelake). Thanks in advance for any hint/suggestion. Best regards, Michel

3 4

[largescale-sig] Next meeting: May 15, 9utc
by Thierry Carrez 15 May '24

15 May '24

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240515T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 2

launch vm and its LVM cinder volumes on same host
by Morteza FarkhondePour 15 May '24

15 May '24

0 <https://serverfault.com/posts/1159435/timeline> I have an OpenStack *Antelope* version installed via Kolla-Ansible, and I have several compute hosts with LVM volume types. When I create an instance using an LVM volume, I expect both the volume and the instance create on the same host. However, they end up on different hosts. For example, the volume is located on d13-compute43@localA#localA, whereas the instance is on d13-compute51

1 0

[kolla] Weekly meeting today (15th May 2024) cancelled
by Michał Nasiadka 14 May '24

14 May '24

Hello Koalas, Weekly meeting today is cancelled due to key participants (including me) not being able to attend. Let’s meet next week (22nd May 2024) - see you then! Michal

1 0

OpenInfra Summit Asia'24 CFP closing in two weeks
by Jeremy Stanley 14 May '24

14 May '24

The OpenInfra Summit Asia'24 is the first community-led Summit[0], hosted by the OpenInfra Korea User Group in collaboration with other OpenInfra user groups throughout Asia. The CFP is currently open and accepting applications until May 29, 2024, so there's only two weeks left to get your proposals submitted[1]. Keep in mind that Summit talks are often professionally recorded and re-watched by a much larger global audience, having a broad impact for years after the event concludes, so your reach can be far greater than just the people who happen to be in the room at that moment. This time, the Summit will be co-located with the OCP (opencompute.org) Regional Summit APAC and will showcase the latest advancements in open source infrastructure software and hardware. If you want to present but are struggling to to come up with ideas, "beginner" content is always a crowd pleaser (setting up your first environment, tips for new contributors), but this could also be of particular interest for the growing local community in Korea. Since this event is occurring alongside one for the Open Compute Project, hardware-related topics might serve to draw in participants from their community and help grow our own through the sort of collaboration we're best known for. Upgrade stories and talks about reducing complexity are also something our users are especially keen to hear about. For that matter, talks about Networking (including 5G telephony) or integration with adjacent community tech (Ceph, Kubernetes, OVN) would be great to show how OpenStack is really an integral piece of the larger open source ecosystem. If you want to attend and your employer cannot fund your travel, the OpenInfra Foundation is continuing the OpenInfra Travel Support program. You can apply for travel support[1] until May 29. If you have any questions or want help (even if it's just to bounce ideas off me for a talk you're thinking about proposing), feel free to reply or find me (fungi) in the #openstack channel on the OFTC IRC network. [0] Register for the OpenInfra Summit Asia: https://2024.openinfraasia.org/ [1] Submit to the CFP: https://openinfrafoundation.formstack.com/forms/openinfra_asia_summit_2024 [2] Apply for the OpenInfra Travel Support Program: https://openinfrafoundation.formstack.com/forms/openinfra_tsp -- Jeremy Stanley

1 0

Boot an uefi volume that migrated from VMware ESXI
by luckydog xf 14 May '24

14 May '24

Hi, list, I migrated a volume from VMware ESXI VMDK, and originally on VMware platform it's EFI boot mode and secure boot enabled. I cloned the entire VMDK by clonzilla and restored on OpenStack as a volume. I referred to this link https://docs.openstack.org/nova/latest/admin/secure-boot.html and uploaded that volume as an image. Then set properties. Finally, I launched an instance with a target image, however, it cannot boot up with a blank and dark screen. What's the right way to implement this? Thanks.

2 11

[nova] Our first spec review day for Dalmatian
by Sylvain Bauza 14 May '24

14 May '24

Hey folks, As agreed during the PTG, we'll have two spec review days this cycle. Next Tuesday, ie. May 14 2024, we'll have the first one. Please make sure you can upload your spec before this and please be around on IRC on Tuesday (if you can) so we could discuss your spec change if we need. Thanks, -Sylvain

1 1

[openstack][kolla-ansible][keystone]upgrade from yoga to zed error keystone database
by Nguyễn Hữu Khôi 13 May '24

13 May '24

Hello. I upgraded from yoga to zed but i encounter this error as a keystone log. https://www.editpad.org/?edit-id=CNujHK962K70e93ae8 I tried to remove this table but this error still appears with other tables. My env: ubuntu22.04 openstack with kolla ansible as the deployment tool Thank you. Regards Nguyen Huu Khoi

2 4

[neutron] Bug deputy report for week of May 6th
by Miguel Lavalle 13 May '24

13 May '24

Hi, I was the Neutron bugs deputy last week. Following is a brief summary of the reported bugs: Critical bugs ----------------- None High bugs -------------- https://bugs.launchpad.net/neutron/+bug/2065094 OVN revision number is bumped on noop port update. Assignee Jakub Libosvar. Released fix: https://review.opendev.org/c/openstack/neutron/+/918492 https://bugs.launchpad.net/neutron/+bug/2065459 ovn-octvia-provider: RuntimeError: cannot join current thread. In progress. Assignee Terry Wilson. Proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/919229 https://bugs.launchpad.net/neutron/+bug/2065460 ovn-octavia-provider results in a new OVSDB connection for every Octavia API request. In progress. Assignee Terry Wilson. Proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/919229 https://bugs.launchpad.net/neutron/+bug/2065566 [ovn-octavia-provider] Return DELETED on member_delete for non-existing members. In progress. Assignee Fernando Royo/ Proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/919482 Medium bugs ------------------ * https://bugs.launchpad.net/neutron/+bug/2065145 AttributeError: 'MetadataDriver' object has no attribute 'monitors' in L3 agent logs, Assignee Brian Haley. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/918674 Low bugs ------------- None Wishlist bugs ------------------ https://bugs.launchpad.net/neutron/+bug/2065198. Allow ml2 MechanismDrivers to start own rpc listeners. Gathering more input from submitter at the moment

1 0

Nova filters
by Gk Gk 13 May '24

13 May '24

Hi, In the Antelope version nova scheduler, is there an option for filtering hypervisors based on available disk space ? I cant find the option "DiskFilter' in the latest documentation for antelope. How to achieve this ? Thanks G.K

2 4

[DNS] RFH: Something is answering DNS PTR queries with UDP and not EDNS
by Philipp Hahn 13 May '24

13 May '24

Hello, I'm new to this list and relatively new to OpenStack, so please be patient with me. Our infrastructure provider is hosting OpenStack for us and I observed the following irritating behavior: If my Linux VM does a reverse-IP-lookup (PTR) something™ seems to intercept those PTR queries on their way from the VM to the *configured* DNS server and answers them itself, returning the name of the VM inside some pre-configured domain: > # dig +nocmd +nocomments +nostats +noedns -x 10.201.0.211 > ;211.0.201.10.in-addr.arpa. IN PTR > 211.0.201.10.in-addr.arpa. 3600 IN PTR jenkins-ucs-5-0-ucs-5-0-7-autotestjoinopenstack-sambaversion-no.a.customers.regiocloud.tech. > > # getent hosts 10.201.0.211 > 10.201.0.211 jenkins-ucs-5-0-ucs-5-0-7-autotestjoinopenstack-sambaversion-no.a.customers.regiocloud.tech > > # python3 -c 'import DNS;req=DNS.DnsRequest("211.0.201.10.in-addr.arpa.",qtype="PTR",server=["10.201.0.211"], protocol="udp");res=req.req();print(res.answers[0]["data"])' > jenkins-ucs-5-0-ucs-5-0-7-autotestjoinopenstack-sambaversion-no.a.customers.regiocloud.tech > > # python3 -c 'import dns.resolver;r=dns.resolver.Resolver(configure=False);r.nameservers=["10.201.0.211"];r.edns=False;a=r.query("211.0.201.10.in-addr.arpa.","PTR",tcp=False);print(list(a))' > [<DNS IN PTR rdata: jenkins-ucs-5-0-ucs-5-0-7-autotestjoinopenstack-sambaversion-no.a.customers.regiocloud.tech.>] This only happens when UDP is used an EDNS is disabled: As soon as I use TCP or force EDNS my queries arrives at the configured DNS server and I get back the expected answer: > # dig +nocmd +nocomments +nostats +edns -x 10.201.0.211 > ;211.0.201.10.in-addr.arpa. IN PTR > 211.0.201.10.in-addr.arpa. 172800 IN PTR master096.autotest096.test. > 201.10.in-addr.arpa. 10800 IN NS master096.autotest096.test. > master096.autotest096.test. 80600 IN A 10.201.0.211 > > # dig +nocmd +nocomments +nostats +edns +tcp -p 53 -x 10.201.0.211 > ;211.0.201.10.in-addr.arpa. IN PTR > 211.0.201.10.in-addr.arpa. 172800 IN PTR master096.autotest096.test. > 201.10.in-addr.arpa. 10800 IN NS master096.autotest096.test. > master096.autotest096.test. 80600 IN A 10.201.0.211 > > # dig +nocmd +nocomments +nostats +noedns +tcp -p 53 -x 10.201.0.211 > ;211.0.201.10.in-addr.arpa. IN PTR > 211.0.201.10.in-addr.arpa. 172800 IN PTR master096.autotest096.test. > 201.10.in-addr.arpa. 10800 IN NS master096.autotest096.test. > master096.autotest096.test. 80600 IN A 10.201.0.211 > > # python3 -c 'import DNS;req=DNS.DnsRequest("211.0.201.10.in-addr.arpa.",qtype="PTR",server=["10.201.0.211"], protocol="tcp");res=req.req();print(res.answers[0]["data"])' > master096.autotest096.test > > # python3 -c 'import dns.resolver;r=dns.resolver.Resolver(configure=False);r.nameservers=["10.201.0.211"];r.edns=False;a=r.query("211.0.201.10.in-addr.arpa.","PTR",tcp=True);print(list(a))' > [<DNS IN PTR rdata: master096.autotest096.test.>] > > # python3 -c 'import dns.resolver;r=dns.resolver.Resolver(configure=False);r.nameservers=["10.201.0.211"];r.edns=True;a=r.query("211.0.201.10.in-addr.arpa.","PTR",tcp=True);print(list(a))' > [<DNS IN PTR rdata: master096.autotest096.test.>] > > # python3 -c 'import dns.resolver;r=dns.resolver.Resolver(configure=False);r.nameservers=["10.201.0.211"];r.edns=True;a=r.query("211.0.201.10.in-addr.arpa.","PTR",tcp=False);print(list(a))' > [<DNS IN PTR rdata: master096.autotest096.test.>] I already talked to out provider and spend multiple hours searching the internet or even having a look at the source code of Neutron myself, but did not find any clue so far. Can someone please enlighten me and tell me, how I (or our provider) can disable that "UDP DNS intercept behavior" as that breaks our current use-case, especially as I seldomly can configure our applications to (not) use UDP / EDNS, so depending on which resolver library they use they get different answers to the same query. Thank you in advance. Philipp Hahn -- Philipp Hahn Open Source Software Engineer Univention GmbH Mary-Somerville-Str. 1 28359 Bremen Germany | Deutschland Phone: +49 (0)421 22232-0 | E-Mail: info(a)univention.de https://www.univention.de | https://www.univention.com Managing Directors: Peter H. Ganten, Stefan Gohmann Local court: Amtsgericht Bremen HRB 20755 | Ust-ID: DE220051310 If you are not the intended recipient of this mail, please contact the sender and delete this message. Any unauthorized copying of this message or unauthorized distribution of the information contained herein is prohibited.Information on the processing of your personal data can be found here: https://www.univention.com/privacy-statement

2 1

Re: CAD applications on OpenStack
by Francesco Di Nucci 13 May '24

13 May '24

You're welcome have you also thought about having a chat with CAD vendor's team? Maybe they encountered it as a problem, as it's more about the CAD and less about having Windows VMs on OpenStack By the way, when a conversation is in a list, reply to all to include the list ;) Best regards Francesco Di Nucci On 13/05/24 12:20, Arne Wiebalck wrote: > Thanks, Francesco! > > Licenses are a concern and we're looking at that. > > What we're not really clear on if this approach works latency- / concurrency wise. > We will probably simply try :) > > Thanks again! > Arne > > -- > Dr. Arne Wiebalck > Group Leader, Compute and Devices Group > CERN IT > > ________________________________________ > From: Francesco Di Nucci <francesco.dinucci(a)na.infn.it> > Sent: Thursday, 9 May 2024 08:12 > To: Arne Wiebalck > Subject: Re: CAD applications on OpenStack > > Hi, > > former CAD user here - first of all I'd advice to clear with your legal > department if your license allows you to use the CAD in VMs. > > AFAIK CATIA runs on Windows, so containerization is not possible unless > you manage to get the CAD running in Wine, and you should configure PCI > passthrough > > (https://docs.openstack.org/nova/2024.1/admin/pci-passthrough.html) to > use a graphic card in the VMs. > > Regards > > Francesco Di Nucci > > On 05/05/24 12:04, Arne Wiebalck wrote: >> Dear all, >> >> We're looking into integrating the use case of CAD applications, such as CATIA V5/6 or CATIA 3DEXPERIENCE, into our OpenStack deployment, with the goals of increased resource sharing >> and to reduce the park of individual workstations we have for this at the moment. >> >> If anyone has experience running such applications on top of OpenStack (on individual VMs >> with GPU access, on bare metal servers with concurrent sessions, maybe even containerised ...) >> and would like to share what they have done, it'd be great if you got in touch with me. >> >> Thanks! >> Arne >> >> -- >> Arne Wiebalck >> CERN IT >> >> > >

1 0

Re: Nova filters
by Gk Gk 13 May '24

13 May '24

Hi, In the Antelope version nova scheduler, is there an option for filtering hypervisors based on available disk space ? I cant find the option "DiskFilter' in the latest documentation for antelope. How to achieve this ? Thanks G.K

1 0

Rabbit mq connections keep on going up, why channels and connections not closing?
by Shrey Chauhan 13 May '24

13 May '24

Hi all, I am observing a behaviour which I am not sure is right or wrong, or something I should be concerned about? Currently I am using openstack xena with rabbit-mq message broker. rabbit mq version is 3.8.3 amqp version 5.0.8 I have installed rabbit management plugin on my cluster, and I observe whenever I perform any task like a resize. My connection and channel counts go up, and with every operation it goes up. I am worried that at some point I will hit some kind of connection threshold. I just want to understand if services like nova, cinder reuse an open rabbit mq connection or reopen for every operation, and if they open msg queue connection for every operation do they close the connection once the action is done Am I missing configuration in my setup of rabbit mq with openstack? Please help me understand this scenario. Thanks for help in advance. Thanks, Shrey Chauhan

1 0

[ops] Inquiry Regarding Addition of DH Groups in OpenStack VPNaaS
by Shubham Yadav 13 May '24

13 May '24

Hello , I hope this message finds you well. I am reaching out to inquire about the possibility of adding additional DH (Diffie-Hellman) groups to the VPNaaS (VPN as a Service) project in OpenStack. Currently, our setup involves using DH groups 14, 16, 20, and 21 on Fortigate routers. However, the available DH groups at the OpenStack Web UI for creating IPSEC policies are limited to groups 2, 5, and 14. Could you please provide insights into whether there are plans to introduce more DH groups into the VPNaaS project? This addition would greatly benefit our configurations and improve compatibility with our existing infrastructure. Thank you in advance for any information or guidance you can provide on this matter. Best regards, Shubham

2 1

[oslo][release] Changing back release model of tooz ?
by Takashi Kajinami 13 May '24

13 May '24

Hello, As you may know, tooz was moved to the independent release model[1] after wallaby release because of its stable code base at that time. However, we introduced several features/improvements in tooz during a few cycles and I'm wondering if we can revisit its status now. One actual problem I'm seeing now is that, we recently got a bug report[2] about the redis sentinel support which we added during 2024.1 cycle but we can't backport the required bug fix to 2024.1 because of no stable branch. Given the situation, I'm wondering if it makes sense (and is possible) to move tooz back to the cycle-with-intermediary model, and create 2024.1 branch from 6.1.0 (the last release during 2024.1 cycle) now, so that we can maintain 2024.1 releases with future bug fixes brackported. [1] https://review.opendev.org/c/openstack/releases/+/788230 [2] https://bugs.launchpad.net/python-tooz/+bug/2063857 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

4 5

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-20)
by Goutham Pacha Ravi 12 May '24

12 May '24

Hello Stackers, We're officially in milestone-1 week for the 2024.2 (Dalmatian) release cycle [1]. Teams are actively planning design specification freezes, hackathons, and bug squashes. I'm delighted to announce that three Outreachy interns have been funded to work with the OpenStack community [2]. Please join me in welcoming Mohd Ariq (tspyderboy), Okeke Christian Chima (cokeke), and Abby Nduta (AbbyNduta). Mohd Ariq and Christian will be working with members of the OpenStack Manila project team, while Abby will be working with members of the OpenStack Horizon project team. Congratulations, interns! These internships begins at the end of May and will conclude at the end of August. There have been a few governance changes in the past week that I'd like to brief you about: The "Consistent and Secure Default RBAC" goal has new milestone requirements. All projects are expected to transition oslo.policy's "enforce_scope" and "enforce_new_defaults" options to True during the 2024.2 release cycle. These options will be removed from oslo.policy during the 2025.1 release cycle. [3] openstack/kuryr and openstack/kuryr-libnetwork are now under the maintainership of the openstack/zun ("Container as a service") team. The TC has adopted a house rule to mark projects that have identified no leadership as "inactive" projects [4]. We've merged slaweq's summary of the 2023 OpenStack User Survey [5]. Thanks, slaweq, and to all of you who took the survey. === Weekly Meeting === Last week's TC meeting was held simultaneously on Zoom (a recording is on YouTube [6]) and IRC on May 7th, 2024. The meeting was logged to eavesdrop [7]. Over the years, we've come to realize that monitoring project activity through objective tools wasn't representing the picture accurately. Several mature/feature-complete projects will seemingly be "inactive," and what we're interested in assessing is whether there are active maintainers tackling security and project infrastructure concerns. Artem Goncharov (gtema) will write up a proposal to tag inactive projects more prominently. We discussed a proposal to change the Distributed Project Leadership model to require DPL liaisons to re-assert their interest at the beginning of each cycle. The proposal also suggests appointing liaisons from the TC to monitor projects that have this leadership model. TC Members would be welcome to nominate themselves as liaisons for projects following DPL if this proposal is accepted. We took some AIs to continue the cleanup of maintainers on OpenStack's packages on PyPI - an ongoing community-wide effort [8]. We discussed the open goal proposal to replace eventlet. The Technical Committee wants to ensure that we're not advocating for a one-size-fits-all solution to the problem of threading in OpenStack projects. Hence, we'd prefer not to merge the proposal to replace eventlet with asyncio. Instead, we want to encourage projects to independently explore solutions that make sense to their individual architecture - which could be asyncio, native threads, or any other threading paradigm/library. We are supportive of ensuring there's no imposition of any specific library or threading mechanism imposed via oslo libraries. JayF will be summarizing this view to this mailing list soon. The meeting concluded with an open discussion on DevStack setup time and an outdated (but relevant) proposal related to OSC as a service on DevStack. Tomorrow's meeting is back on OFTC/IRC, and the call details and agenda are at [9]. We look forward to seeing you there. The TC is always honored to chat with you, so please join us, and feel free to add anything to the agenda that you'd like to chat with us about! === Goal Proposals === As stated above, this goal proposal needs your weigh-in: - Migrate eventlet usages to asyncio (https://review.opendev.org/c/openstack/governance/+/902585) === Governance Proposals === ==== Merged ==== - Remove ref of bylaw Appendix 4 | https://review.opendev.org/c/openstack/governance/+/916942 - Add timeline to remove enforce_scope in RBAC goal | https://review.opendev.org/c/openstack/governance/+/915179 - Move openstack/kuryr and openstack/kuryr-libnetwork to Zun | https://review.opendev.org/c/openstack/governance/+/917517 - 2023 User Survey TC Question Analysis | https://review.opendev.org/c/openstack/governance/+/900516 - Add option to move leaderless project to Inactive status | https://review.opendev.org/c/openstack/governance/+/914726 ==== Open for review/discussion ==== - Update to include docs and miscellaneuos repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 - Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://www.outreachy.org/alums/2024-05/#:~:text=Openstack [3] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [4] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [5] https://governance.openstack.org/tc/user_survey/analysis-2023.html [6] https://youtu.be/-WZT7PC3sig [7] https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-07-18.00.log.html [8] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [9] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

openstack boot an instance from an IDE volume migrated from VMware
by luckydog xf 10 May '24

10 May '24

hi, list, I'm going to boot an instance from an existing volume, and it is a Windows 2016 migrated from VMware. So the bus must be set to 'ide' mode, otherwise it fails to boot up. Let's assume this volume UUID is xyz and it's bootable. I cloned it by clonezilla from VMware ESXI. since virtio drive wasn't installed in Windows, so it must be set to ide. So what's the right way to boot it from this volume and set it to IDE? I have tried lots of ways, like --- openstack server create test-windows --flavor 4 --nic net-id=7b57ee99-136f-4aa7-b3fe-a4958ec8c644 --block-device id=xxxx:disk_bus=ide and ... --block-device-mapping. But unfortunately, none of them work. And there are too many outdated docs like disk_bus=ide and bus=ide. Not sure which one works. This is fairly frustrating. I'm still struggling with this issue and need your help. Thanks a lot.

3 7

[tc][all][ec2-api] Retiring the ec2-api project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the ec2-api project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the ec2-api retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[tc][all][senlin] Retiring the Senlin project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the Senlin project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Senlin retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[tc][all][solum] Retiring the Solum project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the Solum project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Solum retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[tc][all][murano] Retiring the Murano project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the Murano project is not active and was marked 'inactive' since 2024.1 cycle[1]. Due to a critical bug in Murano, the TC needs to pass a resolution to stop its 2024.1 release[2]. In this cycle also, this project is leaderless[3] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[3], the next step is to retire the project. I'm sending this email to propose the Murano retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://governance.openstack.org/tc/resolutions/20240227-remove-murano-from… [3] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[magnum][magnum-cluster-api] Scalling Master Node
by pahrialtkj＠gmail.com 10 May '24

10 May '24

Hello all, I created a k8s cluster with 1 master and 1 worker node, I want to increase the master node to 2 or 3, I tried to do it with cluster resize/update and nodegroup create seems to be not supported and does not work, it works for the worker node, has anyone tried scaling the master node?

3 3

Re: How to check the free RAM or CPU or Disk in openstack python module
by Lajos Katona 10 May '24

10 May '24

Hi, No I meant something like this: $ openstack resource provider list +--------------------------------------+-------+------------+--------------------------------------+----------------------+ | uuid | name | generation | root_provider_uuid | parent_provider_uuid | +--------------------------------------+-------+------------+--------------------------------------+----------------------+ | 0f916a23-403f-43c3-ac57-e109bc371dba | jammy | 2 | 0f916a23-403f-43c3-ac57-e109bc371dba | None | +--------------------------------------+-------+------------+--------------------------------------+----------------------+ $ openstack resource provider inventory list 0f916a23-403f-43c3-ac57-e109bc371dba +----------------+------------------+----------+----------+----------+-----------+-------+------+ | resource_class | allocation_ratio | min_unit | max_unit | reserved | step_size | total | used | +----------------+------------------+----------+----------+----------+-----------+-------+------+ | VCPU | 4.0 | 1 | 6 | 0 | 1 | 6 | 0 | | MEMORY_MB | 1.0 | 1 | 7936 | 512 | 1 | 7936 | 0 | | DISK_GB | 1.0 | 1 | 28 | 0 | 1 | 28 | 0 | +----------------+------------------+----------+----------+----------+-----------+-------+------+ $ openstack resource provider inventory list 0f916a23-403f-43c3-ac57-e109bc371dba +----------------+------------------+----------+----------+----------+-----------+-------+------+ | resource_class | allocation_ratio | min_unit | max_unit | reserved | step_size | total | used | +----------------+------------------+----------+----------+----------+-----------+-------+------+ | VCPU | 4.0 | 1 | 6 | 0 | 1 | 6 | 1 | | MEMORY_MB | 1.0 | 1 | 7936 | 512 | 1 | 7936 | 256 | | DISK_GB | 1.0 | 1 | 28 | 0 | 1 | 28 | 1 | +----------------+------------------+----------+----------+----------+-----------+-------+------+ Recently this API was also added to Horizon (the web gui for Openstack) as hypervisor API and the compute db behind it is not preferred. Best wishes Lajos Katona (lajoskatona) Saeed <s.fazl73(a)gmail.com> ezt írta (időpont: 2024. máj. 10., P, 13:12): > Hello, > > Thanks a lot, but I didn't find the proper way for this. > > In CLI, I run *openstack hypervisor show hypervisor.domain.com > <http://hypervisor.domain.com>*, it then shows all the needed information > and data. > I run *openstack service list*, I see this: > > > +----------------------------------+------------------+-------------------------+ > | ID | Name | Type > | > > +----------------------------------+------------------+-------------------------+ > | 0a289a58588d4d00ac27ef92da8128de | keystone | identity > | > | 2cdf38eca0c0467fa856f1f1d91f8de3 | heat | orchestration > | > | 44393da92532478abd2dc1bdba1454ce | nova_legacy | compute_legacy > | > | 4cee55fd6c524134b010c65a7d406857 | ironic | baremetal > | > | 4f47c9bd69a34b5a9e0ef149823b7785 | neutron | network > | > | 59053bba36ed4944aaac7e8eb0f9ac01 | freezer | backup > | > | 670cb0faa6c64f8f82f0d19315e085a5 | trove | database > | > | 828ba6c2709349d597e469bf7fa55766 | glance | image > | > | 8c2671e5ddde47e4ae1accd2ce2eb696 | placement | placement > | > | 8c6357e12abb40e5a46b10be5f950c79 | heat-cfn | cloudformation > | > | c211ea65a3d440d1bb2add6f74423056 | watcher | infra-optim > | > | ceba54fa82f543579b245569b9fc127e | masakari | instance-ha > | > | d5c2952cc6904a0385cb20e5d39d1afe | nova | compute > | > | e238634b10db492a942e27714ee9d9b1 | gnocchi | metric > | > | f545381f4aa649a39122a258f48833fc | ironic-inspector | > baremetal-introspection | > > +----------------------------------+------------------+-------------------------+ > > If I do understand your reply correctly, you mean I should run a single > command for each server to find its free memory or CPU? For example if I > have 100 servers, I should run 100 times a command with different server > names? > > On Fri, 10 May 2024 at 10:33, Lajos Katona <katonalala(a)gmail.com> wrote: > >> Hi, >> Instead of Compute API, Placement is used for such statistics, see the >> API reference: >> https://docs.openstack.org/api-ref/placement/ >> >> You have to follow the resource providers on your compute, and resource >> providers can be in a tree with a root provider. >> For the available resources (resource classes) you have to list the >> resource provider inventories, and for >> the used resource you have to follow the allocations. >> Check the API ref and see the possibilities with CLI first perhaps. Be >> careful Placement API is microversioned like Compute API. >> >> From python SDK you can find the relevant methods here: >> >> https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/plac… >> >> Best wishes >> Lajos Katona (lajoskatona) >> >> Saeed <s.fazl73(a)gmail.com> ezt írta (időpont: 2024. máj. 9., Cs, 19:06): >> >>> Hello, >>> >>> This is my python code: >>> >>>> import openstack >>> >>> openstack.enable_logging(debug=False) >>> >>> hypervisors = [] >>> >>> conn = openstack.connect(cloud='region1') >>> >>> for hypervisor in conn.compute.hypervisors(details=True): >>> >>> hypervisors.append(hypervisor.to_dict()) >>> >>> >>> I also run this: >>> >>>> for hypervisor in hypervisors: >>> >>> print(hypervisor) >>> >>> >>> This is the last result (other results are similar this): >>> >>>> {'cpu_info': None, 'host_ip': '1.1.1.1', 'hypervisor_type': 'QEMU', >>>> 'hypervisor_version': 6002000, 'name': 'some.fqdn.com', >>>> 'service_details': {'id': 'some-random-id', 'host': 'some.fqdn.com', >>>> 'disabled_reason': 'test'}, 'servers': None, 'state': 'up', 'status': >>>> 'disabled', 'uptime': ' 00:27:11 up 31 days, 10:14, 2 users, load >>>> average: 3.52, 3.20, 3.36\n', 'current_workload': None, 'disk_available': >>>> None, 'local_disk_used': None, 'local_disk_size': None, 'local_disk_free': >>>> None, 'memory_used': None, 'memory_size': None, 'memory_free': None, >>>> 'running_vms': None, 'vcpus_used': None, 'vcpus': None, 'id': >>>> 'some-random-id', 'location': Munch({'cloud': 'region1', 'region_name': >>>> 'Region1', 'zone': None, 'project': Munch({'id': 'somerandomid', 'name': >>>> None, 'domain_id': None, 'domain_name': None})})} >>> >>> >>> As you see, values like *cpu_info*, *disk_available*, *local_disk_used* >>> , *local_disk_size*, *local_disk_free*, *memory_used*, etc are *None*. >>> >>> How can I have the following values? In the Openstack UI I see it says >>> the free available disk, memory and CPU, but I don't know how to have them >>> in python. >>> >>> I see here >>> <https://docs.openstack.org/openstacksdk/latest/user/resources/compute/v2/hy…> >>> the above values, but for me all are None. >>> >>> Regards, >>> Saeed >>> >>

3 2

[manila][cinder][glance][nova][devstack][qa] Add ashrod98 to devstack-plugin-ceph core
by Goutham Pacha Ravi 10 May '24

10 May '24

Dear Stackers, I'd like to nominate Ashley Rodriguez to join the devstack-plugin-ceph core team. She has made significant contributions to Ceph integration and testing, especially with the Manila project. Ashley's work includes CI fixes and improvements to the cephadm installer, enabling multi-node installations and integrating ceph's new ingress service in our test jobs. She has also tackled tech debt in Manila's Ceph testing. If there are no objections, I'll add Ashley to the gerrit group next week. Ashley, your hard work is truly appreciated! Best regards, Goutham

4 4

[horizon] Next two weekly meetings cancellation
by Tatiana Ovchinnikova 10 May '24

10 May '24

Hello team, I'm on holiday for the next two weeks, so I'm cancelling weekly meetings on May 15 and 22. See you on May 29. Regards, Tatiana

1 0

[neutron] Drivers meeting canceled next Friday, May 17th
by Brian Haley 10 May '24

10 May '24

Hello Neutrinos: I'm going to preemptively cancel next Friday's drivers meeting as I will be traveling all week. I will be available intermittently on irc, so please send me an email if you need a quicker answer or if I don't respond to pings. -Brian

1 0

[kolla-ansible][Antelope][Heat] Issues with ASG and Zaqar Trigger
by Devin Patterson 10 May '24

10 May '24

Hello, We are implementing the auto-healing workflow captured here - https://github.com/openstack/heat-templates/tree/master/hot/autohealing We are deploying a Heat auto-scaling group that scales a template that contains the needed services and the Nova resource. The template contains a Zaqar queue, Mistral trigger and Mistral workflow. We are also using a scaling policy to scale up and down the template resources. This is working fine, but we are experiencing an issue with scaling up the auto-scaling group via 'openstack stack resource signal <stack> <scaling_policy>. If the Heat stack is update with a larger value, the resources are added correctly. It is only when using the scaling policy. Logs show a forbidden error when attempting to create the Zaqer Mistral trigger. Any ideas? 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.gxvscbt3q3ga]: UPDATE_COMPLETE Stack UPDATE completed successfully 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.5rjz74hujhxh.alarm_subscription]: CREATE_FAILED ServiceUnavailableError: resources.alarm_subscription: Error response from Zaqar. Code: 503. Title: Service temporarily unavailable. Description: Subscription could not be created. Please try again in a few seconds.. 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.5rjz74hujhxh]: CREATE_FAILED Resource CREATE failed: ServiceUnavailableError: resources.alarm_subscription: Error response from Zaqar. Code: 503. Title: Service temporarily unavailable. Description: Subscription could not be created. Please try again in a few seconds.. 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.5rjz74hujhxh]: CREATE_FAILED ServiceUnavailableError: resources.5rjz74hujhxh.resources.alarm_subscription: Error response from Zaqar. Code: 503. Title: Service temporarily unavailable. Description: Subscription could not be created. Please try again in a few seconds.. 2024-05-09 15:10:41Z [stack_1-DmMTV.asg]: UPDATE_FAILED Resource CREATE failed: ServiceUnavailableError: resources.5rjz74hujhxh.resources.alarm_subscription: Error response from Zaqar. Code: 503. Title: Service temporarily unavailable. Description: Subscription could not be created. Please try again in a few s 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.gxvscbt3q3ga]: UPDATE_COMPLETE state changed 2024-05-09 15:10:42Z [stack_1-DmMTV.asg.nzixbsxmb5mt]: UPDATE_COMPLETE Stack UPDATE completed successfully 2024-05-09 15:10:42Z [stack_1-DmMTV.asg.nzixbsxmb5mt]: UPDATE_COMPLETE state changed 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions [] Subscription could not be created.: keystoneauth1.exceptions.http.Forbidden: Remaining redelegation depth of 0 out of allowed range of [0..10] (Disable insecure_debug mode to suppress these details.) (HTTP 403) (Request-ID: ) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions Traceback (most recent call last): 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/zaqar/transport/wsgi/v2_0/subscriptions.py", line 193, in on_post 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions mgr.driver.register(subscriber, options, ttl, project_id, req_data) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/zaqar/notification/tasks/trust.py", line 60, in register 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions trust_id = auth.create_trust_id( 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/zaqar/common/auth.py", line 67, in create_trust_id 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions trust = client.trusts.create(trustor_user=trustor_user_id, 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneclient/v3/contrib/trusts.py", line 74, in create 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return super(TrustManager, self).create( 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneclient/base.py", line 86, in func 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return f(*args, **new_kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneclient/base.py", line 383, in create 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return self._post( 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneclient/base.py", line 192, in _post 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions resp, body = self.client.post(url, body=body, **kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneauth1/adapter.py", line 401, in post 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return self.request(url, 'POST', **kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneauth1/adapter.py", line 554, in request 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions resp = super(LegacyJsonAdapter, self).request(*args, **kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneauth1/adapter.py", line 257, in request 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return self.session.request(url, method, **kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneauth1/session.py", line 986, in request 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions raise exceptions.from_response(resp, method, url) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions keystoneauth1.exceptions.http.Forbidden: Remaining redelegation depth of 0 out of allowed range of [0..10] (Disable insecure_debug mode to suppress these details.) (HTTP 403) (Request-ID: ) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions Regards, Devin

1 0

[release] Release countdown for week R-20
by Thierry Carrez 10 May '24

10 May '24

Development Focus ----------------- The Dalmatian-1 milestone is next week, on May 16! Project team plans for the 2024.2 Dalmatian cycle should now be solidified. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library which had changes but has not been otherwise released since the 2024.1 Caracal release. PTL's or release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well, by posting a -1. If we do not hear anything at all by the end of the week, we will assume things are OK to proceed. NB: If one of your libraries is still releasing 0.x versions, start thinking about when it will be appropriate to do a 1.0 version. The version number does signal the state, real or perceived, of the library, so we strongly encourage going to a full major version once things are in a good and usable state. Upcoming Deadlines & Dates -------------------------- Dalmatian-1 milestone: May 16 -- Thierry Carrez (ttx)

1 0

[dev] Inquiry Regarding Addition of DH Groups in OpenStack VPNaaS
by Shubham Yadav 10 May '24

10 May '24

Hello , I hope this message finds you well. I am reaching out to inquire about the possibility of adding additional DH (Diffie-Hellman) groups to the VPNaaS (VPN as a Service) project in OpenStack. Currently, our setup involves using DH groups 14, 16, 20, and 21 on Fortigate routers. However, the available DH groups at the OpenStack Web UI for creating IPSEC policies are limited to groups 2, 5, and 14. Could you please provide insights into whether there are plans to introduce more DH groups into the VPNaaS project? This addition would greatly benefit our configurations and improve compatibility with our existing infrastructure. Thank you in advance for any information or guidance you can provide on this matter. Best regards,

1 0

How to check the free RAM or CPU or Disk in openstack python module
by Saeed 10 May '24

10 May '24

Hello, This is my python code: > import openstack openstack.enable_logging(debug=False) hypervisors = [] conn = openstack.connect(cloud='region1') for hypervisor in conn.compute.hypervisors(details=True): hypervisors.append(hypervisor.to_dict()) I also run this: > for hypervisor in hypervisors: print(hypervisor) This is the last result (other results are similar this): > {'cpu_info': None, 'host_ip': '1.1.1.1', 'hypervisor_type': 'QEMU', > 'hypervisor_version': 6002000, 'name': 'some.fqdn.com', > 'service_details': {'id': 'some-random-id', 'host': 'some.fqdn.com', > 'disabled_reason': 'test'}, 'servers': None, 'state': 'up', 'status': > 'disabled', 'uptime': ' 00:27:11 up 31 days, 10:14, 2 users, load > average: 3.52, 3.20, 3.36\n', 'current_workload': None, 'disk_available': > None, 'local_disk_used': None, 'local_disk_size': None, 'local_disk_free': > None, 'memory_used': None, 'memory_size': None, 'memory_free': None, > 'running_vms': None, 'vcpus_used': None, 'vcpus': None, 'id': > 'some-random-id', 'location': Munch({'cloud': 'region1', 'region_name': > 'Region1', 'zone': None, 'project': Munch({'id': 'somerandomid', 'name': > None, 'domain_id': None, 'domain_name': None})})} As you see, values like *cpu_info*, *disk_available*, *local_disk_used*, *local_disk_size*, *local_disk_free*, *memory_used*, etc are *None*. How can I have the following values? In the Openstack UI I see it says the free available disk, memory and CPU, but I don't know how to have them in python. I see here <https://docs.openstack.org/openstacksdk/latest/user/resources/compute/v2/hy…> the above values, but for me all are None. Regards, Saeed

2 1