March 2024 - openstack-discuss - lists.openstack.org

[keystone] weekly meeting canceled for 06-March-2024
by Dave Wilde 06 Mar '24

06 Mar '24

Hello, Apologies for the late notice but I need to cancel the weekly meeting today due to a conflict in my schedule. Please reach out to me on list or on IRC if you need anything. Thanks! /Dave

1 0

Barbican/Heat Xena: strange error with barbican-manage (and heat-manage)
by Michel Jouvin 06 Mar '24

06 Mar '24

Hi, I'm trying to update our Wallaby cloud to Xena. Doing this for Barbican and Heat, I have a problem when trying to upgrade the database. Here is the log for Barbican: ---------- [root@os-77023 ~]# barbican-manage db upgrade head [root@os-77023 ~]# barbican-manage db current ERROR: 'int' object is not iterable [root@os-77023 ~]# barbican-manage db upgrade ERROR: 'int' object is not iterable ---------- I can find a similar error in log files of Heat services, for example in heat-engine.log: --------- 2024-03-05 12:16:27.978 1638283 INFO heat.engine.worker [-] Starting engine_worker (1.4) in engine 686dc841-d595-49cd-bf5e-04a4de876dc1. 2024-03-05 12:16:28.109 1638283 ERROR oslo_service.service [req-b991252a-f4c1-4955-a2ed-b20db59a161c - - - - -] Error starting thread.: TypeError: 'int' object is not iterable --------- My DB connection information, working well with Wallaby, is: ---------- sql_connection=mysql+pymysql://barbican:very_secret_pwd@os-sql-admin.lal.in2p3.fr/barbican ---------- I cannot find any other useful information. Anything trivial I missed? Thanks in advance for any help. Best regards, Michel

1 2

[Watcher] How use Watcher to scheduler Openstack resource without cpu_usage
by Nguyễn Hữu Khôi 06 Mar '24

06 Mar '24

Hello guys. I want to use watcher to scheduler openstack resources but some openstack versions are missing cpu_usage metric. How do we use Watcher without it? Thank you. Nguyen Huu Khoi

3 5

[largescale-sig] Next meeting: March 6, 9utc
by Thierry Carrez 06 Mar '24

06 Mar '24

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC, our EU+APAC time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240306T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[tc] [ptg] Tentative schedule
by Jay Faulkner 05 Mar '24

05 Mar '24

I've posted a tentative schedule for the TC vPTG here: https://etherpad.opendev.org/p/apr2024-ptg-os-tc and booked the appropriate times in the PTGBot. I need people to take the following actions: - Existing TC members please review the times for accuracy and confirm their ability to attend. - TC candidates, please review the times for major conflicts and inform me if any of the selected times are hardships. We will finalize the times once the new TC is seated, but I wanted to ensure we had something scheduled. Also, please take time to indicate topics for the TC session here: https://etherpad.opendev.org/p/apr2024-ptg-os-tc. Thanks, Jay Faulkner OpenStack TC Chair

1 0

[tc][murano] Removing Murano from 2024.1 release
by Jay Faulkner 05 Mar '24

05 Mar '24

Hi all, After discussion in the TC meeting today about lots of gathered evidence that Murano is inactive and plagued by serious bugs, I have proposed a resolution to remove Murano from the release. This is roughly equivalent to marking it inactive; however we can only use inactive status to remove things from the release before milestone-2. At this point, the TC is too late discovering the bad state of Murano to use inactivity to prevent its release. Therefore, I have proposed a special-case resolution[0] reflecting general consensus in the TC meeting that Murano should not be released. I wanted to inform the community of this resolution, and advise anyone who may be considering deployment of Murano to be aware of its current inactive state. Additionally, if you believe our evaluation of the situation is wrong, feel free to let your voice be heard in Gerrit. Thanks, Jay Faulkner OpenStack TC Chair 0: https://review.opendev.org/c/openstack/governance/+/910434

1 1

[magnum][stein][kolla-ansible] Cluster creation timeout
by İzzettin Erdem 05 Mar '24

05 Mar '24

Hi everyone, I am currently working on Magnum installed on kolla-ansible stein version. I followed the docs and created clusters using Fedora-Atomic-27-20180419.0.x86_64.qcow2 image according to docs. Now, magnum is creating necessary resources, VMs etc but after some time it is getting timeout at kube_minions&kube_cluster_deploy steps and there are not any information logs about it. I've tried to use different images but I could not succeed. Can you help me, please? Thanks a lot, İzzettin.

