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

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

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

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

16 May '24

1 0

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

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

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

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

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

14 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