June 2022 - openstack-discuss - lists.openstack.org

[Neutron] team meeting - 28.06.2022. - cancelled
by Lajos Katona 27 Jun '22

27 Jun '22

Hi, As I said in the last Team meeting (see [1]) I am OoO this Tuesday, so can't drive the coming meeting. [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-06-21… Best wishes, and see you online. Lajos Katona (lajoskatona)

1 0

[neutron] Drivers meeting agenda - 24.06.2022.
by Lajos Katona 27 Jun '22

27 Jun '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * [RFE] Improve performance of bulk port create/delete with networking-generic-switch (#linkhttps:// bugs.launchpad.net/neutron/+bug/1976270) * Neutron RBAC not sharing subnet (#link https://bugs.launchpad.net/neutron/+bug/1975603) * [ovn]Floating IP adds distributed attributes (#link https://bugs.launchpad.net/neutron/+bug/1978039) * [RFE] Adding the "rekey" parameter to the api for strongswan like "dpd_action" (#link https://bugs.launchpad.net/neutron/+bug/1979044) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

2 2

[nova] NVLink passthrough
by Cory Hawkvelt 27 Jun '22

27 Jun '22

Hey team, Is anyone working with NVLink in their clouds? How are you handling passing through the right set of GPU's per NVLink 'group' I have servers with 4 sets of 2 way NVLinks(8 cards in pairs of 2) and I'm able to passthrough the PCI devices to the VM no problem but there is no guarantee that the NVLink pair get passed through together and if we end up with 1 GPU from one pair and 1 GPU from another pair then we run into all sorts of issues(As you'd expect) So I'm looking to understand how Nova can be NVLink aware I guess but I'm struggling to find any conversation ro material on the topic but I assume it's been done before? I did find this talk [1] which mentioned this problem but they write some sort of hack to sit in between nova and qemu, while quite a clever solution it seems like there must be a better way to do this in 2022? [1] - https://www.openstack.org/videos/summits/vancouver-2018/can-we-boost-more-h… Cheers, Cory

2 1

[cinder] Spec Freeze in effect
by Rajat Dhasmana 27 Jun '22

27 Jun '22

Hello Argonauts, As per the scheduled deadline[1], the cinder spec freeze is in effect. If you would like to continue working on your spec to get it merged and implemented in the Zed development cycle, please request a spec freeze exception as a new email to the Openstack Discuss mailing list[2] describing the reason for not making it into the deadline and hence it will be granted the spec freeze exception. The deadline for proposing the spec freeze exception is by 1st July, 2022 and the specs granted spec freeze exception should be merged by 8th July, 2022. Following are the specs that are targeted for the Zed cycle: 1) Spec to introduce additional task status field Patch: https://review.opendev.org/c/openstack/cinder-specs/+/818551 Needs an update from the author. 2) WIP: Add new volume transaction tracking Patch: https://review.opendev.org/c/openstack/cinder-specs/+/845176 Since this is a WIP, I'm not sure the intention is to get it into Zed specifically. 3) volume list query optimization Patch: https://review.opendev.org/c/openstack/cinder-specs/+/726070 Has a +2 but still lacks review from the main cinder core team. 4) Update original resource's az Patch: https://review.opendev.org/c/openstack/cinder-specs/+/778437 Hasn't been updated since 31st March so looks less likely to make it into Zed. 5) New Quota System Patch: https://review.opendev.org/c/openstack/cinder-specs/+/819693 Needs to be retargeted for Zed and updated as per PTG discussion. Also would like to request the cinder core team to take a look at the open specs. [1] https://releases.openstack.org/zed/schedule.html#z-cinder-spec-freeze [2] openstack-discuss(a)lists.openstack.org Thanks and regards Rajat Dhasmana

1 0

[neutron] bug deputy report for week of 2022-06-20
by Bence Romsics 27 Jun '22

27 Jun '22

Hi Neutron Team, Here comes the deputy report for last week: High: * https://bugs.launchpad.net/neutron/+bug/1979047 Interface attach fails with libvirt.libvirtError: internal error: unable to execute QEMU command 'netdev_add': File descriptor named '(null)' has not been found gate failure caused by libvirt bug in centos stream 9, affected tests blacklisted until centos fix arrives: https://review.opendev.org/c/openstack/neutron/+/846905 * https://bugs.launchpad.net/neutron/+bug/1979661 [stable/train] member_batch_update breaks contract with octavia-api interface fix merged: https://review.opendev.org/c/openstack/networking-ovn/+/847255 Medium: * https://bugs.launchpad.net/neutron/+bug/1979643 ``get_ports`` query done in ``check_baremetal_ports_dhcp_options`` cannot filter by VNIC type fix waiting for workflow+1: https://review.opendev.org/c/openstack/neutron/+/847346 Still in discussion with reporter: * https://bugs.launchpad.net/neutron/+bug/1979528 neutron dnsmasq keeps pushing the default gateway * https://bugs.launchpad.net/neutron/+bug/1979089 l3ha router delete race condition if state changes to master Cheers, Bence (rubasov)

