15:00:52 <dulek> #startmeeting Kuryr
15:00:53 <openstack> Meeting started Mon Feb 11 15:00:52 2019 UTC and is due to finish in 60 minutes.  The chair is dulek. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:54 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:57 <openstack> The meeting name has been set to 'kuryr'
15:01:02 <dulek> Hey there, anyone here for the meeting?
15:01:24 <dulek> Last 2 were only me speaking, so that's why I'm asking. :D
15:02:18 <maysams> o/
15:04:47 <dulek> ltomasbo: Hey there? ;)
15:05:22 <ltomasbo> o/
15:05:32 <dulek> #topic announcements
15:05:58 <dulek> With etcd ramdisk and https://review.openstack.org/#/c/632684/ merged we should have much better gate stability.
15:06:24 <dulek> So it took a while, but I guess things are back to normal.
15:06:54 <dulek> There are still some issues with network isolation tests failing and pools test.
15:07:13 <dulek> If ltomasbo has some time to take a quick look on those it might be quite useful.
15:07:22 <dulek> Otherwise I can add it to my plate. :)
15:08:16 <ltomasbo> dulek, I can take a look
15:08:51 <ltomasbo> dulek, do you have any example? I thought pools problem were fixed after genadi's patch sets
15:09:12 <ltomasbo> (sorry for the slow reply... in another meeting...)
15:09:19 <dulek> ltomasbo: Sure, just a sec…
15:09:31 <dulek> ltomasbo: http://logs.openstack.org/84/632684/1/experimental/kuryr-kubernetes-tempest-containerized-openshift/7acf659/testr_results.html.gz
15:09:36 <dulek> ltomasbo: This is isolation.
15:10:45 <ltomasbo> dulek, ok, I'll take a look
15:11:17 <dulek> ltomasbo: Aaaand… I can't find a recent pools gate failure so maybe gcheresh patch fixed it.
15:11:49 <ltomasbo> dulek, that is what I thought... but new problems may arise... so... :)
15:12:03 <dulek> ltomasbo: Will ping you once I encounter it.
15:12:06 <ltomasbo> dulek, anyway, I'll take a look at the isolation one...
15:12:07 <dulek> #topic open discussion
15:12:09 <ltomasbo> dulek, sure! thanks!
15:12:15 <dulek> Anyone wants to raise something else?
15:15:54 <gcheresh> dulek: Actually wait_service_status is testing the connectivity in incorrect way sometime
15:16:12 <gcheresh> for ClusterIp service it should run from the pod and not from the tester
15:16:19 <gcheresh> and anyway it doesn't work correctly
15:16:33 <dulek> gcheresh: Oh, yes, but in the gate it should be fairly okay?
15:16:34 <gcheresh> I am talking about kuryr-tempest-plugin base.py file
15:17:30 <gcheresh> dulek: At least on d/s when isolation is enabled it brokes all the tests related to the services, so I guess it could happen in devstack, ltomasbo?
15:18:21 <ltomasbo> it will not happen upstream as it is executed from the cluster itself
15:18:49 <ltomasbo> gcheresh, ^^ no nested testing, and run from the controller/master node
15:20:18 <gcheresh> ltomasbo: ok, anyway this function is not working correctly, it's not testing that all the pods behind service answer, so even if one answers twice it returns True, but it doesn't break the gates :)
15:20:23 <dulek> Anyway it should be fixed one day, I guess. :P
15:21:45 <ltomasbo> dulek, gcheresh: yes, it should be fixed, and make it more flexible, so that it can run in a different node than from within the cluster
15:23:19 <gcheresh> I started to work on it, trying to curl the service from the pod instead but it didn't work for me as for the classmethod function I was calling the regular one, so trying to find a different solution
15:23:54 <ltomasbo> gcheresh, I missed the patch upstream, please add me as reviewer!
15:24:14 <gcheresh> didn't upload it as I need to change an approach
15:24:38 <gcheresh> working on it, when I'll have something working, I'll upload and add yoi
15:24:40 <gcheresh> you
15:24:49 <dulek> Awesome, me too please! :)
15:24:52 <ltomasbo> gcheresh, thanks!
15:26:02 <dulek> Okay, anything else?
15:29:31 <dulek> I guess that's it, thanks folks!
15:29:33 <dulek> #endmeeting