February 2023 - openstack-discuss

[manila] Manila Bugsquash (Feb 27th to Mar 3rd)
by Carlos Silva 24 Feb '23

24 Feb '23

Hello Zorillas! We have been planning our bugsquash for a couple of weeks now, and time has come! We have seen a trend on the number of bugs increasing this cycle, and we have identified that we have many bugs that already have a fix proposed but we didn't get those changes merged. Merging such issues would help us to fix those bugs and continue reducing our bug backlog. So for this bugsquash we will be focusing on getting closure for such changes! Vida (vhari) kindly groomed the bugs list [1]. We will be meeting on Monday to have a kick-off call at 16 UTC [2], so we can assign reviewers to the changes or discuss the progress of the changes if that is the case. [1] https://ethercalc.net/8ru5hurhelyl [2] https://bluejeans.com/371190441 Looking forward to see you there! Thank you, carloss

1 0

[all][elections][ptl][tc] Combined PTL/TC 2023.2 cycle Election Nominations End
by Tony Breeds 24 Feb '23

24 Feb '23

The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 9 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Monasca, OpenStack_Charms, Rally, Sahara, Senlin, Swift, Tripleo, Vitrage, Winstackers There are 0 projects that will have elections. -- TC Election Details -- There are 5 candidates for 5 seats. Given that there are no polls that need to be held, this concludes the election process. Congratulations to our new and returning leaders. Thank you, Tony, on behalf of the election officials. [0] https://governance.openstack.org/election/#bobcar-ptl-candidates [1] https://governance.openstack.org/election/#bobcat-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

3 5

[release] Release countdown for week R-3, Feb 27 Mar 03
by Herve Beraud 24 Feb '23

24 Feb '23

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, March 02. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2023.1 branch will be cut. This branch will track the 2023.1 Antelope release. Once stable/2023.1 has been created, the master branch will be ready to switch to 2023.2 Bobcat development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2023.1 Antelope plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2023.1 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2023.1 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be 2023.2 Bobcat) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2023.1 Antelope release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 02 (R-3 week) Final RC deadline: March 17 (R-1 week) Final 2023.1 Antelope release: March 22 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[kolla-ansible] [yoga] [magnum] [k8s] cannot attach persistent volume to pod
by Stuart Whitman 24 Feb '23

24 Feb '23

Hello, When I try to attach a persistent cinder volume to a pod, I get FailedMount and FailedAttachVolume timeout events. I also get these errors in the log of the csi-cinder-controllerplugin-0 pod: E1020 13:38:41.747511 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.VolumeAttachment: the server could not find the requested resource E1020 13:38:41.748187 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.CSINode: the server could not find the requested resource I fixed a CrashLoopBackoff error with the csi-snapshotter container in the csi-cinder-controllerplugin-0 pod by providing the label "csi_snapshotter_tag=v4.0.0" when I created the cluster template. I found that suggestion in an issue on the GitHub cloud-provider-openstack project. I'm not finding any help with this error on Google. Thanks, -Stu _____________________________________ The information contained in this e-mail and any attachments from Group W may contain confidential and/or proprietary information and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, be aware that any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of that fact by return e-mail and permanently delete the e-mail and any attachments to it.

3 5

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 24 Feb '23

24 Feb '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[magnum] Registry other than dockerhub
by Vivian Rook 24 Feb '23

24 Feb '23

We ran into a problem while deploying magnum when another project exhausted the dockerhub limit on anonymous pulls from a few of the kube-system pods that are deployed. Namely: daemonset.apps/k8s-keystone-auth daemonset.apps/openstack-cloud-controller-manager deployment.apps/kubernetes-dashboard deployment.apps/dashboard-metrics-scraper This would fail with an error noting that dockerhub was blocking the request as too many pulls had happened. We could get around this by adding in a secret with a docker login, and editing those deployments and daemonsets to use that credential. It would appear the container_infra_prefix label can be modified to point to a different registry. Though this would mean we would have to clone all of the images, including images that are from registries other than dockerhub. Leading me to wonder if there isn't an existing registry that one can use using magnum, on quay.io or some host that isn't limiting pulls? Alternatively, is it possible that the dockerhub images that do not pull (some do, coredns for instance does, I suspect it is due to it having "Sponsored OSS" status on dockerhub) without limits could be hosted elsewhere? Or perhaps already are and the default that magnum sets to pull could be updated to those? Alternatively, alternatively, I haven't found an option for giving a dockerhub user/pass to magnum in the documentation, and looking at the code it doesn't appear that there is a variable for one, so I suspect it is not there. Could such an option be added? Thank you -- *Vivian Rook (They/Them)* Site Reliability Engineer Wikimedia Foundation <https://wikimediafoundation.org/>

