Tuesday, 2020-08-11

dansmithabhishekk: for tomorrow, I think your test_reload() test is racy and some child processes get confused which causes it to hit "no new log file created" and when that happens, the cleanup in the base test also waits forever on the api server child, which is the cause of that TIMED_OUT functional job00:00
dansmithmaybe we can discuss in the morning because I'm having a hard time understanding how it's working at all actually...00:00
*** gyee has quit IRC02:11
*** rcernin has quit IRC02:37
*** rcernin has joined #openstack-glance02:48
*** irclogbot_2 has quit IRC03:05
*** irclogbot_2 has joined #openstack-glance03:07
*** Liang__ has joined #openstack-glance03:28
*** Liang__ has quit IRC03:40
*** Liang__ has joined #openstack-glance03:41
*** ratailor has joined #openstack-glance03:46
*** rcernin has quit IRC03:54
*** Liang__ has quit IRC04:07
*** Liang__ has joined #openstack-glance04:09
*** rcernin has joined #openstack-glance04:21
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-glance04:33
*** ratailor has quit IRC04:43
*** ratailor has joined #openstack-glance04:43
*** m75abrams has joined #openstack-glance04:56
*** udesale has joined #openstack-glance05:29
*** belmoreira has joined #openstack-glance05:56
abhishekkdansmith, ack05:56
*** belmoreira has quit IRC05:58
*** belmoreira has joined #openstack-glance06:14
*** nikparasyr has joined #openstack-glance06:31
*** udesale has quit IRC06:51
*** udesale has joined #openstack-glance06:52
*** priteau has joined #openstack-glance08:26
*** priteau has quit IRC08:42
*** priteau has joined #openstack-glance08:58
*** rcernin has quit IRC09:11
*** rcernin has joined #openstack-glance09:33
*** tkajinam has quit IRC09:36
* abhishekk be back on 1400 UTC09:48
*** udesale_ has joined #openstack-glance09:49
*** udesale has quit IRC09:52
*** rcernin has quit IRC09:56
*** priteau has quit IRC10:11
*** Liang__ has quit IRC10:31
*** k_mouza has joined #openstack-glance11:29
*** k_mouza has quit IRC11:30
*** rcernin has joined #openstack-glance11:31
*** k_mouza has joined #openstack-glance11:33
*** ratailor has quit IRC12:03
*** k_mouza has quit IRC12:11
*** Luzi has joined #openstack-glance12:55
*** Luzi has quit IRC13:00
openstackgerritMerged openstack/glance master: Add image_delete_property_atomic() helper  https://review.opendev.org/74359613:10
abhishekkdansmith, hey13:45
dansmithhey13:45
abhishekkI saw your ping early morning13:45
dansmithso, I have a bunch of data and have tried a bunch of things, but I have yet to actually come up with a plan13:45
abhishekkok13:45
dansmithevery time I see this manifest,13:45
dansmithit is in functional cleanup() waiting for the api worker master process to exit,13:46
dansmithbut that child shows in the log no intent on shutting down, like it has not received the signal to exit13:46
dansmithrarely if I kill it, I find that your test was about to report failure for one of the SIGHUP operations,13:47
abhishekkok, so why not it happens consistently?13:47
dansmithbut often it reports success and it was just the functional stuff that was hanging, but only ever on your test13:47
dansmithwell, the first thing is, I don't see where the functional stuff *ever* tries to stop the children13:48
dansmithso I must be missing something13:48
abhishekkhmm13:48
abhishekkthat should be in actual wsgi module13:49
dansmithno, I mean the functional base class has self.process_pid of the api worker it starteed,13:50
dansmithand it looks like when stop() is called it will just waitpid() on that worker,13:50
dansmithI don't see where stop_kill ever gets set True for the regular case13:50
abhishekkright13:53
dansmithso when would we expect the api child to stop?13:53
abhishekkso in actual scenario, it should stop as soon as the task that child is processing is completed13:55
abhishekksomewhere in wait_for_fork method13:56
dansmithwhen we start cmd.api, it will run until it's told to stop13:56
dansmithif we waitpid() on it, we won't return until that pid decides to exist, which is usually because we have sent it a signal13:57
dansmithbut I don't see where we  ever do that (stop_kill=False by default, AFAICT)13:57
abhishekkyes, it is false13:57
dansmithso we won't send the master a signal when we stop(),13:57
dansmithso stop() will just hang until the process decides to exit.. what triggers it to know when to exit?13:58
abhishekknothing atm13:58
dansmithso why do we ever not hang forever there?13:59
dansmiththat's what I'm trying to understand13:59
dansmithfor every functional test that starts a worker, and then calls stop() in cleanup, why do we *ever* not hang?13:59
*** smcginnis has quit IRC14:01
abhishekkyeah, that's what I am not able to understand as well14:01
dansmithokay14:02
dansmithso, the other abnormality I see,14:02
dansmithis that when this happens, the tail of the log file of the worker will show the two worker PIDs, and those pids are alive under the master,14:03
dansmithbut when stop() runs, I've modified it to recursively walk the children of our master process, it finds two other children with (likely) older PIDs to kill14:04
*** smcginnis has joined #openstack-glance14:05
dansmithso I'm worried that the wsgi server's handling of recycling the children might be leaky and there are a couple of zombies left around from a previous HUP,14:05
dansmithand _that_ is why your reload test hangs sometimes when others don't,14:05
dansmithbecause the master process doesn't exit when asked because of those older children hanging around14:06
dansmithbut I'm still working to try to gather more data on that14:06
abhishekkso this you are talking about actual sighup or functional test stuff?14:06
dansmiththe actual sighup handling in the wsgi server, only just triggered by your functional test14:06
dansmithbut causing the hang we see14:07
dansmithanyway, I want to file a bug for this to track this stuff.. there's not one already open for it I assume right?14:07
dansmithI'm not sure how long the functional tests have been hitting TIMED_OUT,14:07
dansmithbut it's as long as I've been around, so a couple of months14:07
*** rcernin has quit IRC14:08
abhishekkthere is no bug at the moment for timeout, but this functional timeout was since this cycle as the test was disabled earlier14:08
dansmithoh was it? why?14:10
abhishekkthere was some issue with py3 earlier14:11
*** m75abrams has quit IRC14:11
dansmithokay14:13
dansmithhttps://bugs.launchpad.net/glance/+bug/189119014:14
openstackLaunchpad bug 1891190 in Glance "test_reload() functional test causes hang and jobs TIMED_OUT" [Undecided,New]14:14
abhishekkalso when this test was added, there was no reload method in functional/__init__.py14:15
abhishekkit was added later during when someone added windows support for glance14:15
dansmithokay14:16
dansmithnot sure how that works (on the Posix one) either14:16
dansmithas part of my local testing, I've added this to the functional base:14:16
dansmith+            self.addCleanup(self.cleanup, force=True)14:16
dansmithwhich tells cleanup to set stop_kill=True before calling stop()14:17
abhishekkok14:17
dansmithclearly I'm still missing where this happens normally, but that is more explicit anyway14:17
dansmiththere's really no reason we should ever call waitpid() if we are unsure if the signal has been sent14:17
dansmithso unless we find it... :)14:17
abhishekkyeah, will have a neat look as well14:18
*** rcernin has joined #openstack-glance14:18
abhishekkdansmith, IMO we should skip it again until we found the way to get it worked14:21
dansmithI'm a bit conflicted, because skipping tests that are flaky is a good way to keep them flaky and keep them from getting attention14:22
dansmithbut...it's failing a lot, so idk14:22
abhishekkthis will really cause problem for us during the milestone release when gate is heavily loaded and waiting time will be much higher14:23
dansmithyup14:23
dansmithAFAICT, that other spurious test fail has been squashed, but let me re-query for it and see if it has shown up at all14:23
abhishekkack14:24
*** rcernin has quit IRC14:24
*** rcernin has joined #openstack-glance14:27
*** rcernin has quit IRC14:31
dansmithabhishekk: I see some failures since the fix landed for the copy revert lifecycle, but *only* on periodic tests, which seems weird14:39
abhishekklooking14:40
abhishekkI can see two failures as well14:42
dansmithin trying to track down this test_reload thing, I have run functional like thousands of times and have not hit the copy revert lifecycle thing ...14:43
abhishekklets wait for couple of run of periodic cycles14:45
dansmithit seems massively better, if nothing else14:46
abhishekkyes14:46
abhishekksmcginnis, jokke, rosmaita please look when you have time, https://review.opendev.org/74540714:53
rosmaitaack14:53
smcginnisDone14:58
rosmaitawhy don't those files show up in https://b1bdaec33567f033c580-b85c91a90386bf84f78798fbdb65380c.ssl.cf1.rackcdn.com/745407/2/check/tempest-full-py3/0c373be/controller/logs/etc/glance/ ? is it something about how devstack installs glance_store?14:59
*** brtknr has left #openstack-glance15:00
abhishekksmcginnis, thank you15:01
abhishekkrosmaita, yes it is15:04
dansmithrosmaita: I expect something is going on there because we install it from git and the uninstall it right after15:04
rosmaitaok, i didn't want to test locally, so was looking for a shortcut15:04
*** nikparasyr has left #openstack-glance15:04
abhishekkI also didn't tested locally, but verified it by cloning glance_store and running setup.py install15:05
abhishekkit is copying those files in /etc/glance15:06
rosmaitaabhishekk: i didn't doubt you for a minute!15:20
abhishekkrosmaita, no, I am not saying that, I am saying that after this change I have also not check by installing devstack that it is copying files to /etc/glance15:21
rosmaitagotcha ... there may need to be some work on the devstack side if that tempest-full-py3 run is typical of a devstack install15:23
abhishekkack15:24
*** belmoreira has quit IRC15:25
* abhishekk going for dinner break15:33
*** rcernin has joined #openstack-glance15:40
*** rcernin has quit IRC15:44
* abhishekk back from dinner16:11
dansmithwell, I have had my "find and kill everything on stop" change running for two hours now without a failure, which is as long as I think I've seen it go16:15
dansmithso I still don't have a cause, and suspect something is actually not right with the wsgi thing, but this seems like legit care to have in the test base anyway16:16
dansmithwe're clearly leaking processes:16:18
dansmith% pgrep -f cmd.api | wc -l16:18
dansmith3616:18
dansmiththose leaked processes are re-parented to init, so they must be orphaned by a master that lost track of them i think16:20
abhishekksounds like processes are never killed in tests as pointed by you16:27
dansmithit's more than that16:29
dansmithbecause I'm killing the whole process tree under our api master process16:29
dansmithand afaict, we only leak processes when we run test_reload(),16:30
dansmithwhich I suspect means we're losing track of the workers we're starting in the sighup16:30
abhishekkmay be in teardown we should see how much workers are there in pre_pid and post_pid dict and kill them in all?16:31
openstackgerritMerged openstack/glance master: Heartbeat the actual work of the task  https://review.opendev.org/74342616:32
dansmithI'm effectively doing that in cleanup() and not finding any extras to kill, yet ps shows an ever-growing number of cmd.api workers running16:32
dansmithafter stopping the tests:16:33
dansmith% pgrep -f cmd.api | wc -l16:33
dansmith3116:33
dansmiththe16:33
openstackgerritMerged openstack/glance master: Update task message during import  https://review.opendev.org/74342716:34
*** udesale_ has quit IRC16:34
abhishekkstrange, even after stopping the test workers are increasing16:35
dansmithyeah16:36
dansmithwell, not increasing after stop,16:36
dansmithjust never going away16:36
dansmithbecause they're re-parented to init because their master has died16:36
abhishekkok16:36
openstackgerritMerged openstack/glance_store master: Copy data files to glance upon installation  https://review.opendev.org/74540716:37
openstackgerritDan Smith proposed openstack/glance master: Increase aggression in functional base API worker management  https://review.opendev.org/74570816:41
dansmithabhishekk: ^ this is my test change, but am going to write another reload check to see if I can catch the leak16:41
abhishekkdansmith, ack, looking16:42
dansmithabhishekk: why are you shelling out to call /bin/kill by the way?16:42
dansmithbecause that creates children and isn't necessary to send signals of course16:42
abhishekkdansmith, could you please point out the location, it was written may be 4 years before16:43
dansmithabhishekk: like this: https://github.com/openstack/glance/blob/master/glance/tests/functional/test_reload.py#L140-L14116:44
abhishekkdansmith, at that time I thought this was easy way to do it16:46
dansmithokay, maybe I'll change it to use signal directly and see if that changes behavior at all16:46
*** zzzeek has quit IRC16:47
abhishekkack16:47
*** k_mouza has joined #openstack-glance17:04
*** k_mouza has quit IRC17:09
dansmithugh, that patch failed the copy revert test :/17:15
abhishekk:(17:18
abhishekkrosmaita, you were right17:21
abhishekkwhen devstack installs glance_store (which I tricked as we don't have new version of glance_store released) it copies those data files in /usr/local/etc/glance/ path and not to /etc/glance17:22
abhishekkdansmith, ^^17:23
dansmithexpected by default I think,17:23
dansmithnot sure why nova and glance behave differently in devstack17:23
dansmithgmann: can you help?17:23
abhishekkthen I guess we need to add that path in here https://github.com/openstack/glance_store/blob/master/etc/glance/rootwrap.conf#L717:25
abhishekk otherwise image will never be created if cinder backend is used in devstack17:25
dansmithabhishekk: is glance_store being installed from git or pypi?17:25
abhishekki have verified that os-brick also copies data files to /usr/local/etc/os-brick17:26
abhishekkdansmith, from git17:26
dansmithabhishekk: are you installing with setup_develop?17:26
abhishekkdansmith, by me you mean devstack, then yes17:27
dansmithokay just looking at differences17:27
abhishekkand if in data_files if I begin with /etc/glance then it copies those files in /etc/glance17:30
dansmithright, but you see that other projects don't do that because it breaks portable install17:30
abhishekkyes, right17:32
dansmithabhishekk: looks like in the nova case at least, inc/rootwrap is copying the files to /etc/nova17:40
dansmithwe do the same for paste.ini,17:40
dansmithand we just write the config directly17:40
dansmithso I think that's the magic17:40
dansmithhttps://zuul.opendev.org/t/openstack/build/f13715b6d142467bb1342fc001c939b7/log/controller/logs/devstacklog.txt#707017:40
dansmiththe thing we call is: configure_rootwrap nova17:41
dansmithso maybe configure_rootwrap glance_store ?17:41
abhishekkohh17:41
abhishekkimo it is different behavior for 3rd party libraries17:44
dansmithwhy?17:45
abhishekkas I said os-brick also copies data files to /usr/local/etc/os-brick17:45
dansmithnova and glance do too right?17:45
abhishekkmay be gmann will help us17:45
abhishekknova, cinder, glance do copy to /etc/* respective folder17:46
dansmithno, devstack does that17:47
dansmiththe package itself should copy them, to /usr/local also17:47
dansmithif lib/glance is installing glance_store, then it should do the same for the glance_store configs17:48
dansmith(or configure things to look at /usr/local if possible)17:49
abhishekkeven if I manually clone glance_store now and run setup.py install it copies those data files to /usr/local/glance directory17:52
dansmithright17:52
dansmithwhich devstack can copy to /etc/glance (or wherever it's needed) right?17:52
abhishekki think it should, but it doesn't17:53
dansmithyou have to _make_ it do that :)17:53
abhishekk:D17:54
abhishekkglance_store is using setup_dev_lib for installing17:56
dansmithright, same for nova18:00
dansmiththen we run this: https://github.com/openstack/devstack/blob/master/lib/nova#L23818:00
dansmithwhich copies things to /etc/nova/rootwrap18:00
abhishekklooking18:02
abhishekkmay be I need call same function in devstack cinder support patch18:04
dansmithabhishekk: [10:41:07]  <dansmith>so maybe configure_rootwrap glance_store ?18:04
dansmith:)18:04
abhishekkohh, I missed that :D18:04
abhishekkAhh, I disconnected 5-10 minutes because of VPN issue in between :D18:05
gmannabhishekk: dansmith yeah you need to write the copy things in devstack to whatever location you want to  /etc/<service>18:07
abhishekkdansmith, gmann last doubt18:08
gmannyou can do in job also18:08
abhishekkglance_store is library18:08
gmannor devstack18:08
dansmithack, I was thinking devstack should be doing the setup.py install with --prefix , but yeah looks like devstack copies manually18:08
gmannyeah18:08
abhishekkso if I avoid cloning of glance_store and allowed pip to install it then configure_rootwrap glance_store will not found glance_store repo in my local env18:08
dansmithabhishekk: yeah, so maybe don't use configure_rootwrap and copy from /usr/local/etc/glance_store,18:09
dansmithor make configure_rootwrap_from_installed() or something18:09
abhishekkyeah18:09
abhishekkwill do it :D18:10
dansmithabhishekk: how does it work for os_brick? maybe you can include the glance_store rootwrap stuff from /usr/local18:12
dansmithsmcginnis: rosmaita ^18:12
abhishekkdansmith, I haven't found os-brick rootwrap reference in cinder.conf18:13
dansmithyeah that's what I'm wondering18:13
dansmithanyway, copying will make it included in the log dump, which is good too18:13
abhishekk+1 I will copy it18:14
smcginniscinder and nova have had to maintain duplicate rootwrap.conf files. We run nearly everything through privsep now, so no longer need to sync those changes.18:14
smcginnisIt caused a big problem with needing to lock step changes between projects.18:14
dansmithsmcginnis:18:16
dansmithsmcginnis: "we" being "brick" in this case?18:16
dansmithmeaning, brick uses privsep?18:16
smcginnisCinder and os-brick.18:16
smcginnishttps://opendev.org/openstack/os-brick/src/branch/master/os_brick/privileged/rootwrap.py#L2218:17
dansmithokay so maybe the bit of devstack that copied the brick rootwrap config into place has been removed to avoid the sync?18:18
smcginnisMaybe?18:19
dansmithor are you saying that nova and cinder included the things brick needed in their own config?18:19
smcginnisThat's how it was always done. And probably is still the case for most existing things.18:19
dansmithoh wow okay18:19
jokkeiirc that's how we used to do it (I think it was still at the time when the cinder store was there but not really usable). I just recall some discussion around "those files should not be shipped with the service but with the lib"18:22
*** k_mouza has joined #openstack-glance18:23
* dansmith nods18:30
abhishekkthere is another catch, devstack doesn't copy any of the data file to glance_store to anywhere :/18:38
abhishekkit copies those file to /usr/local/etc/glance only if I use setup.py install18:38
dansmithabhishekk: you don't mean devstack, I assume, you mean that when you install with pip you don't see the data files?18:41
dansmithI think pip puts those files in the egg, IIRC18:42
abhishekkdidn't found those in the eg18:43
abhishekkdidn't found those in the egg18:43
dansmithbecause it's being installed with -e maybe18:46
abhishekkmay be I should move back to https://review.opendev.org/#/c/743800/1/lib/glance@4718:47
abhishekkand then line #14818:48
dansmithI think that is the wrong move.. agree gmann ?18:48
dansmithglance forcing LIBS_FROM_GIT+=glance_store seems like a -2 to me18:48
abhishekkwhat is the use of this variable then?18:49
dansmithit should be controlled by the job, not a devstack module18:50
dansmithand, you should always be testing glance against the released version of glance_store,18:50
dansmithunless you're testing a depends-on18:50
abhishekkhmm18:50
dansmithand if you override it, you will break the ability to control that, AFAIK18:51
dansmithabhishekk: have you released glance_store yet? I would expect that pip installing from pypi will do a full install and not a -e one, such that the files will be installed,18:51
dansmithlike you see from os-brick18:51
abhishekkI haven't released glance_store yet18:52
dansmithif those files aren't installed when installed from pip normally, then nobody can use glance_store from pip, so we might as well delete it from pypi :)18:52
abhishekkI can verify it by removing os-brick and reinstalling it again using pip18:54
jokkeabhishekk: you won't be seeing those data_files coming from pip before the glance_store with that setup.cfg change has been merged18:54
abhishekkjokke, that change is merged18:54
dansmithit merged didn't it?18:54
jokkes/merged/released/18:54
abhishekkack18:54
jokkerealized my error just when I hit enter ;)18:54
dansmithoh abhishekk are you installing from pypi? I thought you were installing from local18:54
abhishekkwas disconnected in between18:59
abhishekkI missed conversation from <dansmith> oh abhishekk are you installing from pypi? I thought you were installing from local19:01
dansmiththat's all I said19:01
abhishekkok19:01
dansmithit seems like jokke thinks you're installing glance_store from pypi expecting the data_files change to be there, even though you haven't released it19:01
dansmithwhich obviously won't work,19:01
dansmithbut I was assuming you're installing from the local git tree with pip, like devstack does19:02
dansmithif devstack does an install from git of a package, and uses -e, I don't think that it will install the data files,19:03
dansmithbut if you install a released package from pypi it should19:03
dansmithI imagine devstack only does the from-git -e install if it has it in /opt/stack,19:03
dansmithso you should be able to either grab it from /usr/local if installed from pip release, or from /opt/stack if installed from pip local19:04
abhishekkdansmith, neither of it happening19:10
abhishekkwhen I try to installing from local git tree it runs command like;19:10
abhishekkpip_install -e '/opt/stack/glance_store[cinder]'19:11
abhishekksetup_develop /opt/stack/glance_store cinder19:12
abhishekksetup_develop /opt/stack/glance_store cinder19:12
abhishekk_setup_package_with_constraints_edit /opt/stack/glance_store -e cinder19:12
dansmithright, like I said, -e won't install the data_files19:12
dansmithbecause it's installing "in place" anyway19:12
dansmithso in that case, you'd get them from /opt/stack/glance_store19:13
dansmithif you release and install from pypi it *should* install them to /usr/local19:13
dansmithlike you see from os_brick19:13
abhishekkdansmith, ack19:15
abhishekkso I need to tweak the code like that19:15
dansmiththe devstack code, yes19:17
dansmithif glance_store is in LIBS_FROM_GIT, then configure_rootwrap should work, if not, then copy from /usr/local19:17
*** k_mouza has quit IRC19:20
*** k_mouza has joined #openstack-glance19:26
*** k_mouza has joined #openstack-glance19:27
*** k_mouza has quit IRC19:32
abhishekkdansmith, Configure cinder store for glance  https://review.opendev.org/74380019:40
abhishekkdansmith, if glance_store is in LIBS_FROM_GIT, then configure_rootwrap will not work as it accepts project_name as only param and then it will copy files from etc/glance_store to /etc/glance_store not /etc/glance19:41
*** rcernin has joined #openstack-glance19:41
dansmithabhishekk: ack19:43
abhishekkdansmith, +1 for comments, easy way :D19:45
dansmith:)19:45
*** rcernin has quit IRC19:45
dansmithI think we're highlighting that glance_store having rootwrap rules that have to be installed into /etc/glance's directory is a little confusing and weird19:46
dansmithit's definitely an unusual situation I think19:47
abhishekkyes19:48
openstackgerritAbhishek Kekane proposed openstack/glance master: PoC for lazy loading cinder store  https://review.opendev.org/74237319:53
* abhishekk signing out for the day19:57
jokkedansmith: I don't think they do ... one can put the rules where ever they want and point the rootwrap.conf to right path19:58
dansmithjokke: that's what I was asking above.. if we can configure glance to look at both the glance rootwrap.d and the glance_store rootwrap.d that seems much more ideal than having to meld them19:59
*** gyee has joined #openstack-glance19:59
jokkedansmith: there is no glance rootwrap ... it's coming from glance store20:00
jokkehttps://github.com/openstack/glance_store/blob/master/etc/glance/rootwrap.conf#L7 these are just the default values where the rules will be looked at but that line can have any path where you want to put them20:01
dansmithoh I thought we still needed it for some of the file stuff, but if that's all really in glance_store then.. much easier20:01
jokkeyeah, literally only thing using it is the cinder driver in glance_store ... we have no need for it otherwise20:01
dansmithI'm surprised we wouldn't use brick for all the cinder root things we need to do anyway...20:02
jokkeDon't even get me started, but we can't as brick doesn't support most of the cinder backends ;)20:03
jokkes/backends/backend protocols/20:03
dansmithum, okay :)20:04
jokkeThere is bowl of special sphagetti sauce in the cinder driver that in perfect world should be all handled by brick20:05
gmanndansmith: abhishekk : note, all lib/projects defined as 'required_projects' in zuul job are by default added to LIBS_FROM_GIT by devstack.20:10
gmannif you want to test the released version then we need to make sure glance_store is not in 'required_projects'20:11
dansmithgmann: yep, ack20:11
gmannwhich is case now in our jobs.20:11
dansmithgmann: abhishekk was making lib/glance force glance_store into LIBS_FROM_GIT all the time, which I think is -2 right?20:11
gmannyeah, we should not hard code and let job decide.20:12
dansmith++ thought so, just making sure :)20:12
gmannsorry for being late responsive. i am doing downstream things today :)20:13
dansmithgmann: np, thanks for following up :)20:14
*** openstackgerrit has quit IRC20:52
-openstackstatus- NOTICE: The openstackgerrit IRC bot (gerritbot) will be offline for a short period while we redeploy it on a new server20:52
*** zzzeek has joined #openstack-glance21:38
*** gregwork has joined #openstack-glance22:45
*** rcernin has joined #openstack-glance22:45
*** tkajinam has joined #openstack-glance22:54
*** openstackgerrit has joined #openstack-glance23:49
openstackgerritDan Smith proposed openstack/glance master: Make wait_for_fork() more robust against infinite deadlock  https://review.opendev.org/74576323:49

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