1 0

Re: [Swift] [kolla] Swift issues in one cluster
by Albert Braden 27 Jun '22

27 Jun '22

We're running 2.23.3 but it appears that we are experiencing the bug (1). We tracked the problem down to a client who recently started using a java library to read large files from Swift. When he moves his activity to the other QA cluster, the problem follows. Am I guessing correctly that the bug was never fixed, and that (2) fixes a different problem? On Thursday, June 23, 2022, 10:43:44 AM EDT, Clay Gerrard <clay.gerrard(a)gmail.com> wrote: https://review.opendev.org/c/openstack/swift/+/575254 has been included in every released swift tag since 2.21.0 I believe Train included a swift version of at least 2.22 https://releases.openstack.org/train/#swift Nvidia doesn't use haproxy in front of our swift proxies, and we don't see BlockingIOError in tracebacks - the traceback might go away if you upgrade to the latest swift (2.29) and/or eventlet and/or python 3.8ish On Thu, Jun 23, 2022 at 8:49 AM Albert Braden <ozzzo(a)yahoo.com> wrote: Can anyone help with this Swift issue? It looks like we are being hit with this bug (1) but this bug doesn't seem to mention where/whether it was ever fixed. This (2) appears to be a fix, and it appears to have been merged, but it doesn't mention the bug, and it's not obvious to me what version it affects. Is anyone else encountering this problem? It appears that customers in this one cluster may be doing something to cause it; we're still trying to track down specifically what they are doing, that they aren't doing in the other clusters. We are running kolla-ansible Train on RHEL7. 1. https://bugs.launchpad.net/swift/+bug/1572719 2. https://opendev.org/openstack/swift/commit/0e81ffd1e1481a73146fce17f61f2ab9… On Wednesday, June 22, 2022, 05:10:10 PM EDT, Albert Braden <ozzzo(a)yahoo.com> wrote: Is this bug fixed in Train? https://bugs.launchpad.net/swift/+bug/1572719 On Tuesday, June 21, 2022, 09:26:47 AM EDT, Albert Braden <ozzzo(a)yahoo.com> wrote: All of our endpoints are https: +----------------------------------+--------+--------------+--------------+---------+-----------+---------------------------------------------------------+ | ID | Region | Service Name | Service Type | Enabled | Interface | URL | +----------------------------------+--------+--------------+--------------+---------+-----------+---------------------------------------------------------+ | <ID> | <region> | keystone | identity | True | internal | https://api-int.<region>.<domain>:5000 | | <ID> | <region>| swift | object-store | True | public | https://swift. <region>.<domain>:8080/v1/AUTH_%(tenant_id)s | | <ID> | <region>| swift | object-store | True | internal | https://swift.<region>.<domain>:8080/v1/AUTH_%(tenant_id)s | | <ID> | <region>| keystone | identity | True | admin | https://api-int. <region>.<domain>:35357 | | <ID> | <region>| keystone | identity | True | public | https://api-ext. <region>.<domain>:5000 | | <ID> | <region>| swift | object-store | True | admin | https://swift. <region>.<domain>:8080/v1 | +----------------------------------+--------+--------------+--------------+---------+-----------+---------------------------------------------------------+ I don't think this is causing the issue; all of our clusters are setup the same. We did think it was load at first, and got the 2 heaviest users to stop what they were doing, but that didn't make a difference. Our other QA cluster has similar load and identical hardware. When I look at the network graphs, I see traffic spiking up to 1G, but these are 25G interfaces, and none of the resources on the boxes are exhausted. CPU is 97% idle; memory is 30% used, disk is not full. It doesn't look like the problem is load-related. We see the haproxy connections stacking up even when load is low. What else could be causing this? On Friday, June 17, 2022, 11:12:36 PM EDT, Pete Zaitcev <zaitcev(a)redhat.com> wrote: On Fri, 17 Jun 2022 17:33:27 +0000 (UTC) Albert Braden <ozzzo(a)yahoo.com> wrote: > $ openstack container list > Unable to establish connection to https://swift.<region>.<domain>:8080/v1/AUTH_<project>: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer') Right away I have a question: why in the world are you connecting to 8080 with HTTPS? > (from Splunk): > Payload: swift-proxy-server: STDERR: File "/usr/lib64/python3.6/socket.py", line 604, in write#012 return self._sock.send(b) > Payload: swift-proxy-server: STDERR: BlockingIOError > Payload: swift-proxy-server: STDERR: os.read(self.rfd, 1) > Payload: swift-proxy-server: STDERR: File "/usr/lib/python3.6/site-packages/eventlet/wsgi.py", line 818, in process_request#012 proto.__init__(conn_state, self) This looks quite fishy to me, because the os.read is in swift/common/utils.py and it's responsible for the mutex. > When we look at network connections, we see haproxy stacking up (many lines of this): > > # netstat -ntup | sort -b -k2 -n -r | head -n +100 > tcp 5976932 0 127.0.0.1:60738 127.0.0.1:8080 ESTABLISHED 13045/haproxy > tcp 5976446 0 127.0.0.1:58480 127.0.0.1:8080 ESTABLISHED 13045/haproxy > tcp 5973217 0 127.0.0.1:33244 127.0.0.1:8080 ESTABLISHED 13045/haproxy > tcp 5973120 0 127.0.0.1:51836 127.0.0.1:8080 ESTABLISHED 13045/haproxy > tcp 5971968 0 127.0.0.1:58516 127.0.0.1:8080 ESTABLISHED 13045/haproxy > ... > > If we restart the swift_haproxy and swift_proxy_server containers then the problem goes away, and comes back over a few minutes. Where should we be looking for the root cause of this issue? Indeed if so many requests are established, you're in trouble. The best fix, I think, is to find the customer who's doing it and punish them. Otherwise, quotas and the ratelimiting middleware are your friends. There's also a possibility that your cluster is underperforming, although usually that results in 500 results first. But then again, at times users would "compensate" for issues by just launching way more requests, in effect DoS-ing the cluster even worse. -- Pete -- Clay Gerrard210 788 9431