3 6

[diskimage-builder] bootable ISO image for baremetal
by Ettore Simone 05 Mar '24

05 Mar '24

Hi! I know it is not one of the most wonderful options for DIB, but in some circumstances I used ISO image in a USB stick for some old and unmaintained hardware. I used to fix by hand every time the "iso" element to complete the task, due to an old reference to a deprecated variable (DIB_IMAGE_ROOT_FS_UUID, now DIB_BOOT_LABEL). I proposed a very small fix and I hope it could be merged in the future: https://review.opendev.org/c/openstack/diskimage-builder/+/905556 Thank you for all your great work. Cheers, Ettore

4 6

[magnum][nova] AZ or Host aggregates not working as expected
by Satish Patel 04 Mar '24

04 Mar '24

2 13

[tc] Next Meeting Tomorrow, March 53332, 1800 UTC
by Jay Faulkner 04 Mar '24

04 Mar '24

Hi all, the next weekly meeting of the OpenStack Technical Committee is tomorrow, March 5, at 1800 UTC. It will be held in a Zoom video conference with minutes kept in #openstack-tc on OFTC. The proposed agenda is: - Roll call - Follow up on tracked action items - Gate health check - Implementation of Unmaintained branch statuses - Testing runtime for 2024.2 release (gmann) - https://review.opendev.org/c/openstack/governance/+/908862 - Murano inactivity and Caracal release - Should https://review.opendev.org/c/openstack/governance/+/908859/ be landed with/without the release removal change? - 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

OpenDev Removing CentOS 7 Test Nodes from Zuul and Nodepool on March 15
by Clark Boylan 04 Mar '24

04 Mar '24

The OpenDev team has been cleaning up old distro releases from Zuul and Nodepool. Recently, OpenSUSE Leap 15.2 and Debian Buster were removed. Next up on the list is CentOS 7. Unlike Leap and Buster, CentOS 7 is/was used quite a bit more in Zuul configs. According to codesearch [0] these projects are still using CentOS 7 in their master branches: * Swift * OpenStack Ansible * Devstack * Freezer * Solum * Octavia This is likely an incomplete list of OpenStack projects that need cleanup, and I know there are other projects to clean up outside of OpenStack. It would be great if we can clean this up in the near future (and thank you to those of you who have already started). This ensures we don't have another stable branch perpetuating old configs that need cleanup. I have also asked the release team to start communicating cleanups happen early around release time rather than waiting for branch EOL to prevent these configs moving through our releases unnecessarily. Cleanup will also minimize impact when we remove the node type from our CI system on March 15, 2024. The motivation for this cleanup effort is that we've got a number of old distro releases in the CI system that need care and feeding which are either EOL, soon to be EOL, or otherwise unused. Removing these test node types gives us room to add new test node types like the upcoming Ubuntu 24.04 release. We plan to remove Ubuntu Xenial test nodes after CentOS 7 is removed if you want to get a head start on that cleanup too. We understand that this may impact the OpenStack release which is why I'm sending this email. At the same time we want to be in a position where we can have new distro releases ready in a reasonable time frame which necessitates cleanup like this. Please feel free to respond to this thread with any questions or concerns. [0] https://codesearch.opendev.org/?q=centos-7 Clark

1 0

[manila] What's the status of the virtiofs driver?
by Thomas Goirand 04 Mar '24

04 Mar '24

Hi, I've been waiting for this promising feature for a long time already, so I went to check, and saw that in launchpad [1], the blueprint seemed implemented. Though I didn't see anything in Manila's docs about it. So what's the status of this driver? Is it soon ready? Cheers, Thomas Goirand (zigo) [1] https://blueprints.launchpad.net/nova/+spec/libvirt-virtiofs-attach-manila-…

5 5

[neutron] Bug deputy report Feb 25 - Mar 4
by Jakub Libosvar 04 Mar '24

04 Mar '24

Hi, there were only 3 bugs reported. Nothing critical. High —— - [ovn-octavia-provider] OVN LB health checks for IPv6 not working Edit https://bugs.launchpad.net/neutron/+bug/2055876 Assigned to Fernando Low —— - [OVN] "LRP.external_ids" router name is incorrect, we are setting the ID only https://bugs.launchpad.net/neutron/+bug/2055045 Unassigned - [stable-only][OVN] Configure VETH interface MAC address before setting UP the device Edit https://bugs.launchpad.net/neutron/+bug/2055561 Assigned to Rodolfo Patches proposed and merged. May get closed soon.

