- openstack-discuss - lists.openstack.org

[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

[ironic][dib] Ubuntu ramdisk images victoria ironic-python-agent run error
by 韩光宇 21 Feb '23

21 Feb '23

Hi, I made a victoria ramdisk image of ubuntu using the following command, ```shell export DIB_DEV_USER_USERNAME=ipa export DIB_DEV_USER_PWDLESS_SUDO=yes export DIB_DEV_USER_PASSWORD='123' export DIB_REPOLOCATION_ironic_python_agent=/root/ironic-python-agent export DIB_REPOREF_ironic_python_agent=victoria-self export DIB_PYPI_MIRROR_URL=https://pypi.tuna.tsinghua.edu.cn/simple export DIB_NO_PYPI_PIP=1 ironic-python-agent-builder -o my-ssh-ubuntu-ipa-victoria -e selinux-permissive -e devuser ubuntu -e pypi -e pip-cache -e dynamic-login ``` But, in baremtal node clean step, I got the error log from ironic-python-agent （The error.png[1] is a screenshot of the log） ``` Started Ironic Python Agent. ... ImportError: canot import name 'json' from 'werkzeug.wrappers' ``` Is the werkzeug version installed by default too high and incompatible? If this is the reason, can I manually specify a lower version? I have tried to specify Werkzeug in the requirements.txt in the local ironic_python_agent git warehouse as a lower version, but the following error is reported when making image ``` 2023-02-15 13:05:02.689 | ERROR: Cannot install ironic-python-agent==6.4.5.dev3 because these package versions have conflicting dependencies. 2023-02-15 13:05:02.690 | 2023-02-15 13:05:02.690 | The conflict is caused by: 2023-02-15 13:05:02.690 | ironic-python-agent 6.4.5.dev3 depends on Werkzeug==1.0.1 2023-02-15 13:05:02.690 | The user requested (constraint) werkzeug===2.2.2 2023-02-15 13:05:02.690 | 2023-02-15 13:05:02.690 | To fix this you could try to: 2023-02-15 13:05:02.691 | 1. loosen the range of package versions you've specified 2023-02-15 13:05:02.691 | 2. remove package versions to allow pip attempt to solve the dependency conflict 2023-02-15 13:05:02.691 | 2023-02-15 13:05:02.691 | ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ``` I would appreciate any kind of guidance or help. Thank you so so much. [1]: https://photos.app.goo.gl/pimvYyzh3iRXxt5B9

1 0

PTG March 2023 Teams List
by Kendall Nelson 21 Feb '23

21 Feb '23

Hello Everyone! The March 2023 Project Teams List is official! *Projects + Teams* - OpenInfra Foundation Teams - Diversity and Inclusion WG - Edge Computing Group - Environmental Sustainability Working Group - Interop WG - StarlingX - OpenStack Teams - Service Teams - Barbican - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Keystone - Kolla - Kuryr - Magnum - Manila - Neutron - Nova - Octavia - OpenaStackSDK/CLI/Ansible-Collections - OpenStack-Ansible - OpenStackCharms - QA - Tacker - Other Teams - Scientific SIG - PublicCloud SIG OpenStack - Security SIG - OpenStack Technical Committee - RBAC - I18n SIG If your team was planning to meet and isn’t on this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign your team up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — *its FREE!* As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://openinfra-ptg.eventbrite.com

1 0

[kolla] [train] [designate] Terraform "repave" causes DNS records to become orphaned
by Albert Braden 21 Feb '23

21 Feb '23

We have customers who use Terraform to build their clusters. They do a thing that they call “repave” where they run an ansible playbook that calls “terraform destroy” and then immediately calls “terraform apply” to rebuild the cluster. It looks like Designate is not able to keep up, and it fails too delete one or more of the DNS records. We have 3 records, IPv4 forward (A) and reverse (PTR) and IPv6 forward (AAAA). When Designate fails to delete a record, it becomes orphaned. On the next “repave” the record is not deleted, because it’s not associated with the new VM, and we see errors in designate-sink.log: 2023-02-13 02:49:40.824 27 ERROR oslo_messaging.notify.dispatcher [parameters: {'id': '1282a6780f2f493c81ed20bc62ef370f', 'version': 1, 'created_at': datetime.datetime(2023, 2, 13, 2, 49, 40, 814726), 'zone_shard': 97, 'tenant_id': '130b797392d24b408e73c2be545d0a20', 'zone_id': '0616b8e0852540e59fd383cfb678af32', 'recordset_id': '1fc5a9eaea824d0f8b53eb91ea9ff6e2', 'data': '10.22.0.210', 'hash': 'e3270256501fceb97a14d4133d394880', 'managed': 1, 'managed_plugin_type': 'handler', 'managed_plugin_name': 'our_nova_fixed', 'managed_resource_type': 'instance', 'managed_resource_id': '842833cb9410404bbd5009eb6e0bf90a', 'status': 'PENDING', 'action': 'UPDATE', 'serial': 1676256582}] … 2023-02-13 02:49:40.824 27 ERROR oslo_messaging.notify.dispatcher designate.exceptions.DuplicateRecord: Duplicate Record The orphaned record is causing a mariadb collision because a record with that name and IP already exists. When this happens with an IPv6 record, it looks like Designate tries to create the IPv6 record, and fails, and then does not try to create an IPv4 record, which causes trouble because Terraform waits for the name resolution to work. The obvious solution is to tell TF users to introduce a delay between “destroy” and “apply” but that would be non-trivial for them, and we would prefer to fix it on our end. What can I do, to make Designate gracefully manage cases where a cluster is deleted and then immediately rebuilt with the same names and IPs? Also, how can I clean up these orphaned records. I’ve been asking the customer to destroy, and then deleting the record, and then asking them to rebuild, but that is a manual process for them. Is it possible to link the orphaned record to the new VM so that it will be deleted on the next “repave?” Example: This VM was built today: $ os server show f5e75688-5fa9-41b6-876f-289e0ebc04b9|grep launched_at | OS-SRV-USG:launched_at | 2023-02-16T02:48:49.000000 The A record was created in January: $ os recordset show 0616b8e0852540e59fd383cfb678af32 1fc5a9ea-ea82-4d0f-8b53-eb91ea9ff6e2|grep created_at | created_at | 2023-01-25T02:48:52.000000 |

3 5

Propose Yadnesh Kulkarni for Telemetry Core
by Matthias Runge 21 Feb '23

21 Feb '23

Hi, Yadnesh ramped up pretty quickly in the Telemetry project space and helped with fixing the gate, but also proposed enhancements and fixes for ceilometer, aodh and the clients. He provided good and helpful reviews, and if I don't hear any voices against it, I'd promote him to core in 7 days. Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

4 4

[Telemetry][release] release job failure: python-aodhclient 3.1.0
by Elõd Illés 21 Feb '23

21 Feb '23

Hi Telemetry team, we have a release job failure [1], as it seems pypi did not accept the upload of the release [2]. This is probably beccause of a recently added new line in setup.cfg [3]. Can you please try to fix the issue so that we could propose a new release. [1] https://lists.openstack.org/pipermail/release-job-failures/2023-February/00… [2] https://zuul.opendev.org/t/openstack/build/8b0957e7b8af45f99d8412851542492a [3] https://opendev.org/openstack/python-aodhclient/src/branch/master/setup.cfg… Thanks in advance, Előd Illés irc: elodilles @ #openstack-release

4 3

[ironic] This topic describes how to deploy images for the ironic service
by 任亮 20 Feb '23

20 Feb '23

Hi The.kernel and.initramfs images contained in ramdisk are used to use bare metal services. The open source address provides centos ramdisk mirroring.  https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/ https://tarballs.opendev.org/openstack/ironic-python-agent-builder/dib/file… I want to build our own ramdisk mirror, and I would like to ask whether there is a way to manually make ramdisk mirror. If so, how to add the ironic python agent service to it? Or use the ironic-python-agent-builder tool to support other system construction methods. 发自我的企业微信

4 4

[ironic][release] Dmitry no longer release liason
by Jay Faulkner 20 Feb '23

20 Feb '23

Hey all, Dmitry has gotten busier as our secret agent in the CNCF working on Metal3.io -- we're lightening his load on this side by dropping him as a release liaison for Ironic at his request. Riccardo and Iury will remain as release liaisons for Ironic. This email is being sent for transparency purposes. We'll obviously welcome Dmitry to rejoin as a liaison when and if his time allows. Thanks for the help keeping on top of releases the last few years! -Jay Faulkner

1 0

*[cinder] Request for Feature Freeze Exception*
by 河合敦史 / KAWAI，ATSUSHI 20 Feb '23

20 Feb '23

Hi Team, I'd like to request FFE for following patch: *Hitachi: support data deduplication and compression* Patch: https://review.opendev.org/c/openstack/cinder/+/850831 Status: Fix merge conflict and add unit test Why missed the deadline is merge conflict when it occurred at the deadline day. I'll upload this patch, which is rebased and fixed unresolved review comment, by Feb 21st. This feature is useful for capacity saving, and is isolated to the Hitachi driver module, and have no impact on the Cinder database, REST/RPC and APIs. Best regards, Atsushi Kawai

2 1

[neutron] Bug Deputy Report February 13 - 19
by Yatin Karel 20 Feb '23

20 Feb '23

Hello Neutron Team !! Please find bug report from February 13th to 19th, Undecided bugs needs further triage:- *Critical:-* - https://bugs.launchpad.net/neutron/+bug/2007152 - Race condition in DHCP agent cause deletion of the dhcp port as stale port Assigned to slawek - https://bugs.launchpad.net/neutron/+bug/2007254 - [UT] "test_create_ndp_proxy_with_duplicated" fail Fixed with https://review.opendev.org/q/I2fcad691df4a7ae112e1d55fefe662016430aa5b Aassigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2007166 - [tempest] CI job "neutron-ovn-tempest-ipv6-only-ovs-release" unstable, most of the times because of "test_hotplug_nic" Fix proposed https://review.opendev.org/c/openstack/neutron/+/874112 Assigned to yatin - https://bugs.launchpad.net/neutron/+bug/2007565 - [tempest] "test_network_basic_ops" failing randomly Fix proposed https://review.opendev.org/c/openstack/neutron/+/874112 Assigned to ralonsoh *High:-* - https://bugs.launchpad.net/neutron/+bug/2007357 - Grenade jobs failing due to failed ping to the test instance Unassigned - https://bugs.launchpad.net/neutron/+bug/2007553 - [DHCP] TypeError: disable() got an unexpected keyword argument 'network_id' Fix proposed https://review.opendev.org/c/openstack/neutron/+/874073 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2007353 - Functional test neutron.tests.functional.services.ovn_l3.test_plugin.TestRouter.test_gateway_chassis_rebalance fails intermittently Unassigned *Medium:-* - https://bugs.launchpad.net/neutron/+bug/2007327 - Don't send rpc messages about security groups Fix proposed https://review.opendev.org/c/openstack/neutron/+/873850 Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1934666 - IPv6 not set on VMs when using DVR HA + SLAAC/SLAAC (or DHCPv6 stateless) Reopened based on discussion on https://review.opendev.org/c/openstack/neutron/+/869741 *Low:-* - https://bugs.launchpad.net/neutron/+bug/2007414 - [RBAC] "RULE_ADMIN_OR_NET_OWNER_OR_ADVSVC" rule not used any more (Neutron and n-lib) Unassigned *Undecided:-* - https://bugs.launchpad.net/neutron/+bug/2007167 - OVN DHCP replies source from subnet gateway IP Possible Invalid from Neutron perspective, discussion Ongoing - https://bugs.launchpad.net/nova/+bug/2006467 - tempest ssh timeout due to udhcpc fails in the cirros guest Need to root cause it, discussion Ongoing - https://bugs.launchpad.net/neutron/+bug/2007674 - Neutron creates too many connections to rabbitmq Requested more info Thanks and Regards Yatin Karel

1 0

[cinder] Feature freeze in effect
by Rajat Dhasmana 20 Feb '23

20 Feb '23

Hello Argonauts, We are past the feature freeze deadline i.e. 17 Feb, 2023[1]. If you have a feature which you would like to get it into the 2023.1 (Antelope) release, please request a feature freeze exception on the OpenStack discuss mailing list with the following subject: *[cinder] Request for Feature Freeze Exception* Include the patch details, reason for missing the feature freeze deadline and current status in the email. The feature freeze exception will be granted for 1 week i.e. till 24th Feb, 2023 and no features will be accepted after that. Following are the targeted features and their current status: *Hitachi: support data deduplication and compression* Patch: https://review.opendev.org/c/openstack/cinder/+/850831 Status: Fix merge conflict and add unit test *Add iSCSI export support to the StorPool driver* Patch: https://review.opendev.org/c/openstack/cinder/+/847536 Status: Has multiple negative votes with feedback that needs to be addressed *[SVf] Adding support of clone operation for volumegroup* Patch: https://review.opendev.org/c/openstack/cinder/+/871257 Status: Has negative votes with feedback that needs to be addressed *LVM NVMe Target* Topic: https://review.opendev.org/q/topic:lvm-nvmet-shared Status: Need confirmation that the patches are in a reviewable state [1] https://releases.openstack.org/antelope/schedule.html#a-ff Thanks Rajat Dhasmana

2 2

[oslo][OpenStackSDK][heat][keystone][Telemetry][ironic][freezer][senlin][monasca][murano][vitrage][solum][magnum][winstackers][blazar] broken gate on master branch
by Elõd Illés 20 Feb '23

20 Feb '23

Hi $teams_in_subject, I've generated dummy patches to see gate health (to projects' for cycle-with-intermediary deliverables, that have not merged any patches in this year yet) and the patches shows that you have broken CI jobs on your gate. Could the teams please check what the issue / issues are and fix as soon as possible? Thanks in advance! (Note: most of the failures have probably been introduced with tox version 4 release and should be straightforward to fix) Thanks, Előd Illés irc: elodilles @ #openstack-release

