- openstack-discuss - lists.openstack.org

[all] Python 3.12 issues and classes of bugs, helping me fixing them all...
by Thomas Goirand 21 Dec '23

21 Dec '23

Hi there! Since a few days, we have Python 3.12 as available interpreter version in Debian Unstable. All Debian packages were rebuilt by Lucas Neusbaumm, and about 60 Debian RC bugs were filled against the OpenStack related packages. You may have seen it in some of your projects, I was able to fix lots of bugs (so far: 28 bugs fixed since Wednesday morning, and counting...), and forwarded them to upstream OpenStack whenever possible: https://review.opendev.org/c/openstack/os-ken/+/903521 https://review.opendev.org/c/openstack/sahara-plugin-spark/+/903656 https://review.opendev.org/c/openstack/keystonemiddleware/+/903640 https://review.opendev.org/c/openstack/os-ken/+/903521 https://review.opendev.org/c/openstack/sahara-plugin-spark/+/903656 https://review.opendev.org/c/openstack/keystonemiddleware/+/903640 I'd appreciate reviews and merge for these, of course... Many reported issues were problems in a single package (like Eventlet, or taskflow not able to load asyncore), so some bugs were closed without any further action but an attempt of rebuilding the said package to check everything is as expected. However, for a lot of bugs, I do not know how to fix, which leads me to this message. Of course, mostly the hardest bugs are remaining now, as I fixes the most easy ones. Here's a few examples. In Barbican: https://bugs.debian.org/1058183 What is this "KeyError: slice(0, -1, None)" about? Many packages have the same issue (like networking-sfc, neutron-dynamic-routing, neutron-vpnaas, manila, rally and many others), so if I understand this class of bug, I'll be able to fix them all. Help would be very much appreciated on that one. In openstackclient: https://bugs.debian.org/1058097 The stackdump is: File "<frozen importlib._bootstrap>", line 1360, in _find_and_load File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 935, in _load_unlocked File "<frozen importlib._bootstrap>", line 1176, in exec_module File "<frozen codecs>", line 58, in <module> AttributeError: module 'sys' has no attribute 'byteorder' I don't really understand what's going on, but this smells like an issue in Python 3.12 itself. watcher: https://bugs.debian.org/1058377 looks like the interpreter segfauls when importing some modules in watcher.tests.api ?!? Mistral: https://bugs.debian.org/1058182 Manila: https://bugs.debian.org/1058182 AssertionError: Failed to wait for expected result: Execution f2a97f87-7b08-4171-819a-47e30a0a1840 must have reached state SUCCESS state but it is in RUNNING What's going on here? diskimage-builder: I was able to fix the "ModuleNotFoundError: No module named 'imp'" (that's trivial to fix, really...), but now I get: File "/usr/lib/python3/dist-packages/mock/mock.py", line 1245, in _importer thing = __import__(import_path) ^^^^^^^^^^^^^^^^^^^^^^^ ModuleNotFoundError: No module named 'growvols' looks like what I attempted to fix with rewriting a load_source (which is removed from Python 3.12) didn't work. python-pykmip: https://bugs.debian.org/1058411 That one feels tricky. wrap_socket is gone from the standard ssl module, though the example given in here: https://docs.python.org/3/library/ssl.html#ssl.SSLContext.wrap_socket is to use something like this: with context.wrap_socket(sock, server_hostname=hostname) as ssock: but that wont work with the way pykmip is written. So probably it needs some kind of rewrite? Looks like there's some commits upstream to address it, but no new release, unfortunately. I probably should attempt packaging the last Git commit. oslotest: https://bugs.debian.org/1058373 The broken test case attemps to disable the 'sys' module, but it looks like its failing to do so. Is there a change of behavior in the interpreter? wsgi-intercept: https://bugs.debian.org/1058378 TypeError: HTTPSConnection.__init__() got an unexpected keyword argument 'cert_file' No idea how to fix that one... :/ There's more which I probably didn't classify above. The full list of bugs is here: https://bugs.debian.org/cgi-bin/pkgreport.cgi?which=maint&data=team%2Bopens… Please ignore the first 5 though, which I don't really maintain and don't really care about (these aren't Py 3.12 issues). Many thanks to anyone that will help. Cheers, Thomas Goirand (zigo)

