Thursday, 2023-07-20

sairamhi05:31
pdeore#startmeeting glance13:59
opendevmeetMeeting started Thu Jul 20 13:59:23 2023 UTC and is due to finish in 60 minutes.  The chair is pdeore. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
opendevmeetThe meeting name has been set to 'glance'13:59
pdeore#topic roll call13:59
pdeore#link https://etherpad.openstack.org/p/glance-team-meeting-agenda13:59
pdeoreo/13:59
mrjoshio/13:59
pdeoreabhishek is not going to attend due to some emergency 14:00
pdeorelet's wait for others to join14:00
croelandto/14:01
pdeorelet's start14:01
pdeore#topic release/periodic jobs updates14:01
pdeorewe have tagged m2 last week, it was got delayed due to random gate failures but finally we could do it as decided.. 14:02
pdeoreM3 is 6 weeks from now14:02
pdeoreand our targets for m3 would be new location apis, sorting locations based on store weight & having missing cli support for all image & metadef apis in OSC14:02
pdeorepatches are up for review for all these ^ which we are going to see in next topics14:03
pdeorePeriodic jobs are all green except intermittent TIME_OUTs on fips jobs14:03
pdeoremoving to next14:03
pdeore#topic Important Reviews14:03
pdeoreAs said earlier, we have some important patches up for review, 14:04
pdeorebut there are some random CI failures for almost all of these patches14:04
pdeoremostly some cinder related different tempest tests are failing & time outs, not sure how to handle this :/14:04
croelandtThe good way to do this would be to understand why CIs are always failing with issues unrelated to the patches themselves14:05
croelandtbut it's hard work, it takes time, and has no direct business value14:05
dansmithsorry, I'm here14:05
pdeoreyeah14:05
dansmithfixing CI has no direct business value?14:06
dansmithas someone who spends a lot of time fixing CI, that attitude irks me :(14:06
croelandtwell it has value14:06
croelandtit would help us merge patches faster14:06
croelandttest features etc.14:06
dansmithand the tests aren't usually the buggy thing, FWIW14:06
croelandtbut I think if we were to go to all our companies and say "hey, could we invest $$$ to not recheck all the time hoping for the best"14:06
croelandtthey would not be happy14:06
croelandtbut I might be mistaken!14:07
croelandt(I hope so)14:07
dansmithwe don't fix CI to avoid having to recheck, we should be fixing it to either fix the actual product, or fix our ability to show that the product works instead of letting the customers tell us if it doesn't14:07
croelandtyes14:08
croelandtbut as a dev, I feel a bit powerless when trying to merge a patch14:08
croelandtI feel like it's timing out and... not much I can do about it, so I'll click the button14:08
dansmithyou are power*ful*.. go figure out why it's failing, try to fix it.. you'll learn more about the components involved in the process14:08
croelandtwell, when it's randomly timing out, it's quite a tough process to even know whether you fixed it14:10
dansmithanyway, we should move on14:10
pdeorebut these time outs are also for different jobs everytime :/ 14:10
pdeore:)14:10
dansmithpdeore: which shows that they're all related14:10
dansmithpdeore: yesterday your location patch was failing for reasons related to your code14:10
dansmithlooks like you've updated it?14:10
pdeoreyeah i have updated it14:10
croelandtdansmith: now I'm gonna end up bothering you next time there is a failure so you can walk me through your debugging process :)14:11
dansmithcroelandt: as long as you're putting forth a real effort and not asking me for an answer, that's fine.. there are lots of people to lean on in that regard14:11
croelandtgood, maybe I'm not that powerless after all \o/14:12
croelandtbut anyway, I was not implying it's useless to work on the CI14:12
croelandtjust to be clear14:12
dansmithyou pretty much said that exactly14:12
dansmithlet's move on and I can continue being annoyed after the meeting in -glance14:12
croelandtok so it did not come across properly, sorry about that14:12
pdeore:D14:13
croelandtpdeore: you have the floor :)14:13
pdeoreok, so as per the discussion, I have separated out new location api changes in multiple patches and updated as per the suggestions on implemtation part, 14:13
pdeore#link https://review.opendev.org/c/openstack/glance/+/886749/8   - Location Import task flow14:13
pdeore#link https://review.opendev.org/c/openstack/glance/+/881940/22 - Add Location API core changes14:13
pdeore#link https://review.opendev.org/c/openstack/glance/+/886947/2   - Fucntional tests for new Add location api14:13
pdeore#link https://review.opendev.org/c/openstack/glance/+/882498/14 - New Get location API14:13
pdeoreI will submit the documentation + api-reference  & version bump patches by tomorrow EOD or Monday 14:14
pdeoremoving to next 14:15
pdeore#topic OSC & SDK side reviews (mrjoshi)14:15
pdeoremrjoshi wants to highlight some OSC & sdk patches which needs attention14:15
pdeoremrjoshi, ^14:15
mrjoshiThere are few patches on the openstack SDK and Openstackclient which needs review14:16
mrjoshi#link https://review.opendev.org/c/openstack/python-openstackclient/+/878631 - Add cache commands14:17
mrjoshi#link https://review.opendev.org/c/openstack/openstacksdk/+/881939 - Adding Support for image upload14:17
mrjoshi#link https://review.opendev.org/c/openstack/python-openstackclient/+/882086 - Adding ``image delete --store`` and ``image import info`` commands14:17
pdeoremrjoshi, there are some metadef api related patches as well, right?14:18
mrjoshicroelandt, you have a comment regarding raising exception on https://review.opendev.org/c/openstack/python-openstackclient/+/882086 ?14:19
croelandthm14:20
croelandtyes, I was wondering if that was the only way of doing this14:20
croelandtbecause error messages can change in the future14:21
croelandtand this might end up breaking14:21
croelandtcan't we check whether multi store is enabled some other way?14:21
mrjoshipdeore, yes #link https://review.opendev.org/c/openstack/openstacksdk/+/858350 , this patch has some review comments on which I'm working and will upload the updated patch by tomorrow14:22
pdeoremrjoshi, ok14:22
mrjoshicroelandt, I'll look into it if there's any other way14:24
croelandtmaybe ask Stephen about that14:25
mrjoshibut afaik that's how they are doing it in osc , but I'll still confirm it once again14:25
mrjoshiack14:25
pdeoremrjoshi, cool, anything else you want to highlight ?14:26
pdeoreshall we move to open discussions ?14:27
mrjoshiyes, there is one question, do we need the output format similar to glanceclient for all the commands14:28
croelandtI think it should mostly be consistent with other OSC commands14:29
pdeorenot sure but I think according to osc rules we have to showcase14:29
croelandtis there a particular example you had in mind?14:29
mrjoshiyes14:29
mrjoshihttps://review.opendev.org/c/openstack/python-openstackclient/+/88349414:30
mrjoshiSo the output for stores-info in osc is displayed in a list-format 14:30
croelandtyeah I think Stephen is right14:31
croelandtwe should aim for consistency inside OSC14:31
croelandtnot between OSC and glanceclient14:31
mrjoshiok 14:31
pdeore+114:31
croelandtOSC is not going to be a drop-in replacement for glanceclient14:31
croelandtwell, for interactive use, it will be14:31
croelandtbut for scripting, no, basically14:31
mrjoshiok14:33
pdeoreok, moving ahead14:34
pdeore#topic Open Discussions14:34
dansmithpdeore: can you explain why the changes you made to your second patch affected the tempest run?14:35
dansmithAFAICT, nothing should be plumbed through the external API until the last patch,14:35
dansmithyet tempest tests were failing and you made some changes so that they didnt14:35
pdeoredansmith, honestly I also not sure14:36
dansmith... seriously?14:36
dansmithbecause I'm thinking if any of your code is actually being called in the current flow,14:36
dansmithbut is starting a task or something, then any of your new timeouts or new behavior could potentially be related to this code14:37
dansmithso how do you justify the changes you made? Looks like you removed something from the response body and maybe added or changed a result code to 202?14:37
dansmithpotentially the latter might make a client library stop (or start) waiting for something I guess, but that could certainly affect the overall thing14:38
pdeoreyeah earlier as decided i was returning the updated location url & the validation data since the update location operation was sync but after moving to async, we can not return the same, hence 202 14:40
dansmithright, but nothing should be calling this code yet, other than unit/functional tests, so I don't see how those changes would have fixed the failures we saw before14:40
pdeoredansmith, need to verify it again, may be earlier failure was not related to my changes14:42
dansmithkinda hard to imagine they weren't related since they all seemed to involve image ops, but... okay14:43
dansmith... BasicOperationsImagesTest14:43
pdeorewill check it again ..14:45
pdeoreanyone has anything else to discuss?14:47
* croelandt has nothing14:48
mrjoshinothing from me14:48
pdeoreok, then let's conclude for today !14:49
pdeoreThanks everyone for joining!!14:49
pdeore#endmeeting14:49
opendevmeetMeeting ended Thu Jul 20 14:49:44 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
opendevmeetMinutes:        https://meetings.opendev.org/meetings/glance/2023/glance.2023-07-20-13.59.html14:49
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/glance/2023/glance.2023-07-20-13.59.txt14:49
opendevmeetLog:            https://meetings.opendev.org/meetings/glance/2023/glance.2023-07-20-13.59.log.html14:49

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!