May 2023 - openstack-discuss - lists.openstack.org

[kolla-ansible][yoga] Installation failure while `creating shard root mysql user`
by Rob Jefferson 25 May '23

25 May '23

I'm trying to set up Yoga (as part of a way of upgrading from Xena to Yoga to Zed) using kolla-ansible, and I'm finding that I'm getting the following error at the `kolla-ansible/ansible/roles/mariadb/tasks/register.yml` playbook: TASK [mariadb : Creating shard root mysql user] [...] fatal: [control01]: FAILED! => { "changed": false, "msg": "Can not parse the inner module output: b'[WARNING]: Failure using method (v2_playbook_on_play_start) in callback plugin (<ansible_collections.ansible.posix.plugins.callback.json.CallbackModule object at 0x7fa4e6e18d00>): 'Play' object has no attribute 'get_path' [WARNING]: Failure using method (v2_playbook_on_task_start) in callback plugin (<ansible_collections.ansible.posix.plugins.callback.json.CallbackModule object at 0x7fa4e6e18d00>): list index out of range [WARNING]: Failure using method (v2_runner_on_ok) in callback plugin (<ansible_collections.ansible.posix.plugins.callback.json.CallbackModule object at 0x7fa4e6e18d00>): list index out of range { "custom_stats": {}, "global_custom_stats": {}, "plays": [], "stats\": { "localhost": { "changed\": 0, "failures\": 0, "ignored\": 0, "ok": 1, "rescued\": 0, "skipped\": 0, "unreachable\": 0 } } }' "} I am not sure how to fix this error, or determine what's causing it. I've tried matching up Ansible versions between my installation environment and Yoga, I've tried upgrading Kolla, and so forth. For the installation environment, I'm using: * Debian 11 * Ansible 4.10.0 * ansible-core 2.11.2 * docker-ce 5.20.10 Any help with this would be most appreciated. Thanks, Rob

4 6

Cinder Bug Report 2023-05-25
by Sofia Enriquez 25 May '23

25 May '23

Hello Argonauts, Sorry for the late email. Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Low* - Cached images duplicated per host. <https://bugs.launchpad.net/cinder/+bug/2020733> - *Status:* Unassigned. - [rbac] User with Reader role can extend/reserve/retype/unreserve/update_readonly volume. <https://bugs.launchpad.net/cinder/+bug/2020261> - *Status:* Tempest proposed to master. <https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/883182> - [rbac] User with Reader role can create/delete/update/set-bootable volume. <https://bugs.launchpad.net/cinder/+bug/2020113> - *Status:* Tempest proposed to master. <https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/878672> Cheers -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[ironic] Deploy images crashing Dell server BIOS using UEFI boot
by Mike Currin 25 May '23

25 May '23