2 5

[all] Failure to build (FTBFS) with Sphinx 5.0 and docutils 0.18
by Thomas Goirand 27 Jun '22

27 Jun '22

Hi, A number of bugs were filed against the Debian packages I maintain. Here's the list of bugs: https://bugs.debian.org/1013410 Nova https://bugs.debian.org/1013406 os-api-ref https://bugs.debian.org/1013402 openstacksdk https://bugs.debian.org/1013394 dogpile.cache https://bugs.debian.org/1013393 repoze.who https://bugs.debian.org/1013382 cloudkitty I'd appreciate a bit of help from the OpenStack project here, to fix these before Sphinx 5 and Docutils 0.18 are uploaded to Debian Unstable. If you do have a fix, a quick link in these bug reports would be lovely. Cheers, Thomas Goirand (zigo)

3 3

[all][horizon][django 4.0] Failure to build (FTBFS) with Django 4.0
by Thomas Goirand 27 Jun '22

27 Jun '22

Hi, A number of RC bugs were filed against my packages in Debian Unstable: https://bugs.debian.org/1013488 Horizon https://bugs.debian.org/1013475 django-pyscss https://bugs.debian.org/1013515 ironic-ui https://bugs.debian.org/1013605 django-formtools https://bugs.debian.org/1013603 enmerkar https://bugs.debian.org/1013506 ara If you have a fix, and can post the link to the patch in the Debian bug tracker, that'd be very much appreciated and help these packages not being auto-removed from Debian testing. Otherwise, you can always ping me on IRC. Cheers, Thomas Goirand (zigo)

2 2

[Ceph Rados Gateway] 403 when using S3 client
by Taltavull Jean-François 27 Jun '22

27 Jun '22

Hi All, I get an http 403 error code when I try to get the bucket list with Ubuntu (Focal) S3 client (awscli). S3 api has been activated in radosgw config file and EC2 credentials have been created and put in S3 client config file. Otherwise, everything is working fine with OpenStack client. My deployment: - OSA 23.2.0 - OpenStack Wallaby - Ceph and Rados GW Octopus Has any of you already experienced this kind of behaviour ? Many thanks, Jean-Francois

3 6

Re: [heat-translator][tacker] Propose Hiromu Asahina (h-asahina) for heat-translator core team
by Hiromu Asahina 27 Jun '22

27 Jun '22