1 0

[PTLs][release] 2024.1 / Caracal Cycle Highlights
by Herve Beraud 04 Mar '24

04 Mar '24

Hello Everyone! The deadline for cycle highlights is just a few days away, on March 8 [1]. Please be sure to get those in. I look forward to seeing what all you all have accomplished this release! How To Reminder: ------------------------- Simply add them to the deliverables/$RELEASE/$PROJECT.yaml in the openstack/releases repo like this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin. The formatting options for this tag are the same as what you are probably used to with Reno release notes. Also, you can check on the formatting of the output by either running locally: tox -e docs And then checking the resulting doc/build/html/$RELEASE/highlights.html file or the output of the build-openstack-sphinx-docs job under html/$RELEASE/ highlights.html. Thanks [1] https://releases.openstack.org/caracal/schedule.html -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[publiccloud-sig] Reminder - next meeting March 6th - 0800 UTC
by Felix Kronlage-Dammers 04 Mar '24

04 Mar '24

Hi everyone, This Wednesday (March 6th) the next meeting of the public cloud sig is going to happen. We’ll be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig Important: this is a different place than previously. I’ve also updated the Wiki page of the Public-Cloud SIG to reflect this. See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG See you Wednesday! 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

[cinder] FFE request for HPE XP: supporting HA in 2024.1
by 河合敦史 / KAWAI，ATSUSHI 04 Mar '24

04 Mar '24

Hi, I would like to request FFE in the 2024.1 Caracal cycle for the following patch: https://review.opendev.org/c/openstack/cinder/+/892608 Reason for FFE: This patch is one of the important feature for HPE XP driver because it supports a `storage assisted' High Availability. We added the patch into the feature lists for both 2023.2 Bobcat cycle, but it's been merged yet. Additionally, some bugfix patches have a relation chain to this patch. These includes a bug which issued at a customer site on RHOSP. These patches couldn't be merged until merged this patch. Best regards, Atsushi Kawai

2 2

[oslo][release][requirement] FFE request and RFE request for castellan
by Takashi Kajinami 04 Mar '24

04 Mar '24

Hello, We recently caught that castellan 4.4.0, the latest release for caracal, introduced the backword-incompatible change[1] which breaks the existing usage in nova. While we are resolving the problem by the change in nova[2], we discussed this problem in #openstack-release[3], and we agreed that we should make major bump with the upgrade impact properly documented in a release note to announce the breaking change more clearly. Based on the agreement, I'm now preparing a new castellan 5.0.0 release, with the upgrade note added[4]. I'd like to request approval about this release, and also the subsequent upper constraint change to pull castellan 5.0.0 to 2024.1 release. Please let me know if you have any question/concern/etc. Thank you, Takashi [1] https://review.opendev.org/c/openstack/castellan/+/895502/ [2] https://review.opendev.org/c/openstack/nova/+/896100 The same fix for cinder was merged some time ago. https://review.opendev.org/c/openstack/cinder/+/896121 [3] https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-rele… [4] https://review.opendev.org/c/openstack/castellan/+/910884 https://review.opendev.org/c/openstack/releases/+/910883 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

Re: openstack-discuss Digest, Vol 64, Issue 122
by BEDDA Fadhel 02 Mar '24

02 Mar '24