Hi All, We have a Xena based Openstack deployment, recently we deployed 60+ nodes in our research cluster with Ironic which worked well. All of these were deployed using a standard process I'll describe below. We recently took delivery of a new Dell R6625 server with NVMe devices onlym which only support UEFI boot, so we are trying to get that working. The server PXEs and downloads the RAM disk and then the Deploy image, once running that it immediately crashes (I assume when running linuxefi). We tested UEFI deploy on an existing Dell R640 server, that server works with BIOS but we swapped it over to UEFI and it does the same, so it wasn't due to the much bigger/different architecture (AMD vs Intel) server. We have a few older servers in a test setup (which are Dell R630's) which are working fine and don't do this behaviour. We haven't tried them on our production setup as if even if they worked it wouldn't help us move forward. I made a video showing this: https://www.dropbox.com/s/5jbn1qpylxaevqb/uefiboot2.mov?dl=0 In the iDRAC we just get that the "System BIOS has halted" and somewhere I said to change hardware that you recently added, which feels unlikely as 2 different servers both working elsewhere with totally different hardware,. I've done a iDRAC Serial console debug but it isn't showing me much that is of any use. This is our entire process to deploy a node (some is once off of course, I've not included the network setup): openstack flavor create --ram 256000 --disk 20 --vcpus 32 --public our-baremetal openstack flavor set our-baremetal --property capabilities:boot_mode="uefi" We downloaded the latest (Xena) images from: https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/ I also tried the latest Centos9 ones just to try them, made no difference. We then extract the image and make a small mod to the service start (we found it didn't bring the NIC immediately up so put a ping delay in the ExecStart), but that's not part of this problem. openstack image create --disk-format aki --container-format aki --public --file ironic-agent.kernel deploy-vmlinuz openstack image create --disk-format ari --container-format ari --public --file ironic-agent.initramfs-ping-patched deploy-initrd Then to do the deploy: export HOSTNAME=<hostname> export MGMTIP=<idracip> openstack baremetal node create --driver ipmi --name $HOSTNAME --driver-info ipmi_port=623 --driver-info ipmi_username=root --driver-info 'ipmi_password=<ourpassword>' --driver-info ipmi_address=$MGMTIP --resource-class baremetal-resource-class --property cpus=32 --property memory_mb=256000 --property local_gb=20 --property cpu_arch=x86_64 --driver-info deploy_ramdisk=$(openstack image show deploy-initrd -f value -c id) --driver-info deploy_kernel=$(openstack image show deploy-vmlinuz -f value -c id) NODE=$(openstack baremetal node show -f value -c uuid $HOSTNAME) openstack baremetal node set $NODE --property capabilities='boot_mode:uefi' openstack baremetal port create <MACADDRESS> --node $NODE --physical-network physnet3 openstack baremetal node manage $NODE --wait && openstack baremetal node list && openstack baremetal node provide $NODE && openstack baremetal node list openstack server create --use-config-drive --image <ourimage> --flavor our-baremetal --security-group worker --network ironic-network --key-name <ourkeyname> servername Does any one have any more info to help or any suggestions as to something more I could try, I'm out of ideas. I know that UEFI itself works on both the servers, we have a setup with Ubuntu MAAS and it can deploy perfectly fine using its process with the UEFI setup so, it's something on the Ironic deploy image that's causing us this problem. Regards, Mike

2 1

upgrade issue with nova/cinder and api version error
by Jim Kilborn 25 May '23

25 May '23

Hello, First time posting here. We have been running a production openstack environment at my office since the kilo release. We are currently on train, and I'm trying to get up to a more recent version. To make it more difficult, we are on centos7, so having to switch to ubuntu as we update versions. The problem that I am having after updaing to victoria, is that when I delete a vm via horizon, the instance disappears but the cinder volume doesn't delete the attachment. It appears this is due to the following error in /var/log/apache2/cinder_error.log ERROR cinder.api.middleware.fault novaclient.exceptions.NotAcceptable: Version 2.89 is not supported by the API. Minimum is 2.1 and maximum is 2.87. (HTTP 406) When I look at the /usr/lib/python3/dist-packages/cinder/compute/nova.py I can see it's using 2.89 in get_server_volume def get_server_volume(context, server_id, volume_id): # Use microversion that includes attachment_id nova = novaclient(context, api_version='2.89') return nova.volumes.get_server_volume(server_id, volume_id) I am not sure why cinder and nova are in disagreement on the api_version. I have verified that they are both upgraded to the victoria release. Anyone have any ideas as to why I would be getting this error or a possible fix? I haven't been able to find any information on this error. Here are the nova package versions: nova-api/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] nova-common/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] nova-conductor/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] nova-novncproxy/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] nova-scheduler/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] python3-nova/focal-updates,now 2:22.4.0-0ubuntu1~cloud3 all [installed] python3-novaclient/focal-updates,now 2:17.2.1-0ubuntu1~cloud0 all [installed,automatic] Here are the cinder package versions: cinder-api/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed] cinder-common/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed,automatic] cinder-scheduler/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed] cinder-volume/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed] python3-cinder/focal-updates,now 2:17.4.0-0ubuntu1~cloud3 all [installed,automatic] python3-cinderclient/focal-updates,now 1:7.2.0-0ubuntu1~cloud0 all [installed] Thanks in advance for any ideas!

3 4

[neutron] Resignation announcement of Nate, Hongbin and Takashi
by Rodolfo Alonso Hernandez 25 May '23

25 May '23

Hello all: Today I would like to announce that Nate Johnston, Takashi Yamamoto and Hongbin Lu are stepping down as Neutron core reviewers and Neutron drivers. Before sending this email, I contacted them and Nate and Takashi agreed on this decision; I tried twice to contact Hongbin with no response. In order to have a participative Neutron community, the Neutron core and Neutron drivers teams should be made up of active members in code reviews, meeting attendance and spec reviewal. Nate, Takashi and Hongbin have been very active and valuable members of the Neutron (and OpenStack) community in the past; for that I would like to thank you for your contributions. Tomorrow I'll update the Launchpad and gerrit groups. Regards.