4 3

[barbican][blazar][ec2-api][freezer][kuryr][monasca][murano][neutron][sahara][solum][winstackers] broken gate on master branch
by Elõd Illés 24 Feb '23

24 Feb '23

Hi $teams_in_subject, Similarly like one week ago, I've generated dummy patches to see gate health of projects' deliverables (but for cycle-with-rc deliverables this time), that have not merged patches recently [1]. These patches show that you have broken gate jobs. Could teams please check what those failures are, and fix them as soon as possible? Thanks in advance! (Note: similarly as I've mentioned in my previous mail, these failures are also mostly tox v4 related issues, that should be easy to fix) [1] https://review.opendev.org/q/topic:release-health-check-cwr-antelope+is:open Thanks, Előd Illés irc: elodilles @ #openstack-release

2 1

[all] Any good alternatives to uwsgi?
by Thomas Goirand 23 Feb '23

23 Feb '23

Hi there! It's been a few Debian release that all OpenStack APIs are served using uwsgi. Unfortunately: https://github.com/unbit/uwsgi/commit/5838086dd4490b8a55ff58fc0bf0f108caa4e… The question is then: - Is continuing to use uwsgi sustainable? - Is there good alternatives? I do not like at all using Apache mod_wsgi, because restarting Apache would mean restarting all services. So I prefer something standalone. I have no clue if gunicorn is well suited for the job, and if: - it performs well - it implements the multi-interpreter API (which IMO is mandatory to avoid global interpreter locks...) Any opinion? Cheers, Thomas Goirand (zigo)

12 19

(Openstack-Neutron)ResourceInError: resources.activelogic: Went to status ERROR due to \"Message: Build of instance 6072c3e9-e530-4173-93b0-4338d6651ade aborted: Failed to allocate the network(s), not rescheduling., Code: 500\"\n2023-02-20 16:32:07Z [activelogic]: CREATE_FAILED ResourceInError: resources.activelogic: Went to status ERROR due to \"Message: Build of instance 356868a0-7341-43e4-8711-58d633fd745b aborted: Failed to allocate the network(s), not rescheduling
by Adivya Singh 23 Feb '23

23 Feb '23

Hi Team, I get these error not often , but some times Went to status ERROR due to \"Message: Build of instance 6072c3e9-e530-4173-93b0-4338d6651ade aborted: Failed to allocate the network(s), not rescheduling., Code: 500\"\n2023-02-20 16:32:07Z [activelogic]: CREATE_FAILED ResourceInError: resources.activelogic: Went to status ERROR due to \"Message: Build of instance 356868a0-7341-43e4-8711-58d633fd745b aborted: Failed to allocate the network(s), not rescheduling My initial thought was these errors related to OVS switch as it goes in some kind of a loop while creating a instance, Any thought on this

3 2

keypair missing from users in Open Stack(Xena Version)
by Adivya Singh 23 Feb '23

23 Feb '23

Hi Team, I am facing an issue where key pairs are missing from users project id all of a sudden. Any thoughts on this. Regards Adivya Singh

3 4

[Glance][infra][ci]docs and functional jobs are failing for some stable branches
by Pranali Deore 23 Feb '23

23 Feb '23

Hello Everyone, The openstack-tox-docs job is failing consistently for stable/wallaby branch[1] with below error, ----------------------------------------------------------------------------------------------------- autodoc: failed to import module 'manage' from module 'glance.cmd'; the following exception was raised: No module named 'sqlalchemy.databases' ----------------------------------------------------------------------------------------------------- and openstack-tox-functional job is failing for stable/train [2], seems we need to install some packages for python2.7[3]. Do we need similar changes[4] for openstack-tox-functional as well? These jobs are failing since quite long time and we have some import patches to merge in these stable branches, hence raising this on ML. [1]: https://review.opendev.org/c/openstack/glance/+/871621 [2]: https://review.opendev.org/c/openstack/glance/+/871630 [3]: https://bugs.launchpad.net/tripleo/+bug/2006479 [4]:https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/873020/ Thanks & Regards, Pranali Deore

2 1

[Octavia] Feature freeze exception
by Gregory Thiemonge 23 Feb '23

23 Feb '23

Hi Folks, We would like to request a feature freeze exception for python-octaviaclient in Antelope. A late commit [0] added a dependency on munch, it was included in the 3.3.0 release (the final release for Antelope). But a more recent proposal [1] removes this dependency and updates the code with an easy patch. We are proposing a 3.4.0 release [2] that includes this commit, and we would like this release to become the official python-octaviaclient release for Antelope instead of 3.3.0 (and the starting point of the 2023.1 branch). Thanks. [0] https://review.opendev.org/c/openstack/python-octaviaclient/+/872357 [1] https://review.opendev.org/c/openstack/python-octaviaclient/+/874553 [2] https://review.opendev.org/c/openstack/releases/+/874864

1 0

[ironic][QA][horizon][release][OpenStackSDK] Cycle With Intermediary without recent deliverables
by Herve Beraud 23 Feb '23

23 Feb '23

Hello, Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest $series release available on release week. The following deliverables have done an Antelope release, but it was not refreshed in the last two months: bifrost horizon ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch patrole python-openstackclient tempest You should consider making a new one very soon, so that we don't use an outdated version for the final release. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

3 2

[tempest][neutron] tempest-slow-py3 is failing
by Rajat Dhasmana 23 Feb '23

23 Feb '23

Hello, The tempest-slow-py3 job has been failing consistently since 21 February[1]. Looking at the failure, there is one failing test which looks neutron related[2] (but might be tempest related, not sure). *tempest.scenario.test_network_basic_ops.TestNetworkBasicOps. test_subnet_details* File "/opt/stack/tempest/tempest/lib/common/ssh.py", line 238, in exec_command raise exceptions.SSHExecCommandFailed( tempest.lib.exceptions.SSHExecCommandFailed: Command 'set -eu -o pipefail; PATH=$PATH:/sbin:/usr/sbin; cat /var/run/udhcpc.eth0.pid', exit status: 1, stderr: cat: can't open '/var/run/udhcpc.eth0.pid': No such file or directory Cinder is currently in the feature freeze exception phase and we have few patches that need to be merged within this week (before 24 Feb), hence raising the issue on ML. [1] https://zuul.opendev.org/t/openstack/builds?job_name=tempest-slow-py3&proje… [2] https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Thanks Rajat Dhasmana

6 6

OSP 17 v2 clone status
by Sofia Enriquez 22 Feb '23

22 Feb '23

17.1 Doesn't have v2 clone api enabled https://review.opendev.org/c/openstack/tripleo-ansible/+/803683 --> was reverted -- 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

Glance multistore config makes image service inaccessible Edit | openstack wallaby | tripleo
by Swogat Pradhan 22 Feb '23

22 Feb '23

Hi, Openstack wallaby | tripleo I am trying to setup DCN where i want to setup a glance multistore config in both central and edge sites as per the documentation. But when ever i run stack update with the following config for multistore: [stack@hkg2director ~]$ cat workplace/glance.yaml parameter_defaults: GlanceShowMultipleLocations: true GlanceBackend: rbd GlanceEnabledImportMethods: web-download,copy-image GlanceBackendID: ceph GlanceMultistoreConfig: dcn01: GlanceBackend: rbd GlanceStoreDescription: 'dcn01 rbd glance store' CephClusterName: dcn01 The image service becomes inaccessible. Giving the following error: (overcloud) [stack@hkg2director ~]$ openstack image list Failed to contact the endpoint at https://bolt.bdxworld.com:13292 for discovery. Fallback to using that endpoint as the base url. Failed to contact the endpoint at https://bolt.bdxworld.com:13292 for discovery. Fallback to using that endpoint as the base url. The image service for :regionOne exists but does not have any supported versions. glance api.log from controller nodes: 2023-02-13 13:02:19.878 7 INFO glance.async_ [-] Threadpool model set to 'EventletThreadPoolModel' 2023-02-13 13:02:19.969 7 INFO keyring.backend [-] Loading KWallet 2023-02-13 13:02:19.977 7 INFO keyring.backend [-] Loading SecretService 2023-02-13 13:02:19.982 7 INFO keyring.backend [-] Loading Windows 2023-02-13 13:02:19.983 7 INFO keyring.backend [-] Loading chainer 2023-02-13 13:02:19.983 7 INFO keyring.backend [-] Loading macOS 2023-02-13 13:02:20.571 7 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2023-02-13 13:02:20.711 7 ERROR stevedore.extension [-] Could not load 'glance.store.s3.Store': No module named 'boto3': ModuleNotFoundError: No module named 'boto3' 2023-02-13 13:02:20.719 7 ERROR stevedore.extension [-] Could not load 's3': No module named 'boto3': ModuleNotFoundError: No module named 'boto3' Is there a patch to fix this issue??

5 17

[cinder] Bug Report | 22-08-2023
by Sofia Enriquez 22 Feb '23

22 Feb '23

Hello Argonauts. Hope you are all doing well! High - When creating a backup fails, the volume status is changed to None <https://bugs.launchpad.net/cinder/+bug/2007631>. - *Status*: Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/873862>. - Online extension not seen in guest instance without stop/start or re-attach of the volume <https://bugs.launchpad.net/cinder/+bug/2007779>. - *Status*: No fix proposed to master. - Failure to mount volumes with LUN ID > 255 <https://bugs.launchpad.net/cinder/+bug/2006960>. - *Status*: Same bugs as last week bug open against Cinder project. Medium - A restore from backup ought to keep the sparse volumes <https://bugs.launchpad.net/cinder/+bug/2007615>. - *Status*: No fix proposed to master. Low - The PowerStore driver doesn't allow more than 32 clones <https://bugs.launchpad.net/cinder/+bug/2008024>. - *Status*: No fix proposed to master. - NetApp NFS driver slow for creating a volume native python threads <https://bugs.launchpad.net/cinder/+bug/2008017>. - *Status*: No fix proposed to master. - image_utils: log message uses incorrect variable <https://bugs.launchpad.net/cinder/+bug/2008041>. - *Status*: No fix proposed to master. - *Notes*: Low hanging fruit bug. Good first contribution. - image_utils: misleading log message <https://bugs.launchpad.net/cinder/+bug/2008043> - *Status*: No fix proposed to master. - *Notes*: Low hanging fruit bug. Good first contribution. 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

[cinder] This week's meeting will be in video+IRC
by Rajat Dhasmana 22 Feb '23

22 Feb '23

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (today) will be held in video + IRC mode with details as follows: Date: 22nd February, 2023 Time: 1400 UTC Meeting link: https://bluejeans.com/556681290 IRC Channel: #openstack-meeting-alt Make sure you're connected to both the bluejeans meeting and IRC. Thanks Rajat Dhasmana

1 0

[nova] Clean up "building" instances
by Eugen Block 22 Feb '23

22 Feb '23

Hi, we had a network issue two weeks ago in a HA Victoria cloud resulting in a couple of stale resources (in pending state). Most of them I could cleanup relatively easy, but two instances are left in "building" state, but not yet in the nova database so I can't just remove them via 'openstack server delete <UUID>'. I've been looking through the various nova databases where traces have been left to get an impression where I could intervene (although I don't like manipulating the database). The VMs are two amphora instances: control01:~ # openstack server list --project service | grep -v ACTIVE +--------------------------------------+----------------------------------------------+--------+-------------------------------------------------------------------------------------+---------------------------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+----------------------------------------------+--------+-------------------------------------------------------------------------------------+---------------------------+---------+ | 0453a7e5-e4f9-419b-ad71-d837a20ef6bb | amphora-0ee32901-0c59-4752-8253-35b66da176ea | BUILD | | amphora-x64-haproxy_1.0.0 | amphora | | dc8cdc3a-f6b2-469b-af6f-ba2aa130ea9b | amphora-4990a47b-fe8a-431a-90ec-5ac2368a5251 | BUILD | | amphora-x64-haproxy_1.0.0 | amphora |+--------------------------------------+----------------------------------------------+--------+-------------------------------------------------------------------------------------+---------------------------+---------+ The database tables referring to the UUID 0453a7e5-e4f9-419b-ad71-d837a20ef6bb are these: nova_cell0/instance_id_mappings.ibd nova_cell0/instance_info_caches.ibd nova_cell0/instance_extra.ibd nova_cell0/instances.ibd nova_cell0/instance_system_metadata.ibd octavia/amphora.ibd nova_api/instance_mappings.ibd nova_api/request_specs.ibd My first approach would be to update the nova_cell0.instances table and edit the fields 'vm_state' and 'task_state', or even remove the intire row. But I don't know about the implications this would have on the other tables, so I'd like to know how you would recommend to deal with these orphans. Any comment is appreciated! Thanks, Eugen

3 7

[all][tc] Technical Committee next weekly meeting on 2023 Feb 22 at 1600 UTC
by Ghanshyam Mann 22 Feb '23

22 Feb '23

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2023 Feb 22, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Feb 21 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[openstack-dev][CLI] How to set NoneType in openstack CLI's json format string?
by Sam 22 Feb '23

22 Feb '23

Hi all, I'm using openstack command like this, and got error: ``` gyw@c1:~$ openstack port create --network selfservice --vnic-type remote-managed \ > --binding-profile '{"pci_vendor_info": None, "pci_slot": None, "physical_network": None, "card_serial_number": "AB0123XX0042", "pf_mac_address": "08:c0:eb:8e:bd:f8", "vf_num":1, "vnic_type": "remote-managed"}' \ > pf0vf0 Expected '<key>=<value>' or JSON data for option --binding-profile, but encountered JSON parsing error: Expecting value: line 1 column 21 (char 20) ``` So how to set "pci_vendor_info" to NoneType of python in openstack CLI's json format string? BTW, "NoneType of python" means the NoneType in python code, like these comment in https://github.com/openstack/neutron/blob/stable/yoga/neutron/common/ovn/ut… ``` # With this example param_set: # # param_set = { # 'do_not_check_this_key': None, # 'pci_slot': [str], # 'physical_network': [str, type(None)] # } # # We confirm that each binding_profile key is of one of the listed types, # allowing validation of polymorphic entries. # # 'physical_network' is polymorphic because: When a VNIC_REMOTE_MANAGED or # VNIC_DIRECT with PORT_CAP_SWITCHDEV capability port is attached to a # project network backed by an overlay (tunneled) network the value will be # 'None'. For the case of ports attached to a project network backed by # VLAN the value will be of type ``str``. This comes from Nova and is # provided in the ``physical_network`` tag in the Nova PCI Passthrough # configuration. # # In the above example the type of the value behind 'do_not_check_this_key' # will not be checked, 'pci_slot' must be ``str``, 'physical_network must # be either ``str`` or ``NoneType``. ``` Thank you~ -- Best Regards， ------------------------------------------------ Sam Green Home Page: http://blog.csdn.net/batmancn Email:batmanzg@163.com

1 1

[PTL][release] 2023.1 Antelope Cycle Highlights
by Elõd Illés 21 Feb '23

21 Feb '23

Hi, This is a reminder, that *this week* is the week for Cycle highlights [1][2]! They need to be added to deliverable yamls so that they can be included in release marketing preparations. (See the details about how to add them at the project team guide [3]) Note that the deadline was the Feature Freeze date in previous cycles, but due to requests of PTLs it was decided to postpone one week in the future (to R-4 week). This is better for PTLs as they are usually very busy around Feature Freeze, on the other hand gives less time to marketing team to process the highlights. [1] https://releases.openstack.org/antelope/schedule.html [2] https://releases.openstack.org/antelope/schedule.html#a-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles @ #openstack-release

2 1

[requirements][oslo] RFE for oslo* deliverables
by Herve Beraud 21 Feb '23

21 Feb '23

1 0

Volume can not be detached/deleted properly & Available volume can not be attached with new instance
by sudeb ghosh 21 Feb '23

21 Feb '23

Hi Team, we are using opensource Openstack (Openstack foundation) in our environment. Facing following issues to fix. Need some guidance or suggestion to resolve the same. Problem Detail: 1. We are struggling to delete the volume which are in 'available' state. After deleting from Dashboard/CLI its showing 'deleting' only. 2. Can not detach the volume from any instance. Showing 'detaching' itself. 3. Once status of volume made available by updating table of Database, the volumes are showing 'available' but could not attach further with any existing instance. 4. Once status of volume made deleted by updating table of Database or by deleting the entries of table the volumes are showing status as 'deleted' in CLI(mysql query) & disappeared from Dashboard but reclaiming of space is not happening in storage or quota point of view. Request your guidance with steps to fix the issue pl. BR// Sudeb Ghosh 7044064878 9332034788

2 1

[neutron] Etherpad for Bobcat release, now available
by Rodolfo Alonso Hernandez 21 Feb '23

21 Feb '23

Hello Neutrinos: Please check the link [1]. This is the etherpad for the Bobcat release PTG [2]. If you have any request, RFE, bug, question or topic you want to discuss during the virtual PTG, don't hesitate to add it in the "Topics" section. Once we have collected all of them, we'll create the agenda, adding the corresponding links to the virtual meeting rooms. If you have any question, please contact me (ralonsoh) in the Neutron channel (#openstack-neutron) or via mail. You can also talk to any Neutron core reviewer present in this channel. Regards. [1]https://etherpad.opendev.org/p/neutron-bobcat-ptg [2]https://openinfra.dev/ptg/

1 0