15:00:07 #startmeeting manila 15:00:07 Meeting started Thu May 29 15:00:07 2025 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:07 The meeting name has been set to 'manila' 15:00:28 o/ 15:00:43 courtesy ping: dviroel vhari carthaca msaravan Sai ashrodri gireesh 15:00:55 o/ 15:02:00 :) 15:03:45 o/ hello zorillas 15:03:58 our meeting agenda for today: 15:04:24 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:04:44 so this is still the bugsquash week 15:04:48 we'll get to that in a bit 15:04:55 but first 15:04:57 #topic Announcements 15:05:01 Schedule and Deadlines 15:05:07 #link https://releases.openstack.org/flamingo/schedule.html (Flamingo Schedule) 15:05:46 we're now two weeks away from our hackathon, which in the initial idea of the PTG targeted functional tests for the python-manilaclient repo 15:06:06 targeting OSC, I mean 15:06:12 we wanted to do that before we remove the manilaclient 15:06:28 hi 15:06:38 * carloss o/ 15:06:50 do you have any concerns with regards to the hackathon date? as in: are you okay with it being in two weeks from now? 15:08:32 sounds good; however we may need a bunch of pre-work to determine the gaps 15:09:17 gouthamr: yep, I can work on that 15:09:27 wait, you said two weeks from now 15:09:42 but, on the schedule it is R-13 15:09:46 Jun 30 - Jul 04 15:09:54 argh, yes 15:10:00 something wrong with my eyes today 15:10:03 gouthamr: thanks 15:10:28 next deadline is spec freeze, 3 weeks from now 15:11:03 my bad 15:12:02 that's all I had for $topic 15:12:19 do you have any other announcements you'd like to share with the zorillas today? 15:13:11 not an announcement, per se.. but a word on availability - mine is going to be iffy over the next couple of months.. i'd probably engage more async than usual 15:13:45 hoping to still keep up with reviews, and will need some notice to have sync conversations 15:16:36 gouthamr: ack, thanks for the heads-up 15:17:08 and also for offering time in case we need :) 15:17:53 let's switch to Bug triaging, and then we can talk bugsquash 15:18:05 #topic Bug Triage 15:18:14 #link https://etherpad.opendev.org/p/manila-bug-triage-pad-new (Bug triage etherpad) 15:18:21 a bunch of new bugs 15:19:12 #link https://bugs.launchpad.net/manila/+bug/2111813 ([NetApp] enable aes-encryption for cifs) 15:19:33 we seem to have a fix proposed: 15:19:42 #link https://review.opendev.org/c/openstack/manila/+/951087 ([NetApp] Enable aes-encryption for cifs) 15:19:47 yes, assigned to self 15:19:55 kpdev: thank you 15:20:17 kpdev: is it breaking any workflows? 15:20:40 its was fix of some error during cifs share creation 15:20:49 mentioned in commit 15:20:55 yep 15:21:11 I think we can make it medium importance 15:21:13 is this really a bug? 15:21:28 sounds like a missing feature.. what's failing without this? 15:22:06 kind of bug or small feature. was getting error during share creation KRB5KDC_ERR_ETYPE_NOSUPP.. mentioned in commit 15:22:16 but PR is small, I created bug and fixed via it. 15:22:28 sounds fine, some bugs are really RFEs 15:22:44 but, did something change in ONTAP to require it? 15:22:44 also.. manila-grenade-skip-level-always still failing for recheck of all patches I retried since yesterday. 15:23:35 > also.. manila-grenade-skip-level-always still failing for recheck of all patches I retried since yesterday. 15:23:35 yep, that's one of the topics I wanted to mention, as I also noticed it when I was looking at changes from the bugsquash and rebasing them 15:24:40 https://zuul.opendev.org/t/openstack/build/f9beac99a25043229c93ad2605d85e9d/log/job-output.txt#15713-15736 15:24:55 ^ i haven't checked the chatter to see if neutron folks know about this 15:28:49 https://zuul.opendev.org/t/openstack/build/f9beac99a25043229c93ad2605d85e9d/log/controller/logs/screen-neutron-api.txt looks fine to me 15:29:08 yes 15:29:08 >but, did something change in ONTAP to require it? ... No, nothing changed. it was downstreamed since last 2-3 years, upstreaming it now. 15:30:06 kpdev: sounds like some ONTAP configuration in your cloud requires this 15:31:32 ++ - maybe we should tag as an RFE 15:31:33 Sai/gireesh: please take a look.. i'd be concerned if this is not available/expected to be turned on my default.. because i've not seen an issue creating cifs shares/access rules without AES encryption enabled.. 15:32:03 I dont see any special config did for this feature. but yes netapp internal testing and review would be better to confirm. 15:32:21 ++ 15:32:23 https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Can_we_enable_AES_encryption_on_CIFS_server 15:32:34 I will dissolve with Gireesh on this. Will update him. Thanks. 15:32:47 Discuss* 15:33:00 Sai: thanks 15:33:20 also this: https://docs.netapp.com/us-en/ontap/smb-admin/enable-disable-aes-encryption-kerberos-task.html 15:34:05 "Whether AES encryption is enabled by default and whether you have the option to specify encryption types depends on your ONTAP version." - maybe the driver will need to do this based on the ONTAP versions 15:35:16 also, the option is changing with newer versions 15:35:43 with newer versions of ONTAP, you can specify the encryption type 15:35:45 hmm. so this will be 9.11.1 and earlier 15:36:20 I will update fix to consider versions 15:37:12 kpdev++ 15:38:07 thanks 15:38:54 I think we have time for another untriaged bug 15:39:06 #link https://bugs.launchpad.net/manila/+bug/2111905 (NetApp - Need to provide the option to override the “is-shared” field value for qos policy created during share creation) 15:40:05 sounds like an RFE 15:40:24 yeah 15:40:33 i see gireesh already added himself to assignee 15:40:38 likely low prio 15:41:05 +1 15:41:13 Sai: are you aware if gireesh is planning to work on this? 15:41:32 yes, these are kind of RFE, one of the customer is requesting for these. We will work on these 15:42:23 gireesh: ack, thank you! 15:43:17 we have another untriaged bug that seems a bit high prio 15:43:30 * carloss is hijacking all the time of bugsquash to bug triaging :/ 15:43:44 this is the last one I'll bring up today, I promise 15:43:53 #link #link https://bugs.launchpad.net/manila/+bug/2111918 ([Manila][NetApp][REST]Share deletion is failing at NetApp volume creation saying: Field "retention_period" cannot be set in this operation") 15:44:15 Sai thank for reporting this bug! 15:44:34 I've set kpdev as an assignee mostly for an investigation reason, as I think he might have the most context on this change 15:44:41 Np, Thank you carloss !! 15:44:42 apparently, share deletion is failing in REST 15:44:52 kpdev: could you please take a look? 15:45:02 this might be a regression 15:45:17 if it is, we'll need to have an owner to this fix 15:45:23 No, I had added fix there based on documentation. but this time we need correct soluton from netapp 15:45:40 since the field I mentioned no longer present in REST documentation. 15:46:11 so need to find another way to provide retention_period. NetApp needs to update on bug how to do it and then I will raise PR. 15:46:17 so might be something varying from one ontap version to another? 15:46:32 so, this is one of those issues the NetApp CI would easily catch :/ 15:47:08 kpdev: Meanwhile, can you please update the documentation you referred earlier in the bug. Thanks 15:47:13 not sure about version, we are not using REST yet. 15:47:24 retention_period need to set in patch call not in post call. Once vserver is created after that we have to set this parameter - kpdev 15:47:32 The documentation redirect to new pages now, I had shared with you earlier 15:48:03 @gireesh: got it, can anyone from netapp update that on bug ? 15:48:26 ok, I'll do this 15:48:38 ack, thank you 15:48:56 please update the bug as well 15:49:54 alright, let's move to the next topic 15:50:09 #topic Bugsquash - Review-a-thon 15:50:14 https://etherpad.opendev.org/p/manila-flamingo-m1-bugsquash (Flamingo m-1 bugsquash) 15:50:19 #link https://etherpad.opendev.org/p/manila-flamingo-m1-bugsquash (Flamingo m-1 bugsquash) 15:50:58 so we had the kick-off call on Tuesday and I am posting the video to the YouTube channel 15:51:39 we've got review assignments, so I'd like to ask reviewers to take a look at the changes 15:51:57 we have the CI situation at the moment, but there are some easy wins for us that are not relying on the CI being working rn 15:52:06 I'm talking about documentation bugs 15:53:00 #link https://review.opendev.org/c/openstack/manila/+/945891 (Add mount snapshot support to user guide) 15:53:18 #link https://review.opendev.org/c/openstack/manila/+/934462 (Updates the share extend and shrink documentation) 15:53:39 #link https://review.opendev.org/c/openstack/manila/+/946505 (use os cli for shared-file-crud-share.rst) 15:54:11 two of these already have +2s/+1 from cores 15:54:18 can I get more eyes on them? 15:54:35 yep 15:54:37 i will check this 15:54:45 gouthamr haixin thank you very much! 15:55:01 now for the other changes, which are being impacted by the CI situation 15:55:24 I've looked at the job history and apparently it is failing for a while 15:56:02 I tried correlating to the changes that were merged to openstack/neutron on a given date but these don't seem to be a problem 15:56:16 and as gouthamr also mentioned, neutron API seems to be working just fine 15:57:27 I posted some review comments to a bunch of changes, some are being resolved, but CI won't let these changes merges even if we have agreement from reviewers 15:57:35 I'll investigate the failures 15:57:39 in the meantime 15:59:23 not a very good timing for the CI being broken 15:59:31 but I think we are getting reviews in some changes 15:59:58 and when CI issues are fixed, we can go ahead and merge the changes that are blocked by it 16:00:02 questions? suggestions? 16:01:05 alright, let's wrap up 16:01:10 and get back to #openstack-manila 16:01:15 thanks for participating 16:01:27 and have a great day 16:01:29 #endmeeting