4 4

Can't access terminal on website
by vincent lee 20 Feb '23

20 Feb '23

Hi all, I have deployed OpenStack on my system (all with Ubuntu 20.04 Desktop versions) using kolla-ansible deployment. I am able to launch containers and open the terminal (console of containers) in the web-browser from the horizon dashboard. However, when I installed an OpenStack on my system using *Ubuntu 20.04 Server* version using kolla-ansible deployment, all containers were running, but I was not able to access the terminal in the web-browser on the horizon dashboard for the running container. I am getting an error message "*Firefox can't establish a connection to the server at wss://...*" All my OpenStack is deployed using the Python virtual environment. I have been following the exact steps in deploying OpenStack from "https://docs.openstack.org/kolla-ansible/yoga/user/quickstart.html." My current OpenStack version is yoga. Apart from that, I would like to ask if there is any specific path I can make modifications on my OpenStack. Every time when I deployed a fresh OpenStack on my system and tried to make some modifications, the path might not take any effect on the horizon dashboard. Sometimes, modifying the library in /var/lib/kolla/venv/lib/python3.8/site-packages/openstack_dashboard and restarting horizon updates the modification. Sometimes, it might be in /horizon-source/.../openstack_dashboard/. Thank you, Vincent

1 0

[kolla-ansible] Upgrade roadmap
by Nguyễn Hữu Khôi 19 Feb '23