4 3

[Senlin][tc][all] Senlin project marked inactive by TC
by Jay Faulkner 21 Dec '23

21 Dec '23

OpenStack Community, The Technical Committee marked the Senlin project inactive[0] due to failing CI jobs and general lack of contribution. If you rely on Senlin, please take notice that without intervention, it will not be part of future OpenStack releases, including 2024.1 (Caracal). The only way for a project to leave inactive status is to become active again, and be removed from the inactive list, or to be retired from OpenStack. For more information, please see our documentation[1] on inactive projects. I encourage the OpenStack community to rally and support Senlin to bring it back into active status. If you are an operator and want more information on how to contribute and get this project going, please reply to this email and someone will be glad to help. Thank you, Jay Faulkner OpenStack TC Chair 0: https://review.opendev.org/c/openstack/governance/+/902626 1: https://governance.openstack.org/tc/reference/emerging-technology-and-inact…

1 0

[ec2-api][tc][all] ec2-api project marked inactive by TC
by Jay Faulkner 21 Dec '23

21 Dec '23

OpenStack Community, The Technical Committee marked the ec2-api project inactive[0] due to failing CI jobs and general lack of contribution. If you rely on ec2-api, please take notice that without intervention, it will not be part of future OpenStack releases, including 2024.1 (Caracal). The only way for a project to leave inactive status is to become active again, and be removed from the inactive list, or to be retired from OpenStack. For more information, please see our documentation[1] on inactive projects. I encourage the OpenStack community to rally and support ec2-api to bring it back into active status. If you are an operator and want more information on how to contribute and get this project going, please reply to this email and someone will be glad to help. Thank you, Jay Faulkner OpenStack TC Chair 0: https://review.opendev.org/c/openstack/governance/+/902625 1: https://governance.openstack.org/tc/reference/emerging-technology-and-inact…

1 0

beginning with [masakari]
by Shubham Kumar Yadav 21 Dec '23

21 Dec '23

