- openstack-discuss - lists.openstack.org

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 20 Feb '23

20 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 20 Feb '23

20 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 19 Feb '23

19 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