- openstack-discuss - lists.openstack.org

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