Tuesday, 2018-06-26

*** maysamacedos has quit IRC00:00
*** yamamoto has quit IRC00:03
*** rh-jelabarre has joined #openstack-kuryr00:08
*** salv-orlando has joined #openstack-kuryr00:11
*** salv-orlando has quit IRC00:16
*** s1061123 has quit IRC00:46
*** s1061123 has joined #openstack-kuryr00:50
*** yamamoto has joined #openstack-kuryr00:59
*** yamamoto has quit IRC01:05
*** salv-orlando has joined #openstack-kuryr01:11
*** salv-orlando has quit IRC01:15
*** hongbin has joined #openstack-kuryr01:21
*** phuoc has joined #openstack-kuryr02:24
*** yamamoto has joined #openstack-kuryr03:01
*** rh-jelabarre has quit IRC03:06
*** yamamoto has quit IRC03:07
*** hongbin has quit IRC03:54
*** yamamoto has joined #openstack-kuryr04:04
*** yamamoto has quit IRC04:09
*** pc_m has quit IRC04:29
*** dims has quit IRC04:30
*** pc_m has joined #openstack-kuryr04:33
*** dims has joined #openstack-kuryr04:35
*** gcheresh has joined #openstack-kuryr04:39
*** janki has joined #openstack-kuryr04:54
*** yamamoto has joined #openstack-kuryr05:05
*** CrayZee has joined #openstack-kuryr05:07
*** jchhatbar has joined #openstack-kuryr05:09
*** yamamoto has quit IRC05:12
*** janki has quit IRC05:13
*** ispp has joined #openstack-kuryr05:33
*** isssp has quit IRC05:36
*** snapiri- has joined #openstack-kuryr05:53
*** isssp has joined #openstack-kuryr05:53
*** ispp has quit IRC05:54
*** ispp has joined #openstack-kuryr05:55
*** CrayZee has quit IRC05:56
*** isssp has quit IRC05:58
*** openstackgerrit has quit IRC06:04
*** yamamoto has joined #openstack-kuryr06:09
*** yamamoto has quit IRC06:14
*** openstackgerrit has joined #openstack-kuryr06:52
openstackgerritDaniel Mellado proposed openstack/kuryr-tempest-plugin master: Skip service tests  https://review.openstack.org/57782106:52
*** yamamoto has joined #openstack-kuryr06:56
phuocHi, I tried kuryr-kubernetes by using devstack07:05
phuocbut I can not create pod07:05
phuocI want to know this is an issue in kuryr-kubernetes now, or it is just in my environment :)07:06
phuocthanks07:06
*** aojea_ has joined #openstack-kuryr07:18
ltomasbohi phuoc, can you provide a bit more information? what type of error are you seeing? are you using Octavia?07:19
*** pcaruana has joined #openstack-kuryr07:20
*** aojea_ has quit IRC07:20
dmelladophuoc: any local.conf around? :D07:21
phuochttps://github.com/openstack/kuryr-kubernetes/blob/master/devstack/local.conf.sample07:23
phuocI use this local.conf07:23
phuocI think this is problem with Octavia07:24
openstackgerritPeng Liu proposed openstack/kuryr-kubernetes master: Implement multi-vif driver  https://review.openstack.org/57562907:24
ltomasbophuoc, yes, you need to add something like this to your local.conf:07:26
phuocthe amphora's IP address in k8s-service-net should be the same with cluster IP address07:27
phuocAm I wrong?07:27
ltomasboOCTAVIA_AMP_IMAGE_FILE="/tmp/test-only-amphora-x64-haproxy-centos-7.qcow2"07:27
ltomasboOCTAVIA_AMP_IMAGE_SIZE=307:27
ltomasboOCTAVIA_AMP_IMAGE_NAME="test-only-amphora-x64-haproxy-centos-7"07:27
ltomasboand download to /tmp the qcow2 image before stacking:07:27
ltomasbowget https://tarballs.openstack.org/octavia/test-images/test-only-amphora-x64-haproxy-centos-7.qcow207:27
ltomasbophuoc, no, it should not be the same07:28
phuocltomasbo, thank you ^^07:28
openstackgerritPeng Liu proposed openstack/kuryr-kubernetes master: [WIP] Implement NPWG multi-vif driver  https://review.openstack.org/57800907:28
ltomasboclusterIP will be one of the allowed address pairs that the amphora VM accepts07:28
ltomasbophuoc, ^^07:28
openstackgerritPeng Liu proposed openstack/kuryr-kubernetes master: [WIP] Implement NPWG multi-vif driver  https://review.openstack.org/57800907:29
phuocI have another question, Will this issue be fixed soon? :)07:31
phuocbecause I can wait for 2 or 3 days07:34
ltomasbophuoc, what issue? the octavia thing? that is not an issue on kuryr-kubernetes side I believe, so I cannot answer07:34
ltomasbodmellado, do you have any info on that?07:34
dmelladowhat issue?07:35
dmelladophuoc: ?07:36
dmelladoif you mean the amphora qcow2 image07:36
phuocdmellado, yes07:37
dmelladothat's unrelated to kuryr-kubernetes but rather to Otavia and DIB07:37
phuocI got it07:37
dmelladobasically, unless you provide a precreated image like that07:37
dmelladoOCTAVIA_AMP_IMAGE_FILE and so07:37
dmelladoDIB fails to generate the Octavia image, thus devstack fails07:37
dmelladoI guess I'll update the sample local.conf, but if you check what do we do on the upstream infra is basically just the same07:38
dmelladohttps://github.com/openstack/kuryr-kubernetes/blob/master/playbooks/get_amphora_tarball.yaml07:38
phuocis there problem with ubuntu xenial ?07:41
*** yboaron_ has joined #openstack-kuryr07:43
phuocOk, I got that07:45
phuocthank you guys ^^07:45
*** pmannidi has quit IRC07:51
*** salv-orlando has joined #openstack-kuryr08:22
*** salv-orlando has quit IRC08:25
*** salv-orlando has joined #openstack-kuryr08:26
openstackgerritGenadi Chereshnya proposed openstack/kuryr-tempest-plugin master: Test restart of CNI and Controller kuryr pods  https://review.openstack.org/55249808:32
*** salv-orlando has quit IRC08:40
*** garyloug has joined #openstack-kuryr08:49
*** jchhatbar is now known as janki09:01
openstackgerritMerged openstack/kuryr-tempest-plugin master: Skip service tests  https://review.openstack.org/57782109:20
openstackgerritShachar Snapiri proposed openstack/kuryr-kubernetes master: Explicitly set threaded=False when starting Flask  https://review.openstack.org/57776009:23
openstackgerritShachar Snapiri proposed openstack/kuryr-kubernetes master: Remove redundant line from dragonflow config  https://review.openstack.org/57765609:27
*** salv-orlando has joined #openstack-kuryr09:41
*** salv-orlando has quit IRC09:46
*** jchhatbar has joined #openstack-kuryr10:17
*** janki has quit IRC10:19
*** salv-orlando has joined #openstack-kuryr10:42
dulekdmellado: Crap, skipping tests isn't enough because it's resourceSetup that fails… :P10:45
dmelladodulek: yeah :\10:46
dmelladoI'm thinking about maybe setting a whole setting for this on tempest for now10:46
dmelladosuch as in the config10:46
*** salv-orlando has quit IRC10:47
*** yamamoto has quit IRC10:58
openstackgerritDaniel Mellado proposed openstack/kuryr-tempest-plugin master: Explicitly disable service tests by default  https://review.openstack.org/57806210:59
dmelladodulek: ^^10:59
dmelladothat should handle it10:59
dmelladodammit10:59
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Explicitly set threaded=False when starting Flask  https://review.openstack.org/57776011:03
*** yamamoto has joined #openstack-kuryr11:07
*** yamamoto has quit IRC11:30
*** yamamoto has joined #openstack-kuryr11:33
*** atoth has joined #openstack-kuryr11:38
*** rh-jelabarre has joined #openstack-kuryr11:38
openstackgerritShachar Snapiri proposed openstack/kuryr-kubernetes master: Remove redundant line from dragonflow config  https://review.openstack.org/57765612:13
dulekyboaron_: Any progress with IP conflict investigation?12:22
dulekyboaron_: I've started looking and I see kuryr-kubernetes is doing multiple POST to /load-balancer/v2.0/lbaas/loadbalancers12:23
dulekyboaron_: It looks a bit like LB gets created, then some change is detected on Service and controller tries to create the LB again.12:25
yboaron_dulek, well, not yet, lemme check it12:25
dulekyboaron_: This is the run I'm looking at: http://logs.openstack.org/60/577760/1/check/kuryr-kubernetes-tempest-daemon-containerized-octavia/a4a1048/12:25
dulekyboaron_: Might be easier to communicate if we look on the same logs.12:26
yboaron_dulek, OK, 10x, checking it ..12:26
dulekyboaron_: See e.g. this: http://logs.openstack.org/60/577760/1/check/kuryr-kubernetes-tempest-daemon-containerized-octavia/a4a1048/controller/logs/screen-o-api.txt.gz#_Jun_25_12_26_00_14339612:28
dulekyboaron_: This is request ending with 201.12:28
dulekThen below there's a traceback for another POST that gets the IP conflict.12:29
dulekIt clearly looks like Kuryr tries to create the LB twice. I guess that it's done with the same IP.12:29
yboaron_Kuryr uses the IP (cluster IP) allocated by K8S12:30
dulekyboaron_: Ah, okay, though I don't think that invalidates my hypothesis?12:32
yboaron_dulek, I think that for some reason the pool/subnet separation between  K8S service IPAM and OCTAVIA amaphora allocation - not configured properly12:33
dulekyboaron_: Hm, okay, that should be pretty easy to check, lemme try.12:34
dulekyboaron_: Isn't it like Octavia just creates the amphora using the IP we've provided it with?12:39
yboaron_dulek, Octavia creates another port from this subnet12:40
openstackgerritDanil Golov proposed openstack/kuryr-kubernetes master: Add SR-IOV capabilities to VIF handler  https://review.openstack.org/51228012:41
openstackgerritDanil Golov proposed openstack/kuryr-kubernetes master: Add SR-IOV binding driver to CNI  https://review.openstack.org/51228112:41
*** maysamacedos has joined #openstack-kuryr12:46
yboaron_dulek, I can see that 'kuryr-kubernetes-tempest-octavia' gate is green, so I assume that it should be related to subnet pool separation12:48
yboaron_dulek, Did u see the failure also on non containerized gate ?12:48
dulekyboaron_: Yeah, the failure is transient and shows up on every Octavia gate.12:49
dulekyboaron_: I'll try to find an example.12:49
dulekyboaron_: Hm, I can't find it now to be honest…12:53
dulekMaybe you're right.12:53
yboaron_dulek, NP, I"ll dig at the latest zuul results of patch#57776012:54
*** yamamoto has quit IRC13:01
*** yamamoto has joined #openstack-kuryr13:29
*** snapiri- has quit IRC13:41
*** hongbin has joined #openstack-kuryr13:42
*** rh-jelabarre has quit IRC13:46
dulekyboaron_: Okay, you were right!13:48
dulekyboaron_: I think I have the root cause.13:48
dulekyboaron_: kuryr-controller gets restarted. If we're unlucky we end up creating second LB with same IP.13:48
yboaron_dulek, : BTW, checking https://review.openstack.org/#/c/577760/ latest Zuul failures, seems that tempest fails because 'service_tests_enabled' option is missing13:49
dulekyboaron_: I guess that's dmellado's fault. :)13:49
dulekyboaron_: There are two things to fix this. First - we should definitely fix the restarting issue.13:49
dulekyboaron_: But secondly - ensure_loadbalancer should check for old LB being created and delete/reuse it.13:49
yboaron_dulek, yes, that's correct13:50
dmelladodulek: heh13:51
dmelladowhat did I do?13:51
dmelladoxD13:51
yboaron_dmellado, take a look at http://logs.openstack.org/60/577760/3/check/kuryr-kubernetes-tempest-octavia/a26cac0/testr_results.html.gz13:51
yboaron_dmellado, 'oslo_config.cfg.NoSuchOptError: no such option service_tests_enabled in group [kuryr_kubernetes]'13:52
dmelladodamn13:52
dmelladomore and more bullshit of this13:52
dmelladoxD13:52
yboaron_dulek, A far as I remember in case kuryr-controller being restarted, LBaaS handler should not call LBaaS driver cause of : https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/handlers/lbaas.py#L28713:55
dulekyboaron_: I assume _is_lbaas_spec_in_sync returns false because some stuff wasn't finished yet?13:56
yboaron_dulek, but I agree that for robustness LBaaS driver should handle this case13:56
yboaron_dulek, most probably you are right13:56
dulekyboaron_: It's super tricky to write idempotent code for such case.13:57
ltomasbodulek, yboaron_: I also see that most (if not all) the calls to lbaas client are not try/catched13:57
dulekyboaron_: But there's worse thing - I don't know at all why kuryr-controller gets restarted because we don't have logs for previous restarts. :D13:57
ltomasboso, if they fail, the controller dies13:57
dulekltomasbo: Not controller, just Handler.13:58
ltomasbothe handler dies and the kuryr-controller crashes13:58
ltomasbobesause the lbaas driver failing, right?13:58
dulekltomasbo: We have RetryHandler in place to catch exceptions.13:58
yboaron_dulek,  we support HA, isn't it? standby should resume the work .. :-)13:58
dulekyboaron_: No HA in gate yet. ;)13:59
yboaron_dulek, just kidding13:59
dulekSeems like readinessProbe fails…14:00
*** jchhatbar is now known as janki14:01
ltomasboin my setup is the alive probe failing14:01
ltomasboand that restarts the kuryr-controller14:01
dulek"http://158.69.95.158:8090/ready: dial tcp 158.69.95.158:8090: getsockopt: connection refused"14:01
openstackgerritDaniel Mellado proposed openstack/kuryr-tempest-plugin master: Explicitly disable service tests by default  https://review.openstack.org/57806214:01
dulekLiveness does the same.14:01
dmelladodulek: yboaron_14:02
dmelladomy fault14:02
ltomasbothis is what I see in my env:14:02
dmelladoforgot to amend that14:02
dmelladoxD14:02
dulekltomasbo: Okay, awesome, so I can reproduce that locally?14:02
dmelladodulek: by going to ltomasbo house14:02
ltomasbohttp://paste.openstack.org/show/724312/14:02
dmelladoand logging in14:02
dmelladoxD14:02
ltomasboit is not the root, as it restarted the controller and I lost the initial cause14:03
ltomasbobut this is the state that is left, and why the controller is not getting over it after restarts14:03
*** rh-jelabarre has joined #openstack-kuryr14:03
dulekltomasbo: Oh my, what the heck is that.14:03
ltomasboit cannot find the created loadbalancer when restarting it seems14:04
dulekltomasbo: Restarting here could happen because of handler exploding a few times and liveness probe failing.14:04
ltomasboperhaps it is octavia breaking us...14:04
dulekBut - that's not what I see in the gate.14:04
dulekIn the gate I see connection refused.14:04
yboaron_dmellado, 10x for the update14:04
yboaron_dulek, what/where logs are u checking/digging into?14:05
dulekyboaron_: kubelet. E.g. http://logs.openstack.org/60/577760/1/check/kuryr-kubernetes-tempest-daemon-containerized-octavia/a4a1048/controller/logs/screen-kubelet.txt.gz#_Jun_25_12_00_19_49042414:06
dulekgcheresh: Hey man, by accident we've created ultimate kuryr-controller restarting machine in the gate.14:07
dulekgcheresh: We just don't know how it works yet.14:07
dulekgcheresh: But it already found issues in our code. xD14:08
ltomasbolol14:09
*** gcheresh has quit IRC14:10
dulekHey, looks like kubelet is trying port 8090, while the probes are on 8082 by default. We might have some mismatch here.14:11
*** gcheresh has joined #openstack-kuryr14:11
ltomasbo8090 was for cni, right?14:11
ltomasboand 8082 for controller, right?14:11
ltomasbodulek, ^^14:11
dulekltomasbo: mhm. There's no mismatch. Just CNI health checks fail as well.14:12
ltomasbodulek, I created an env with devstack, and I see both kuryr pods in bad status14:16
ltomasbokube-system   kuryr-cni-ds-hcvkd                  0/1       Running            10         31m14:16
ltomasbokube-system   kuryr-controller-7db7c944fb-gh9vt   0/1       CrashLoopBackOff   13         31m14:16
ltomasboand yes, I'm getting connection refused on port 808214:17
ltomasbo(on kubelet)14:18
dulekltomasbo: Both pods are on host networking.14:18
ltomasboJun 26 10:17:33 kuryr-i24c-02.mpc.lab.eng.bos.redhat.com hyperkube[39681]: I0626 10:17:33.549062   39681 prober.go:111] Readiness probe for "kuryr-controller-7db7c944fb-gh9vt_kube-system(03a6f212-7947-11e8-84a0-842b2b2d5e58):controller" failed (failure): Get http://10.16.144.154:8082/ready: dial tcp 10.16.144.154:8082: getsockopt: connection refused14:18
dulekltomasbo: Check out if you can reach that from localhost.14:18
ltomasbocurl 10.16.144.154:808214:19
ltomasbocurl: (7) Failed connect to 10.16.144.154:8082; Connection refused14:19
ltomasboand yes, both are on hostnetworking14:20
dulekltomasbo: Flask update broke another thing?14:20
ltomasboyes, this is with your patch applied14:21
dulekltomasbo: This looks fine: http://logs.openstack.org/60/577760/1/check/kuryr-kubernetes-tempest-daemon-containerized-octavia/a4a1048/controller/logs/kubernetes/pod_logs/kube-system-kuryr-cni-ds-pjmdd.txt.gz#_2018-06-25_12_40_03_67414:21
ltomasboUmm, in my case it is not working...14:22
ltomasboand I see both containers crashing...14:22
dulekltomasbo: Yes, yes, sure. I mean the logs from server initialization seem fine.14:23
ltomasbo Starting CNI health check server.14:23
ltomasbo * Serving Flask app "cni-health-daemon" (lazy loading)14:23
ltomasbo * Environment: production14:23
ltomasbo   WARNING: Do not use the development server in a production environment.14:23
ltomasbo   Use a production WSGI server instead.14:23
ltomasbo * Debug mode: off14:23
ltomasboI also see the cni health check server starting14:23
dulekltomasbo: Yeah, this looks fine, isn't it?14:23
ltomasbobut the controller dies after a while14:23
ltomasbowith no reason...14:24
ltomasbothese are the last 2 lines from the log14:24
ltomasbo2018-06-26 14:17:26.565 37 INFO werkzeug [-]  * Running on http://127.0.0.1:8090/ (Press CTRL+C to quit)14:24
ltomasbo2018-06-26 14:17:31.676 29 DEBUG kuryr_kubernetes.handlers.dispatch [-] 1 handler(s) available __call__ /usr/lib/python2.7/site-packages/kuryr_kubernetes/handlers/dispatch.py:6214:24
ltomasbo2018-06-26 14:18:00.858 29 DEBUG kuryr_kubernetes.handlers.dispatch [-] 1 handler(s) available __call__ /usr/lib/python2.7/site-packages/kuryr_kubernetes/handlers/dispatch.py:6214:24
ltomasboand similarly for the kuryr-controller14:25
ltomasbo2018-06-26 14:24:10.383 1 INFO kuryr_kubernetes.controller.service [-] Service 'KuryrK8sService' stopping14:26
dulekltomasbo: The controller isn't dying. It's getting killed by kubelet due to liveness/readiness check being unreachable.14:26
ltomasbo2018-06-26 14:24:10.387 1 INFO kuryr_kubernetes.controller.service [-] Service 'KuryrK8sService' stopped14:26
ltomasbonot even that I think14:26
ltomasbolet me remove the readiness/liveness probe to avoid those restarts14:26
dulekltomasbo: Why? It gets SIGTERM, so starts shutting down.14:26
dulekltomasbo: Good idea!14:26
ltomasbodulek, you are right, seems it is working without the probes14:30
yboaron_dulek, ltomasbo: could it be that the LBaaS Handler/driver exception (due to not being able to ensure already created LB ) is the root cause for all of this ?14:33
yboaron_changing:14:33
yboaron_https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/drivers/lbaasv2.py#L40414:33
yboaron_to :14:33
yboaron_except (n_exc.Conflict, n_exc.InternalServerError)14:33
yboaron_dulek, ltomasbo : should fix the LBaaS driver ensure_LB for already created loadbalancer14:33
dulekyboaron_: I don't think it's the root cause. The root cause is that healthchecks endpoint is unreachable.14:34
dulekltomasbo: Maybe it's time for netstat and checking if 8082 and 8090 are opened?14:34
ltomasbodulek, not in my env...14:36
ltomasboyboaron_, I think that will help with the issue, at least the one I'm hitting on my other env14:37
yboaron_ltomasbo, what issue is it?14:37
ltomasboproblem at ensure_loadbalancer14:37
ltomasboI saw t he loadbalancer was either created or in pending creation adn the controller could not start due to that14:38
ltomasboprobably it got restarted by some reason in between and then it cannot proceed further14:38
ltomasboyboaron_, though, in my case I'm getting the error when performing the find at line 40514:39
ltomasboso, probably that should also be try/catch14:39
yboaron_ltomasbo, yes, I assume controller restart and LBaaS state annotation weren't saved, otherwise the LB handler should stop at should_ignore14:40
ltomasboI guess so14:40
ltomasboand perhaps it was restarted by the probes14:40
ltomasbothat could explain why it didn't happen for juriarte, as he has the env without probes...14:41
*** rh-jelabarre has quit IRC14:41
ltomasbobut, in my case, deleting the svc and the loadbalancer, and then restarting the kuryr-controller fixed the issue14:41
yboaron_dmellado, ping14:58
dmelladoyboaron_: pong what's up?14:58
yboaron_dmellado, all well , 10x14:58
dmellado\o/14:59
yboaron_dmellado, I want to add the openshift python client in the tempest plugin14:59
yboaron_dmellado, https://github.com/openshift/openshift-restclient-python/blob/4de49b9c3c700ad3b8556b27aa948396ea4de55c/README.md14:59
dmelladoyboaron_: should be done in a fairly similar way as I did with the k8s one14:59
yboaron_dmellado, Yes , I saw that you just updated the requirements.txt file15:00
dmelladoyou can even make it depend on a config15:00
dmelladolike15:00
dmelladodefault container_foo = k8s15:00
dmelladobut then on the base15:00
dmelladoit'd create either k8s or openshift base on what you'd like to15:01
dmelladoand the openshift gates would override that15:01
dmelladooh, well15:01
dmelladoThe OpenShift client depends on the Kubernetes Python client, and as part of the installation process, the Kubernetes (K8s) client is automatically installed.15:01
dmelladoit won't really hurt15:02
yboaron_dmellado, Yep, so, should I add something also to requirements.txt ?15:03
dmelladoyboaron_: sure, if the client is on pypi I suggest that you just add that to the requirementes15:03
dmelladorequirements15:03
yboaron_dmellado, I have the openshift python client in my local env, for ocp gate15:03
dmelladohttps://pypi.org/project/openshift/15:03
yboaron_dmellado, OK, 10x!15:04
dmelladoyboaron_: you can just add like that15:05
dmelladobut also check that it doesn't raise the k8s client req15:05
dmelladoand after that I'd propose to add that to upper-requirements as well15:05
dmelladohttps://github.com/openstack/requirements/blob/master/upper-constraints.txt15:05
yboaron_dmellado, OK, 10x!15:06
dmelladoyboaron_: yw!15:06
dmelladoping me if you need help or clarification ;)15:06
dmelladoyboaron_: in any case15:06
dmelladothink that if your needs wouldn't be just enough with the k8s one15:07
dmelladothanks!15:07
yboaron_dmellado, NP15:07
dmelladodamn, the patch for skipping failed15:12
dmelladoltomasbo: could you take a look, I'll need to go soon-ish15:12
*** janki has quit IRC15:13
ltomasbodmellado, seems it is missing the service_tests_enabled option at kuryr_kubernetes...15:14
ltomasbo    oslo_config.cfg.NoSuchOptError: no such option service_tests_enabled in group [kuryr_kubernetes]15:14
dmelladoltomasbo: yeah, but I added it15:14
dmelladohttps://review.openstack.org/#/c/578062/2/kuryr_tempest_plugin/plugin.py15:15
ltomasbodmellado, https://review.openstack.org/#/c/578062/2/kuryr_tempest_plugin/config.py15:21
dmelladoltomasbo: just realized it15:21
dmelladoI need a coffee or time out15:21
ltomasbodmellado, ^^ perhaps you should change service_tests by service_test_enabled...15:21
ltomasboxD15:21
dmelladoexactly15:22
dmelladowill amend15:22
dmelladoand then go away15:22
dmelladoxD15:22
ltomasbo:D15:23
openstackgerritDaniel Mellado proposed openstack/kuryr-tempest-plugin master: Explicitly disable service tests by default  https://review.openstack.org/57806215:24
dmelladoltomasbo: dulek yboaron_ all tight15:24
dmelladoright15:24
dmelladonow it works15:24
dmelladocould you please make it sure so those changes15:24
dmelladogoes their way when this is done15:24
dmelladoI mean https://review.openstack.org/#/c/577760/15:24
* dmellado goes away15:25
dmelladottyl!15:25
dmelladog'night y'all15:25
*** garyloug_ has joined #openstack-kuryr15:29
*** garyloug has quit IRC15:32
*** garyloug__ has joined #openstack-kuryr15:36
*** yboaron_ has quit IRC15:37
*** garyloug_ has quit IRC15:39
*** garyloug__ has quit IRC15:41
*** pcaruana has quit IRC15:42
*** garyloug__ has joined #openstack-kuryr15:43
*** janki has joined #openstack-kuryr16:39
*** CrayZee has joined #openstack-kuryr16:49
*** CrayZee has quit IRC16:51
*** garyloug__ has quit IRC17:05
*** yamamoto has quit IRC17:12
*** yamamoto has joined #openstack-kuryr17:14
*** yamamoto has quit IRC17:20
openstackgerritMerged openstack/kuryr-tempest-plugin master: Explicitly disable service tests by default  https://review.openstack.org/57806217:59
*** yamamoto has joined #openstack-kuryr18:16
*** yamamoto has quit IRC18:20
*** yamamoto has joined #openstack-kuryr18:21
*** dmellado has quit IRC18:32
*** gcheresh has quit IRC18:49
*** atoth has quit IRC18:53
*** janki has quit IRC19:04
*** gcheresh has joined #openstack-kuryr19:48
*** gcheresh has quit IRC20:20
openstackgerritDaniel Mellado proposed openstack/kuryr-tempest-plugin master: Disable load balancer service scenario  https://review.openstack.org/57819520:27
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Explicitly set threaded=False when starting Flask  https://review.openstack.org/57776020:30
*** maysamacedos has quit IRC20:45
*** irenab has quit IRC21:51
*** irenab has joined #openstack-kuryr21:52
*** lihi has quit IRC22:22
*** lihi has joined #openstack-kuryr22:25
*** hongbin has quit IRC22:36
*** threestrands has joined #openstack-kuryr22:38
*** threestrands has quit IRC22:38
*** threestrands has joined #openstack-kuryr22:38
openstackgerritMerged openstack/kuryr-tempest-plugin master: Disable load balancer service scenario  https://review.openstack.org/57819522:47

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!