- openstack-discuss - lists.openstack.org

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 25 May '24

25 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 24 May '24

24 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 24 May '24

24 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 23 May '24

23 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 23 May '24

23 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 22 May '24

22 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 22 May '24

22 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 22 May '24

22 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 21 May '24

21 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 20 May '24

20 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 20 May '24

20 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