Hi, i have recently started working on Masakari (kubernetes in openstack) so i wanted some help with it please i was trying to test the masakari-instance_monitor & masakari-host-monitor but having trouble with it. i have created a pacemaker remote cluster (with pacemaker & corosync on controller nodes and pacemaker remote on compute node. *pcs statusCluster name: lab-clusterCluster Summary: * Stack: corosync * Current DC: lab-11053-26006-ceph-2 (version 2.1.2-ada5c3b36e2) - partition with quorum * Last updated: Thu Dec 14 08:41:41 2023 * Last change: Thu Dec 14 08:41:22 2023 by root via cibadmin on lab-11053-26006-ceph-1 * 6 nodes configured * 3 resource instances configuredNode List: * Online: [ lab-11053-26006-ceph-1 lab-11053-26006-ceph-2 lab-11053-26006-ceph-3 ] * RemoteOnline: [ lab-11053-26006-comp-1.cluster.local lab-11053-26006-comp-2.cluster.local lab-11053-26006-comp-3.cluster.local ]Full List of Resources: * lab-11053-26006-comp-1.cluster.local (ocf:pacemaker:remote): Started lab-11053-26006-ceph-1 * lab-11053-26006-comp-2.cluster.local (ocf:pacemaker:remote): Started lab-11053-26006-ceph-2 * lab-11053-26006-comp-3.cluster.local (ocf:pacemaker:remote): Started lab-11053-26006-ceph-3Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled* i have also created segment and added hosts(computes) in it. when i tried to test the masakari host monitor by manually powering off the compute node, masakari should move the vms from powered off computes to some running compute but after the compute is powered off vms still remains on the powered off compute. Am i missing some conf? is there any need to add some conf in nova and keystone too? in masakari engine logs i see host_failure.evacuate_all_instances = True instance_failure.process_all_instances = False host_failure.add_reserved_host_to_aggregate = False host_failure.ha_enabled_instance_metadata_key = HA_Enabled log_opt_values host_failure.ignore_instances_in_error_state = False host_failure.service_disable_reason = Masakari detected host failed. do you have any suggestion please let me know! Thank You

2 1

[oslo] Nominating tobias-urdin for etcd3gw core
by Takashi Kajinami 21 Dec '23

21 Dec '23

Hi team, I raised this topic in #openstack-oslo today and already got a few acks, but I'm sending this email here for an official proposal as well as record. The etcd3gw library is now extensively used by tooz as the primary implementation for etcd3 backend. Because Tobias is already a core reviewer in the tooz library, I propose adding him to the etcd3gw core as well. Please let me know in case anyone has any thoughts on the proposal. I'll add him to the group next week if we hear no objections. Thank you Takashi Kajinami

2 2

[cinder] Canceling next week's meeting (27th December)
by Rajat Dhasmana 21 Dec '23

21 Dec '23

Hello Argonauts, Since most of the team members will be on year end break, we have decided to cancel next week's cinder meeting that was going to be held on 27th December, 2023. A merry christmas and a happy new year to the team. See you all next year! Thanks Rajat Dhasmana

1 0

Reg the issue
by Rohit Sansiya 20 Dec '23

20 Dec '23

Sir, I want help regarding openstack project creation. While creating the project by using openstack project create then stuck the process and got the error regarding fail to discover available identity versions when contacting the url(http://controller11:5000/v3) & gateway timeout 504 kindly help. Your message is ready to be sent with the following file or link attachments: Rohit Sansiya https://sites.google.com/view/rpgcloud/research-india Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled.

1 0

Re: about magnum capi for production
by Oliver Weinmann 20 Dec '23

20 Dec '23

4 7

[tc] OpenInfra Foundation Bylaws & TC Charter Changes
by Jay Faulkner 20 Dec '23

20 Dec '23

Hi all, I wanted to inform you we have two TC resolutions up for vote related to recent OpenInfra Foundation bylaws changes. First, https://review.opendev.org/c/openstack/governance/+/903239 is a resolution by the Technical Committee approving the OpenInfra Foundation bylaws changes. Secondly, https://review.opendev.org/c/openstack/governance/+/903236 is an update to the Technical Committee charter required as part of the bylaws changes. This is part of a joint effort between the OpenInfra Foundation and the OpenStack Technical Committee to remove language from the foundation bylaws treating OpenStack differently from other OpenInfra projects. Please take notice! Thanks, Jay Faulkner OpenStack TC Chair

1 0

[neutron] DevStack support for OVN BGP Agent
by Luis Tomas Bolivar 20 Dec '23

20 Dec '23

Hey folks, This is just a heads up we worked on a DevStack plugin for the OVN BGP agent [1], so that it is easier to deploy and test locally, with limited functionality. I also posted about how to use it [2] [1] https://review.opendev.org/c/openstack/ovn-bgp-agent/+/814185 [2] https://ltomasbo.wordpress.com/2023/12/19/deploying-ovn-bgp-agent-with-devs… Best regards, Luis -- LUIS TOMÁS BOLÍVAR Principal Software Engineer Red Hat Madrid, Spain ltomasbo(a)redhat.com

2 1

octavia lb operating status is always offline
by zhengrui20220 20 Dec '23

20 Dec '23

[octavia] hello，i am zhengrui，I have a problem with octavia deployment, my lb can work normally, but 'openstack loadbalancer list' command shows lb's operating status is offline, and my health manager log show 'Exception: 'NoneType' object has no attribute 'encode', then I add 'heartbeat_key = 20e8350e-950f-40fb-bb36-b9259e355523' in octavia.conf ,it shows 2023-12-19 10:38:59.701 1013848 WARNING octavia.amphorae.backends.health_daemon.status_message [-] calculated hmac(hex=True): 37623763633366666565616639383462373865343661616235616431623533363866306638336638653937656262333538303732346339656364623932623339 not equal to msg hmac: 61303433633739663136306366633465363234653535396663373230616636306134623036333339353363353736616339656133616538653961643762383763 dropping packet Now, I have no idea about this problem. | | zhengrui20220 | | zhengrui20220(a)163.com |

3 2

[publiccloud-sig] Skipping meeting next week - next meeting will be January 10th
by Felix Kronlage-Dammers 20 Dec '23

20 Dec '23

Hi everyone, like most (all? ;) of the other teams: Due to the holidays the publiccloud-sig will not meet next week - instead the next meeting will be on January 10th - then as always at 0800 UTC. Enjoy the holidays! felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack 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

[barbican] Meetings scheduling
by Grzegorz Grasza 19 Dec '23

19 Dec '23

Hi all, As proposed in our last meeting [1], the new meeting time will move to Mondays @ 15:00 UTC. The next meeting is scheduled for Jan 8th 2024. [2] Enjoy the holiday season and I'll see y'all next year! / Greg [1] https://meetings.opendev.org/meetings/barbican/2023/barbican.2023-12-19-12.… [2] https://review.opendev.org/c/opendev/irc-meetings/+/903976

1 0

[kolla] Cancelling weekly meetings until 10th January 2024
by Michał Nasiadka 19 Dec '23

19 Dec '23

Hello Koalas, Since we’re approaching festive season and most of the meeting participants are going to be off - I’m cancelling couple of next weekly meetings. Let’s meet again on 10th of January 2024. Michal

1 0

[zaqar][tc] master and 2023.2 unit tests are broken
by Takashi Kajinami 19 Dec '23

19 Dec '23

Hello, Today I happened to notice that unit tests in zaqar is broken because some tests requires base test class from oslo.db which was removed in 13.0.0 release[1]. The 13.0.0 release of oslo.db was made during 2023.2 cucle so these tests are also broken in stable/2023.2 branch. In addition, py311 job was made voting in master but is broken and we probably need to fix bindep.txt so that it works in Debian 12. I'm sending this mail so that people maintaining the project is aware of the situation. I'll add [tc] tag because if the CI is not fixed then zaqar may become a new candidate for inactive projects. Thank you, Takashi [1] https://review.opendev.org/c/openstack/oslo.db/+/874239

2 1

[tc] Weekly Meeting tomorrow, Dec 19 at 1800 UTC
by Jay Faulkner 19 Dec '23

19 Dec '23

Hi all, The weekly meeting of the OpenStack Technical Committee is scheduled for tomorrow, December 19, at 1800 UTC in #openstack-tc on OFTC. As a reminder, this will be our last meeting of 2023. Our next scheduled meeting after this will be January 7, 2024. The proposed agenda is: - Roll call - Follow up on tracked action items: https://meetings.opendev.org/meetings/tc/2023/tc.2023-12-12-18.00.html - Spotz - (due Jan 7 2024) Look into updating https://docs.openstack.org/install-guide/openstack-services.html and report back to TC Create TC resolution expressing approval for OIF bylaws change - Gate health check - Leaderless projects (gmann) - Implementation of Unmaintained branch statuses - 2024.1 TC Tracker - https://etherpad.opendev.org/p/tc-2024.1-tracker - Open Discussion and Reviews Thanks, Jay Faulkner OpenStack TC Chair

1 0

[Kolla-ansible] Upgrading from Yoga to Zed HCI deployment
by wodel youchi 18 Dec '23

18 Dec '23

Hi, I need to upgrade my Openstack deployment from Yoga (Rocky Linux 8) to Zed (Rocky Linux 9). My deployment is an HCI deployment with ceph pacific deployed using ceph-ansible. it contains : - 03 controllers that contain also ceph mgr/mon/rgw/cephfs containers - 27 compute/storage nodes I am planning to follow these steps : 1. Upgrade to Rocky 9, starting with the controllers, then the compute/storage nodes. 1. Undeploy 1 controller at a time, upgrade to Rocky 9, re-deploy the controller. 2. Undeploy 3 compute/storage nodes at a time, upgrade to Rocky 9, redeploy the nodes. 2. Stop the Openstack platform 3. Convert the deployed ceph pacific from ceph-ansible to cephadm. 4. Upgrade from Yoga to ZED If you can help me with some insights/thoughts things to do / to avoid, so that the upgrade will move smoothly, that would be great. Regards.

5 5

[neutron] Bug Deputy Report December 11 - December 17
by Yatin Karel 18 Dec '23

18 Dec '23

Hi Neutrinos, Below is the bug deputy report for last week:- High ------ - https://bugs.launchpad.net/neutron/+bug/2046457 ovn provider fails with "AttributeError: 'Client' object has no attribute 'ports'" Antelope impacted with a recent patch Unassigned Low ---------- - https://bugs.launchpad.net/neutron/+bug/2046392 Service Type Framework cannot handle router flavor provider entry point shortcut with stevedore Assigned to Miguel Lavalle Undecided -------------- - https://bugs.launchpad.net/neutron/+bug/2046510 neutron-servers have high memory usage Report against stable/rocky, requested more information. -- Thanks and Regards Yatin Karel

1 0

[neutron] Cannot reach external network from within VM
by Michael J Turek 18 Dec '23

18 Dec '23

Hey all, We’ve been trying to get our Bobcat openstack cloud working and have been stuck on some networking woes. It’s a flat provider network with one compute node and one controller (plan to expand after this is resolved). 1) We can SSH and ping the VMs but only if we are on the controller and behind the qdhcp network namespace. 2) Once on the VM, we cannot reach the external network. We followed this installation guide [0] and nothing stands out as misconfigured. If anyone can offer some advice on how to debug this, it would be greatly appreciated. [0] https://docs.openstack.org/neutron/latest/install/controller-install-option…