19 Feb '23

Hello guys. I have questions: - Can we upgrade version skipping such as Wallaby to Zed OR Wallaby >> Xena >> Yoga >> Zed? - Is there any way to upgrade Openstack to a new version without host upgrade? Imaging that We have 1000 nodes as a Train version then we need to upgrade to Zed, it is too hard, - Is there any plan to upgrade Xena(Ubuntu 20.04) to Zed(20.04). Thank you. Regards Nguyen Huu Khoi

2 7

Issue on Volume Attach/Detach/Delete in openstack
by sudeb ghosh 19 Feb '23

19 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

[cinder]Improve Cinder backup
by Nguyễn Hữu Khôi 19 Feb '23

19 Feb '23

Hello guys. I want to show Cinder backup pool stats such as size, I search google but there is no cli to achieve this task. One more thing, we also need a progress bar when backup volume. It is a useful feature for users who want to track their backup tasks. Thank you. Regards Nguyen Huu Khoi

1 0

[all][tc] What's happening in Technical Committee: summary 2023 Feb 17: Reading: 5 min
by Ghanshyam Mann 18 Feb '23

18 Feb '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Feb 15. Most of the meeting discussions are summarized in this email. The meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-02-15-16.00.log.html * The next TC weekly meeting will be on Feb 22 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 21. 2. What we completed this week: ========================= * Guidelines for using the OpenStack/project release version/name in 1. releasenotes 2. Documentation[2] * Retire repo from the Governance repo - Retire xstatic-font-awesome[3] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[4]. Open Reviews ----------------- * Seven open reviews for ongoing activities[5]. Deprecation process for TripleO -------------------------------------- You might have seen the ML discussion for TripleO deprecation[6]. TripelO release model is a little different where they do have stable branches till stable/wallaby and after that, it was an independent release. But in the independent release model also, stable/zed branch was cut. With the TripleO deprecation, the team can maintain only till stable/wallaby. This makes the situation a little difficult where we do not have the best possible way to deprecate/retire stable/zed. TC discussed it but could not find any suitable options other than maintaining the stable/zed also. James will be checking this option with TripleO team and updating the ML thread. Election updates -------------------- Technical election nomination for the next cycle has been closed[7]. Even though there is no poll required in PTL as well as in TC elections, the TC campaigning is going on[8] where you can ask question to the TC candidates. Defining 2023 upstream investment opportunities ------------------------------------------------------------ Every calendar year, TC defines the upstream investment opportunities where we need help and the organization can help. I have pushed the patch[9] to define the 2023 calendar year, which is continuing last year's opportunities. Please let TC know if any of the areas/projects you think need help and should be added to this list. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The audit process is going on and a few projects have been completed [10]. There is a discussion also going on in ML[11]. JayF is working on an email template which can be used to communicate to additional developers to transfer the ownership to 'openstackci' account and remove them from the maintainer's list. The process to find the less active projects early in the cycle: ------------------------------------------------------------------------ No update this week. JayF started the etherpad to collect the data and define the criteria to help in this process[12]. Project updates ------------------- * Add Cinder Huawei charm[13] * Add the woodpecker charm to Openstack charms[14] * Retire xstatic-font-awesome[15] * mistral adopting PTL model[16] * Add xstatic-angular-fileupload as Horizon team deliverables[17] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://review.opendev.org/c/openstack/governance/+/872769 [3] https://review.opendev.org/c/openstack/governance/+/872837 [4] https://etherpad.opendev.org/p/tc-2023.1-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03208… [7] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03224… [8] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03224… [9] https://review.opendev.org/c/openstack/governance/+/872233 [10] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [11] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848… [12] https://etherpad.opendev.org/p/project-health-check [13] https://review.opendev.org/c/openstack/governance/+/867588 [14] https://review.opendev.org/c/openstack/governance/+/869752 [15] https://review.opendev.org/c/openstack/governance/+/872837 [16] https://review.opendev.org/c/openstack/governance/+/873260 [17] https://review.opendev.org/c/openstack/governance/+/873845 [18] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Ceph outage cause filesystem error on VM
by Satish Patel 17 Feb '23

17 Feb '23

Folks, I am running a small 3 node compute/controller with 3 node ceph storage in my lab. Yesterday, because of a power outage all my nodes went down. After reboot of all nodes ceph seems to show good health and no error (in ceph -s). When I started using the existing VM I noticed the following errors. Seems like data loss. This is a lab machine and has zero activity on vms but still loses data and the file system corrupt. Is this normal ? I am not using eraser coding, does that help in this matter? blk_update_request: I/O error, dev sda, sector 233000 op 0x1: (WRITE) flags 0x800 phys_seg 8 prio class 0

5 14