2 1

Message d'erreur
by BEDDA Fadhel 24 May '23

24 May '23

Good morning who can help me to work around this problem: root@controller certs(keystone)# openstack project create --domain default --description "Service Project" service Failed to discover available identity versions when contacting https://controller.cloud.net:5000/v3. Attempting to parse version from URL. SSL exception connecting to https://controller.cloud.net:5000/v3/auth/tokens: HTTPSConnectionPool(host='controller.cloud.net', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:997)')))

2 1

[kolla] How to patch images during build
by Satish Patel 24 May '23

24 May '23

Folks, I'm using kolla-build to build all images and push them to the local repo. So far all good but let's say If in future for some reason I want to patch some bug and rebuild the image in that case how do i patch kolla images? I am reading at [1] and didn't see any example to patch Image for any bug. Should I be downloading tarball and patch it and then use type=local to build the image from local source or add patch to Dockerfile? What people use for best practice for this kind of thing? [1] https://docs.openstack.org/kolla/latest/admin/image-building.html

5 16

[kolla] [train] [keystone] Number of User/Group entities returned by LDAP exceeded size limit
by Albert Braden 24 May '23

24 May '23

We have 200 groups in our LDAP server. We recently started getting an error when we try to list groups: $ os group list --domain AUTH.OURDOMAIN.COM Number of User/Group entities returned by LDAP exceeded size limit. Contact your LDAP administrator. (HTTP 500) I read the "Additional LDAP integration settings" section in [1] and then tried setting various values of page_size (10, 100, 1000) in the [ldap] section of keystone.conf but that didn't make a difference. What am I missing? [1] https://docs.openstack.org/keystone/train/admin/configuration.html#identity… Here's the stack trace: 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application [req-198741c6-58b2-46b1-8622-bae1fc5c5280 d64c83e1ea954c368e9fe08a5d8450a1 47dc15c280c9436fadac4d41f1d54a64 - default default] Number of User/Group entities returned by LDAP exceeded size limit. Contact your LDAP administrator.: keystone.exception.LDAPSizeLimitExceeded: Number of User/Group entities returned by LDAP exceeded size limit. Contact your LDAP administrator. 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application Traceback (most recent call last): 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/backends/ldap/common.py", line 996, in search_s 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application attrlist, attrsonly) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/backends/ldap/common.py", line 689, in wrapper 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return func(self, conn, *args, **kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/backends/ldap/common.py", line 824, in search_s 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application attrsonly) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 870, in search_s 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return self.search_ext_s(base,scope,filterstr,attrlist,attrsonly,None,None,timeout=self.timeout) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 1286, in search_ext_s 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return self._apply_method_s(SimpleLDAPObject.search_ext_s,*args,**kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 1224, in _apply_method_s 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return func(self,*args,**kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 864, in search_ext_s 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return self.result(msgid,all=1,timeout=timeout)[1] 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 756, in result 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application resp_type, resp_data, resp_msgid = self.result2(msgid,all,timeout) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 760, in result2 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application resp_type, resp_data, resp_msgid, resp_ctrls = self.result3(msgid,all,timeout) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 767, in result3 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application resp_ctrl_classes=resp_ctrl_classes 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 774, in result4 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application ldap_result = self._ldap_call(self._l.result4,msgid,all,timeout,add_ctrls,add_intermediates,add_extop) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 340, in _ldap_call 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application reraise(exc_type, exc_value, exc_traceback) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/compat.py", line 46, in reraise 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application raise exc_value 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib64/python3.6/site-packages/ldap/ldapobject.py", line 324, in _ldap_call 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application result = func(*args,**kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application ldap.SIZELIMIT_EXCEEDED: {'msgtype': 100, 'msgid': 2, 'result': 4, 'desc': 'Size limit exceeded', 'ctrls': []} 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application During handling of the above exception, another exception occurred: 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application Traceback (most recent call last): 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/flask/app.py", line 1813, in full_dispatch_request 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application rv = self.dispatch_request() 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/flask/app.py", line 1799, in dispatch_request 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return self.view_functions[rule.endpoint](**req.view_args) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/flask_restful/__init__.py", line 480, in wrapper 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application resp = resource(*args, **kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/flask/views.py", line 88, in view 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return self.dispatch_request(*args, **kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/flask_restful/__init__.py", line 595, in dispatch_request 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application resp = meth(*args, **kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/api/groups.py", line 59, in get 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return self._list_groups() 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/api/groups.py", line 86, in _list_groups 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application hints=hints) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/common/manager.py", line 116, in wrapped 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application __ret_val = __f(*args, **kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/core.py", line 414, in wrapper 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return f(self, *args, **kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/core.py", line 424, in wrapper 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return f(self, *args, **kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/core.py", line 1329, in list_groups 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application ref_list = driver.list_groups(hints) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/backends/ldap/core.py", line 116, in list_groups 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return self.group.get_all_filtered(hints) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/backends/ldap/core.py", line 474, in get_all_filtered 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application for group in self.get_all(query, hints)] 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/backends/ldap/common.py", line 1647, in get_all 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application for x in self._ldap_get_all(hints, ldap_filter)] 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/common/driver_hints.py", line 42, in wrapper 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application return f(self, hints, *args, **kwargs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/backends/ldap/common.py", line 1600, in _ldap_get_all 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application attrs) 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application File "/usr/lib/python3.6/site-packages/keystone/identity/backends/ldap/common.py", line 998, in search_s 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application raise exception.LDAPSizeLimitExceeded() 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application keystone.exception.LDAPSizeLimitExceeded: Number of User/Group entities returned by LDAP exceeded size limit. Contact your LDAP administrator. 2023-05-15 20:18:41.932 36 ERROR keystone.server.flask.application

2 4

[cinder-backup][ceph] cinder-backup support of incremental backup with ceph backend
by Satish Patel 24 May '23

24 May '23

Folks, I have ceph storage for my openstack and configure cinder-volume and cinder-backup service for my disaster solution. I am trying to use the cinder-backup incremental option to save storage space but somehow It doesn't work the way it should work. Whenever I take incremental backup it shows a similar size of original volume. Technically It should be smaller. Question is does ceph support incremental backup with cinder? I am running a Yoga release. $ openstack volume list +--------------------------------------+------------+------------+------+-------------------------------------+ | ID | Name | Status | Size | Attached to | +--------------------------------------+------------+------------+------+-------------------------------------+ | 285a49a6-0e03-49e5-abf1-1c1efbfeb5f2 | spatel-vol | backing-up | 10 | Attached to spatel-foo on /dev/sdc | +--------------------------------------+------------+------------+------+-------------------------------------+ ### Create full backup $ openstack volume backup create --name spatel-vol-backup spatel-vol --force +-------+--------------------------------------+ | Field | Value | +-------+--------------------------------------+ | id | 4351d9d3-85fa-4cd5-b21d-619b3385aefc | | name | spatel-vol-backup | +-------+--------------------------------------+ ### Create incremental $ openstack volume backup create --name spatel-vol-backup-1 --incremental --force spatel-vol +-------+--------------------------------------+ | Field | Value | +-------+--------------------------------------+ | id | 294b58af-771b-4a9f-bb7b-c37a4f84d678 | | name | spatel-vol-backup-1 | +-------+--------------------------------------+ $ openstack volume backup list +--------------------------------------+---------------------+-------------+-----------+------+ | ID | Name | Description | Status | Size | +--------------------------------------+---------------------+-------------+-----------+------+ | 294b58af-771b-4a9f-bb7b-c37a4f84d678 | spatel-vol-backup-1 | None | available | 10 | | 4351d9d3-85fa-4cd5-b21d-619b3385aefc | spatel-vol-backup | None | available | 10 | +--------------------------------------+---------------------+-------------+-----------+------+ My incremental backup still shows 10G size which should be lower compared to the first backup.

6 14

[neutron] Deprecate networking-odl project
by Rodolfo Alonso Hernandez 24 May '23

24 May '23

Hello all: During the last releases, the support for "networking-odl" project has decreased. Currently there is no active developer or maintainer in the community. This project depends on https://www.opendaylight.org/; the latest version released is Sulfur (16) while the version still used in the CI is Sodium (11) [1]. I would like first to make a call for developers to update this project. But if this is not possible, I will then start the procedure to deprecate it [2] (**not to retire it**). Regards. [1] https://github.com/openstack/networking-odl/blob/db5c79b3ee5054feb8a17df130… [2] https://docs.openstack.org/project-team-guide/repository.html#deprecating-a…

3 3