14:09:06 #startmeeting cinder 14:09:06 Meeting started Wed Apr 30 14:09:06 2025 UTC and is due to finish in 60 minutes. The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:09:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:09:06 The meeting name has been set to 'cinder' 14:09:09 #topic roll call 14:09:12 o/ 14:09:14 o/ 14:09:14 o/ 14:09:19 o/ 14:09:28 o/ 14:09:41 hi 14:09:43 o/ 14:10:25 hi 14:14:33 hello everyone, welcome 14:14:39 one sec and we'll get started 14:15:31 #link https://etherpad.opendev.org/p/cinder-flamingo-meetings 14:15:37 ^ here's our etherpad 14:15:56 o/ 14:16:03 we do not have any particular topics for today 14:16:47 i know we had some gate issues yesterday, simondodsley, rosmaita: how are things looks from your perspective? 14:16:56 not good 14:17:29 i will be more specific 14:17:52 wonderful, lets get into it :) 14:18:12 simondodsley noticed that there had been a requirements change that broke our py39 based jobs 14:18:20 so i put up a patch for that 14:18:25 #link https://review.opendev.org/c/openstack/cinder/+/948348 14:18:52 and that fixed the functional-py39 failures, but there are 2 other jobs failing 14:19:27 cinder-plugin-ceph-tempest started failing on master on 25 april: 14:19:28 https://zuul.opendev.org/t/openstack/builds?job_name=cinder-plugin-ceph-tempest&project=openstack/cinder 14:19:29 o/ 14:19:50 cinder-tempest-plugin-lvm-lio-barbican started failing monday on master: 14:19:50 https://zuul.opendev.org/t/openstack/builds?job_name=cinder-tempest-plugin-lvm-lio-barbican&project=openstack/cinder 14:21:04 are other barbican jobs failing, or just ours? 14:21:12 good question 14:23:40 https://zuul.openstack.org/builds?job_name=barbican-tempest-plugin-simple-crypto 14:23:41 looks like octavia as well, but there aren't may barbican jobs. I do see more upper-constraints changes in requirements due to osc-lib release... 14:24:38 i thought they tested requirements changes prior to help predict these sorts of failures 14:24:48 i guess maybe not 14:25:08 they mostly run unit tests and possibly functional tests 14:25:29 yes - it looks like barbican is generally failing now as well https://zuul.opendev.org/t/openstack/builds?job_name=*barbican*&project=openstack%2Fbarbican&skip=0 14:25:32 do we know specicically which requirement package/version is causing the failures? 14:25:45 no 14:25:49 at least, i don't 14:26:02 and i don't think we're seeing these fail in the stable branches 14:26:06 it seems to have been around the 29th something changed 14:26:21 (although maybe that's because there's not much new stuff proposed for backport) 14:26:35 correct - only seem to be in master 14:30:45 ok, that's a lot to process 14:30:56 will look at this today 14:31:27 i wonder if we can roll back a requirments change and just have the cinder functional tests run 14:32:05 this is probably independent of requirements change 14:32:28 and looking at the barbican repo, looks like theyh merged a shitload of stuff since RC1 14:35:32 ok 14:35:39 any good news? any at all? 14:36:16 i got a ticket to the Miami Grand Prix!! 14:36:18 we may need to ask them to run some cinder tests in their gate 14:36:24 https://review.opendev.org/c/openstack/barbican/+/937752?tab=change-view-tab-header-zuul-results-summary 14:36:26 simondodsley: nice! 14:36:48 rosmaita: ok, im happy to reach out to them today 14:38:15 their latest run of barbican-tempest-plugin-simple-crypto is showing the internal server errors that i think are responsible for us not being able to get a response from the key manager in our cinder-tempest-plugin tests 14:38:24 https://zuul.opendev.org/t/openstack/build/3f511fa396694e64a565a9ca63feb8eb 14:39:47 ha! that's on this patch: https://review.opendev.org/c/openstack/barbican/+/948391 14:40:05 looks like gibi has noticed that the nova job is having issues 14:41:05 ok, so they may be aware of the problem 14:41:14 ill followup to be sure 14:41:25 thanks for all of the investigation 14:42:53 ok, if you follow up on that one, i will continue to look at the cinder-plugin-ceph-tempest job 14:43:05 deal 14:44:50 #topic open discussion 14:45:12 as an aside - Red Hat team - enjoy your trip to Brno 14:45:52 wow, word really gets around ... thanks! 14:46:20 i have kindly provided y'all with a nice new array to play with 14:46:32 oh dang! new toys! 14:47:31 btw, bobcat was tagged EOL and the branch will be deleted sometime within the next week or so 14:48:05 ok, nice work on all of that 14:50:04 Regarding patch- https://review.opendev.org/c/openstack/cinder/+/925450 I've updated the release notes mentioning removal of config option. Let me know if it looks okay. Thankyou! 14:50:43 oy, we need to get these gate issues sorted 14:51:22 VrindaDhakad: thanks, ive added it to the review request list as well 14:53:02 For issue https://review.opendev.org/c/openstack/cinder/+/901318 14:53:14 agilica and I are from Hitachi and working on Hitachi driver. For this issue, we also believe it will cause a bug. We’re working with Japan and Golden Week has prevented us from getting clarity on whether or not it requires fixing (ie is the feature being used upstream yet), so we need to rescind the review request for now.  Hopefully we will have clarity next week. 14:54:45 agamboa: that's completely fine, you can mark it as work-in-progress if you'd like, or just leave brian's -1 as it is and update it once you know how to proceed 14:55:56 sorry being late, I joined 15 minutes ago. The PR from Storpool export support of iSCSI needs review/ This has being already discussed here couple of months ago.. and updated as per discussion. https://review.opendev.org/c/openstack/cinder/+/847536 14:56:16 agamboa: if you click on the three vertical dots way over on the top right of the gerrit review, you get an option to "Mark as work in progress" 14:56:51 i think you have to be the patch owner, though, or that option doesn't appear 14:57:12 thanks! will mark it as in progress or update 14:57:42 kpdev: ack, added to the list 14:58:18 thanks, its already added at line 7 14:59:23 kpdev: ok, i see 15:00:35 kpdev: will address gate issues first and come back for those after 15:00:45 ok, ack. 15:00:51 anything else? last call 15:01:35 #endmeeing 15:02:03 hmm 15:02:06 #endmeeting