help: su -s /bin/bash keystone -c "keystone-manage db_sync" error : Exception ignored in: <function _removeHandlerRef at 0x7f33d74bc3a0> Traceback (most recent call last): File "/usr/lib/python3.10/logging/__init__.py", line 846, in _removeHandlerRef File "/usr/lib/python3.10/logging/__init__.py", line 226, in _acquireLock File "/usr/lib/python3.10/threading.py", line 164, in acquire File "/usr/lib/python3/dist-packages/eventlet/green/thread.py", line 34, in get_ident AttributeError: 'NoneType' object has no attribute 'getcurrent' Thanks Le ven. 1 mars 2024 à 11:17, <openstack-discuss-request(a)lists.openstack.org> a écrit : > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > openstack-discuss-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-discuss-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of openstack-discuss digest..." > > Today's Topics: > > 1. [all][ptls][release] Action needed to move forward Unmaintained > branch policy > (Jay Faulkner) > 2. Re: [blazar] Proposing Mark Powers and Matt Crees as core reviewers > (Pierre Riteau) > 3. [oslo] Removing feature branches of oslo.messaging > (Takashi Kajinami) > 4. Re: [all][ptls][release] Action needed to move forward Unmaintained > branch policy > (Dmitriy Rabotyagov) > 5. Re: Need Help to setup Bumblebee VDI project (Andy Botting) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 Feb 2024 14:18:36 -0800 > From: Jay Faulkner <jay(a)gr-oss.io> > Subject: [all][ptls][release] Action needed to move forward > Unmaintained branch policy > To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Message-ID: > < > CA+sTGNekJcbP3-ePYjq90ghSiYO-QiNB1dSd0XbVtjV6nktstQ(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="0000000000009bb91406128ca449" > > Hi all, > > If you are a PTL of a project, a release liason, or a person generally > interested in older OpenStack branches, please make sure you take a look at > the topic here: https://review.opendev.org/q/topic:%22vwx-unmaintained%22 > and vote appropriately on projects you care about. > > More information can be found in the commit message for the patches > themselves. > > A lot of folks have done work behind the scenes to enable this transition; > please help us by doing your part and getting these reviews done in a > timely manner is one way we can show gratitude to the releases team and > others who have worked to make this transition possible. > > Thanks, > Jay Faulkner > OpenStack TC Chair >

1 0

Need Help to setup Bumblebee VDI project
by Artemio Mendoza 01 Mar '24

01 Mar '24

Hello, I'm trying to set up the Bumblebee (https://github.com/NeCTAR-RC/bumblebee) project on my local computer to test. So I installed docker and tried setup by following the readme. But I'm really new in OpenStack (only tried to run OpenStack through devstack) so I would appreciate it if I could have a very detailed guide. So please share any idea, online video link, or guide document. anything is good to me. Looking forward to hearing from you. Thanks, Artemio Mendoza

3 4

[manila] Feature Freeze Exceptions
by Carlos Silva 01 Mar '24

01 Mar '24

Hello, Zorillas! During this week's IRC meeting we talked about the features we are working on and that need a feature freeze exception, and three contributors shared changes that need some more time to get to completion: 1. Human Readable Export locations: https://review.opendev.org/c/openstack/manila/+/908897 - Core + API https://review.opendev.org/c/openstack/python-manilaclient/+/908909 - CLI https://review.opendev.org/c/openstack/manila/+/908907 - NetApp driver implementation This change relates to an RFE created by operators a couple of cycles ago, and it will enhance the usability for Manila users while mounting shares. The author of this change has been responding to all comments and actively working with the reviewers to implement the suggested modifications. The author mentioned that he would need more time to fix the review comments. 2. Share backups for NetApp driver: https://review.opendev.org/c/openstack/manila/+/910595 - Changes to the backup base driver https://review.opendev.org/c/openstack/manila/+/909115 - NetApp Backup driver The generic approach for share backups was implemented in the previous cycle and NetApp is working on a driver-specific implementation for backups. The author has also been actively working with the reviewers providing updates, but more time would be needed for more review rounds. 3. Deferred deletion: https://review.opendev.org/c/openstack/manila/+/907051 This is also a feature we have been designing for a while, and it will be useful when the backend takes a lot of time to delete shares. Manila will be able to release the quotas and track the shares deletion in the background. The author worked on review comments very fast and addressed the issues pointed by the reviews, but we still need some more review rounds. I would like to grant a feature freeze exception for the three features mentioned and we should aim to merge them by the end of the next week (march 8th). Thank you, carloss

1 0

[release][ironic][swift] cycle-with-intermediary deliverables without any release
by Elõd Illés 01 Mar '24

01 Mar '24

Hi, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the 2024.1 Caracal cycle: [swift] swift [ironic] bifrost ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch Those should be released ASAP, and in all cases before March 14th, so that we have a release to include in the final 2024.1 Caracal release. Előd Illés irc: elodilles @ #openstack-release

2 1

[oslo] Removing feature branches of oslo.messaging
by Takashi Kajinami 01 Mar '24

01 Mar '24

Hello, # I already discussed this with a few people but am sending this email # mostly for records. Currently we have a few feature branches in oslo.messaging but it seems these are not actually used now. feature/amqp-dispatch-router : the feature was already merged into master feature/nats-driver : this branch contains no meaningful change feature/pika : the feature was already merged into master feature/zmq : the feature was already merged into master I'd propose deleting these useless branches. Note that currently the nats-driver branch is causing config error in zuul, which was triggered by TripleO's retirement, and my quick attempt revealed that, as I expected, CI in that branch is badly broken. Please let me know if you have any concern. Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