4 6

Re: openstack-discuss Digest, Vol 62, Issue 59
by Kerem Çeliker 17 Dec '23

17 Dec '23

1 0

[release] Release countdown for week R-15, Dec 18-22
by Elõd Illés 16 Dec '23

16 Dec '23

Development Focus ----------------- The Caracal-2 milestone will happen in next month, on January 11th, 2024. 2024.1 Caracal-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/caracal/schedule.html for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/carac… You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/caracal/schedule.html#c-mf Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- Caracal-2 Milestone: January 11th, 2024 Előd Illés irc: elodilles @ #openstack-release

1 0

[cinder] Festival of XS reviews (15 Dec)
by Rajat Dhasmana 15 Dec '23

15 Dec '23

Hello Argonauts, We will be having our monthly festival of reviews this Friday i.e. 15th December (Friday) from 1400-1600 UTC. Following are the details: Date: 15th December, 2023 Time: 1400-1600 UTC Meeting link: https://meet.google.com/jqg-eigw-rku etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews Thanks Rajat Dhasmana

1 1

[neutron] Meetings next few weeks
by Brian Haley 15 Dec '23

15 Dec '23

Hello Neutrinos: With company Holiday shutdowns over the next couple of weeks, just wanted to make sure everyone was aware of our meetings during that time, and of my availability. 12/19: Neutron meeting, chaired by Rodolfo 12/22: Neutron Drivers meeting, if necessary, chaired by Rodolfo 12/26: Neutron meeting cancelled 12/29: Neutron Drivers meeting cancelled 1/2: Neutron meeting, chaired by Rodolfo 1/5: Neutron Drivers meeting, if necessary, chaired by Rodolfo Thanks Rodolfo for doing this while I'm out! I am out the next three weeks, but will occasionally check-in to make sure nothing is on fire :) The first week of 2024 I will not be available at all, please ping other core reviewers in the #openstack-neutron channel with any questions. Thanks, and have a nice holiday break! -Brian, Neutron PTL

1 0

[neutron] Drivers meeting cancelled tomorrow
by Brian Haley 15 Dec '23

15 Dec '23

Hello Neutrinos: Due to the lack of agenda, Friday's drivers meeting is cancelled. Have a nice weekend! -Brian

1 0

[solum][tc][all] Solum project marked inactive by TC
by Jay Faulkner 15 Dec '23

15 Dec '23

OpenStack Community, The Technical Committee marked the solum project inactive[0] due to failing CI jobs and general lack of contribution. If you rely on solum, please take notice that without intervention, it will not be part of future OpenStack releases, including 2024.1 (Caracal). The only way for a project to leave inactive status is to become active again, and be removed from the inactive list, or to be retired from OpenStack. For more information, please see our documentation[1] on inactive projects. I encourage the OpenStack community to rally and support solum to bring it back into active status. If you are an operator and want more information on how to contribute and get this project going, please reply to this email and someone will be glad to help. Thank you, Jay Faulkner OpenStack TC Chair 0: https://review.opendev.org/c/openstack/governance/+/902624 1: https://governance.openstack.org/tc/reference/emerging-technology-and-inact…

1 0