Thank you for your warm feedback. I'll do my best :) By the way, me and Ueha-san who just joined the heat-translator core before me are not listed on heat-translator drivers [1]. I guess it means we don't have the permissions to control the heat-translator launchpad. Is it possible to add us to that list? Best Regards, Hiromu (h-asahina) [1] https://launchpad.net/~heat-translator-drivers/+members On 2022/06/27 13:42, Yasufumi Ogawa wrote: > > > > -------- Forwarded Message -------- > Subject: Re: [heat-translator][tacker] Propose Hiromu Asahina > (h-asahina) for heat-translator core team > Date: Fri, 24 Jun 2022 15:57:18 +0900 > From: Yasufumi Ogawa <yasufum.o(a)gmail.com> > To: Rico Lin <ricolin(a)ricolky.com> > CC: ueha.ayumu(a)fujitsu.com <ueha.ayumu(a)fujitsu.com>, > openstack-discuss(a)lists.openstack.org > <openstack-discuss(a)lists.openstack.org>, HADDLETON, Robert W (Bob) > <bob.haddleton(a)nokia.com>, Ghanshyam Mann <gmann(a)ghanshyammann.com> > > Thanks Rico and all! > > On 2022/06/24 5:03, Rico Lin wrote: >> Hi team >> >> Sorry for the late reply, just added Hiromu to the heat-translator-core. >> >> And welcome Hiromu. >> >> *Rico Lin* >> >> >> On Fri, Jun 24, 2022 at 2:30 AM Yasufumi Ogawa <yasufum.o(a)gmail.com >> <mailto:yasufum.o@gmail.com>> wrote: >> >> Hi heat-translator cores, >> >> We tacker team would like to keep contributing to maintain >> heat-translator, so appreciate if you agree to the proposal kindly. >> >> Cheers, >> Yasufumi >> >> On 2022/06/09 14:14, ueha.ayumu(a)fujitsu.com >> <mailto:ueha.ayumu@fujitsu.com> wrote: >> > Hi Rico, >> > >> > This is just a friendly reminder that we are waiting for your >> action. >> > Or please let us know if there are any other necessary processes. >> > Thanks. >> > >> > Best Regards, >> > Ueha >> > >> > -----Original Message----- >> > From: ueha.ayumu(a)fujitsu.com <mailto:ueha.ayumu@fujitsu.com> >> <ueha.ayumu(a)fujitsu.com <mailto:ueha.ayumu@fujitsu.com>> >> > Sent: Thursday, June 2, 2022 5:39 PM >> > To: openstack-discuss(a)lists.openstack.org >> <mailto:openstack-discuss@lists.openstack.org>; 'Rico Lin' >> <ricolin(a)ricolky.com <mailto:ricolin@ricolky.com>> >> > Subject: RE: [heat-translator][tacker] Propose Hiromu Asahina >> (h-asahina) for heat-translator core team >> > >> > Hi Rico, >> > >> > This proposal is great helpful for us! >> > There seems to be no particular objection, so could you add it to >> heat-translator-core if there is no problem? >> > Thanks. >> > >> > Best Regards, >> > Ueha >> > >> > -----Original Message----- >> > From: ueha.ayumu(a)fujitsu.com <mailto:ueha.ayumu@fujitsu.com> >> <ueha.ayumu(a)fujitsu.com <mailto:ueha.ayumu@fujitsu.com>> >> > Sent: Wednesday, May 25, 2022 1:40 PM >> > To: openstack-discuss(a)lists.openstack.org >> <mailto:openstack-discuss@lists.openstack.org> >> > Subject: RE: [heat-translator][tacker] Propose Hiromu Asahina >> (h-asahina) for heat-translator core team >> > >> > +1 >> > >> > Best Regards, >> > Ueha >> > >> > -----Original Message----- >> > From: Yoshito Ito <yoshito.itou.dr(a)hco.ntt.co.jp >> <mailto:yoshito.itou.dr@hco.ntt.co.jp>> >> > Sent: Wednesday, May 25, 2022 12:31 PM >> > To: openstack-discuss(a)lists.openstack.org >> <mailto:openstack-discuss@lists.openstack.org> >> > Subject: [heat-translator][tacker] Propose Hiromu Asahina >> (h-asahina) for heat-translator core team >> > >> > Hi heat-translator team! >> > >> > I would like to propose Hiromu Asahina (h-asahina) as a member of >> the heat-translator core team. I'm now not able to actively >> contribute to heat-translator, and he can lead the team instead >> of me. >> > >> > He is mainly contributing to Tacker by fixing issues, refactoring >> existing codes, and a lot of helpful reviews, with his experience as >> a research engineer in NTT. Tacker highly depends on heat-translator >> in its main functionality, so I believe he can manage it with his >> knowledge of Tacker. >> > >> > Please vote for his nomination by answering this mail till >> June 1st. >> > >> > Best Regards, >> > >> > Yoshito Ito >> > >> > >>

1 0