3 2

[release] Release countdown for week R-4, March 04-08
by Herve Beraud 01 Mar '24

01 Mar '24

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the 2024.1/Caracal deliverables can be proposed, well ahead of the final 2024.1/Caracal release date. General Information ------------------- We are still finishing up processing a few release requests, but the 2024.1/Caracal release requirements are now frozen. If new library releases are needed to fix release-critical bugs in 2024.1/Caracal, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in 2024.1/Caracal that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By March 25, 2024 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/2024.1 branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for 2024.1/Caracal changes should be added there to make sure the consumers of your release notes see them. Upcoming Deadlines & Dates -------------------------- Cycle Highlights Due: March 7th, 2024 (R-4 week) RC1 deadline: week of March 11, 2024 (R-3 week) Final RC deadline: week of March 25, 2024 (R-1 week) Final 2024.1/Caracal release: April 3, 2024 Dalmatian PTG: April 8-12, 2024 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[TC][openapi] Request for new projects under the OpenStack hat
by gtema 01 Mar '24

01 Mar '24

Hi TC representatives, Some time ago I was communicating about my POC on generating OpenAPI schemas from the source code of services. I continued working on that and have now few projects (that I was developing on GitHub to make life easier) that I would like to bring under the OpenStack hood (and place them under the SDK team). I have also figured out that Nova is now reviewing spec on starting using supporting this (thanks Stephen) and Neutron folks expressed also interest. === codegenerator https://gtema.github.io/openstack-codegenerator/ This project is responsible for generation of the OpenAPI specs and generate other (currently user-facing) code ouf of them === openstack-openapi https://gtema.github.io/openstack-openapi/ This repo hosts rendered specs and provides analogue to the os-api-ref Sphinx extension that renders them into the html (what you see under the link is a mix of Swagger and os-api-ref style). I was not really effectively working on that rendering lately, the repo right now is more or less a storage for the specs themselves with a first sketch of sphinx extension of rendering and basic OpenAPI flavoring doc. === openstack-rs https://gtema.github.io/openstack/ This is a Rust monorepo project with few items: - SDK for OpenStack out of the rendered OpenAPI specs - experimental CLI following very different approach compared to the python- openstackclient. It is compiled into single binary (what helps those not willing to pull whole python with all deps and the insanity we experience lately or those who build docker containers with only OSC inside to bypass the mentioned hell) and purely auto-generated from the specs - [future] openstack-tui (similar to k9s for Kubernetes) Here it is all really oriented only on the user facing tooling. I am very convinced in this project and will continue working on it independent on the outcome. Any objections/ideas/comments? Should I just go and create 3 project-config changes pending the approval? ====== Since I am on this topic anyway I would also like to address another related question. While working for OpenTelekomCloud we developed HashiVault plugin for managing OpenStack credentials as secrets (I had a talk on that in Vancouver). We tried to bring this to OpenDev but were unsure under which namespace. Pretty shortly a Hashi license issue started circling around and after few back and forth iterations we were not sure what to do with that project at all. Anyway the plugin itself is Apache-2 and working. It should be possible to also use it with OpenBAO (as a fork of Vault), but it was not tested so far. I am now not with Telekom anymore, but people there are still willing to contribute it under the OpenStack. Do you have any opinions on that? Is there interest in getting this under the OpenDev and if yes then which namespace (openstack or X)? ======= Thanks, Artem

4 5

[tacker] Gate broken, and a fix patch has been posted
by Ayumu Ueha (Fujitsu) 01 Mar '24

01 Mar '24

Hi Tacker team, As you may know, the following two tacker’s gate jobs are broken since Feb 28. * tacker-functional-devstack-multinode-sol * tacker-functional-devstack-multinode-sol-multi-tenant I have investigated the cause, and posted bug report [1] and fixed patch [2]. Please refer to [1] and [2] for the problem and fix details. To: Yasufumi and Toshiaki, I have already confirmed that the above job is successful. Could you kindly review the patch [2] and merge it if it is no problem. [1] https://bugs.launchpad.net/tacker/+bug/2055431 [2] https://review.opendev.org/c/openstack/tacker/+/910720 Regards, Ayumu

1 0