February 2023 - openstack-discuss

*[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 18 Feb '23

18 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