Wednesday, 2019-11-13

brtknrjakeyip: its slightly incorrect too, atm stein only supports upto 1.14.600:18
brtknr1.14.7 and 1.14.8 do not seem compatible with stein for whatever reason00:18
jakeyipyeah doesn't work for me too. I tried 1.14.6 and that works00:19
brtknrflwang: ^^00:19
jakeyiperror in `pod/kube-flannel-ds-amd64-`, is that what is happening for you?00:20
jakeyip`kube-system   pod/kube-flannel-ds-amd64-gptmd             0/1     CrashLoopBackOff   10         27m`00:21
brtknryep same thing00:21
jakeyip@brtknr: you fixing up the pep8 errors? it's your commit but I can help if you like00:22
brtknrI am going to bed now, will take a look tomrrow, nearly 1am here00:23
jakeyipok I'll do it00:23
brtknrthankss :)00:23
jakeyipgood night :)00:23
brtknrhave a good day! will you come to the meeting at 9am utc tomorrow?00:24
jakeyipyeah sure :)00:24
brtknrsweet!00:26
openstackgerritJake Yip proposed openstack/magnum master: Add compatibility matrix for kube_tag  https://review.opendev.org/68567500:40
*** goldyfruit has joined #openstack-containers01:12
openstackgerritFeilong Wang proposed openstack/magnum master: Support TimeoutStartSec for k8s systemd services  https://review.opendev.org/69044501:14
*** udesale has joined #openstack-containers03:42
*** dave-mccowan has quit IRC04:02
*** dave-mccowan has joined #openstack-containers04:12
*** ykarel|away has joined #openstack-containers04:35
*** goldyfruit has quit IRC05:00
*** dave-mccowan has quit IRC05:05
*** ykarel|away is now known as ykarel05:47
*** trident has quit IRC07:57
*** trident has joined #openstack-containers08:06
*** ivve has joined #openstack-containers08:19
*** flwang1 has joined #openstack-containers08:31
*** ykarel is now known as ykarel|lunch08:37
brtknrMorning flwang, strigazi, jakeyip, Meeting in 15 minutes?08:43
flwang1brtknr: yes08:45
jakeyipsure08:46
flwang1brtknr: can you please revisit this https://review.opendev.org/#/c/690445/ ?08:46
flwang1brtknr: the podman doesn't work for me without this patch08:47
brtknrSure thing09:00
strigazimeeting?09:01
brtknr0/09:01
flwang1#startmeeting Magnum09:01
openstackMeeting started Wed Nov 13 09:01:48 2019 UTC and is due to finish in 60 minutes.  The chair is flwang1. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: Magnum)"09:01
openstackThe meeting name has been set to 'magnum'09:01
flwang1#topic roll call09:02
*** openstack changes topic to "roll call (Meeting topic: Magnum)"09:02
flwang1o/09:02
strigazio/09:02
jakeyipo/09:02
brtknro/09:02
flwang1strigazi: long time no see09:02
flwang1thank you for joining, guys09:02
strigazilast week I was in the summit. I could not join.09:03
flwang1before we go through the agenda on https://etherpad.openstack.org/p/magnum-weekly-meeting, anything you guys want to start first?09:03
flwang1strigazi: anything you can share from the summit?09:03
brtknrHow’s the summit?09:04
strigaziI'm reading the etherpad, give me a moment09:04
strigaziThe summit was 1800 attendees09:06
strigaziFrom my experience, an english speaking conference in China is not going to be attractive. I'm sure the conference would be more popular in chinese.09:07
flwang1strigazi: i can imagine09:07
strigaziI was not able to attend the PTG, there was an issue with my flight and I had to leave earlier. (Strike in germany)09:08
strigaziI didn't see many new projects/products in the summit.09:09
strigazis/many/any/09:09
flwang1sigh...09:09
brtknrStig, the only person who attended from StackHPC shared similar feelings09:10
flwang1strigazi: do you know where will be the next summit?09:11
flwang1North America?09:11
brtknrI believe its in Vancouver09:11
strigaziIMO, the TC should focus on stabilizing the core-projects. No new crazy changes09:11
strigaziyes, vancouver09:12
jakeyipthat'll be the third time in vancouver09:12
flwang1strigazi: I'd like to see TC take more responsibility on T instead of others09:12
flwang1i'd like to go the next one09:12
brtknrWhat OpenStack needs is fewer projects that work well09:12
flwang1i have missed the the other two in vancouver09:13
jakeyiplong long flight for us flwang1 :)09:13
strigaziKeystone, glance, nova, neutron should work. The rest is debatable.09:13
flwang1jakeyip: i know, my friend :)09:13
brtknrEqually long time to get there from the UK I think09:13
flwang1brtknr: which city are you based in UK?09:14
brtknrBristol, west coast... not that UK is very wide to begin with09:14
flwang1jakeyip: are you in Sydney or Melbourne?09:14
jakeyipMelbourne. The Core team is in Melbourne.09:14
jakeyipNectar Cloud Core Services team, to clear up any confusion with the 'core' work09:15
jakeyipword09:15
flwang1jakeyip: :)09:15
flwang1strigazi: anything else you want to share?09:15
strigazino, there was nothing else09:15
jakeyipwas there much interest in magnum? :)09:16
brtknrthat was going to be my question09:16
strigaziI don't think any of our contributors was there. Mohamed was there09:16
strigaziWe didn't have a Project Update.09:17
strigaziSo I can not tell what was the interest.09:17
flwang1fair enough09:18
strigaziFinally,09:19
strigaziManila and other teams will have additional on-line TPGs09:19
strigazis/TPG/PTG/09:19
brtknrAre we other teams?09:20
openstackgerritFeilong Wang proposed openstack/magnum master: Support TimeoutStartSec for k8s systemd services  https://review.opendev.org/69044509:20
strigaziWe should be09:20
brtknrDo we have a date/time09:21
strigaziNo09:21
flwang1strigazi: brtknr: if you guys all think we should have a dedicated PTG, then we can plan it09:21
flwang1before the Xmas holiday09:22
brtknrI think it would be useful to have some kind of planning meeting, even if we dont call it a PTG09:22
strigaziLet's decide next week? Ricardo is not here. I prefer that he is available before we (cern) can commit to something.09:22
flwang1strigazi: works for me09:22
brtknrsounds good09:22
flwang1when we say PTG, how long the session we need?09:22
flwang1given we're a world wide team, the TZ is still a problem for us09:23
strigaziTwo two-hour sessions?09:23
strigaziIn different days?09:23
flwang1then can we split it into 2 days?09:23
strigaziI don't think we need more09:23
strigaziyes, exactly.09:23
flwang14 hours is enough i think09:23
strigaziyeap09:23
flwang1next Wed and Thu?09:24
brtknrWould a meet/hangout be option?09:24
brtknrWould  meet/hangout be an option?09:24
strigaziI can not say for sure now, I need to talk to others here09:24
flwang1brtknr: yep09:24
brtknror would it be iRC only?09:25
flwang1or etherpad09:25
flwang1all good for me, i prefer to start with meet/hangout to say hi for each other09:26
flwang1then we can stay on etherpad09:26
flwang1and use the voice call for necessary cases09:26
strigaziok09:27
flwang1strigazi: did you see my email about master resize?09:28
brtknrokay shall we move to a topic on the agenda from roll call?09:28
flwang1the main thing i'd like to do in U release is the master resize and containerized master nodes09:28
flwang1sure09:29
flwang1#topic stable/stein 8.2.009:29
*** openstack changes topic to "stable/stein 8.2.0 (Meeting topic: Magnum)"09:29
flwang1brtknr: would you like to give us an updates?09:30
brtknrYes, so we recently noticed that the dns autoscaler is broken in stein as the docker repo has been removed completely09:31
brtknralso fa27 as also been removed so CI jobs are failing09:31
jakeyipsame here...09:31
brtknrstein 8.2.0 incorporates these changes09:31
brtknrfor us at stackhpc, we also need to support multiple NICS on a cluster and I have backported changes from master to enable this09:32
brtknrlastly, i'd like to also incorporate changes to support 1.14.7,1.14.8 in stein, possibly also 1.15.x, but havent managed to get to the bottom of why 1.14.7 and 1.14.8 clusters fail successfuly to spawn calico and flannel services in kube-system namespace09:33
brtknrdoes any of it seem controversial?09:33
flwang1brtknr: i think that's why strigazi replaced the atomic system container with podman09:34
flwang1strigazi: do you know the root cause why the 1.15.x doesn't work on atomic system container?09:34
brtknri think podman was to support 1.16.x09:34
flwang1brtknr: without podman, the max version of v1.15.x  working for me is v1.15.309:35
flwang1after cherry-pick the podman patch, v1.15.5 works for me09:36
flwang1i'm curious the root cause09:36
strigaziI haven't tried, I don't know. we are using 1.15.3 with atomic.09:37
jakeyipwondering if it is efficient to spend time figuring out why stein won't work with 1.14.7+? I think users would like to see 1.15 / 1.16 support more09:37
jakeyipfor us I think we will support at least one good version in stein and figure out how to get to train ASAP09:38
jakeyipso many nice new features09:38
strigazi1.14.x should work in atomic.09:38
strigaziwhere x any version09:38
strigaziI will try and let you know09:38
brtknrstrigazi: we have multiple sites where 1.14.7 and 1.14.8 are consistently failing to spawn with upstream stable/stein09:39
strigazi#action strigazi to try latest 1.14.x with atomic09:39
brtknras in, calico and flannel pods fail to start09:39
strigazibrtknr: what is the failure? why they don't start? what is the error?09:39
jakeyipsame thing I am seeing (flannel crashing)09:39
brtknrbut please try with upstream stable/stein, not a modified branch09:39
brtknryes, lots of CrashLoopBacks09:40
strigaziyes, but why? it can't read its token?09:40
strigazican you do logs?09:40
brtknrit caues everything else to stay in pending state09:40
brtknrcant read logs, says IP not assigned09:40
jakeyiplogs is broken for us I still haven't figured out why? does it work for you?09:40
strigazissh to node, docker logs09:41
jakeyipsame here brtknr. (I feel like I'm saying that a lot this meeting)09:41
strigazialso k get nodes?09:41
strigazido you see an IP?09:41
strigaziif k8s doesn't node ips (i.e. the occm hasn't given one)09:42
strigazilogs won't work09:42
brtknroccm has a daemonset but doesnt spwan a pod09:43
brtknroccm has a daemonset but doesnt spwan the pod09:43
flwang1i think it maybe related to the occm09:43
brtknrwhen i do k get nodes, no IP09:44
strigazithat is why logs don't work09:44
jakeyipI've got a failing cluster on hand, where should I dump the output?09:44
strigazipaste.openstack.org09:44
strigaziin fedora: fpaste <file>09:44
brtknrjakeyip: you can also do | nc seashells.io 133709:45
brtknrmuch easier :)09:45
jakeyiphttps://seashells.io/v/2MkCnqdw09:45
jakeyipbrtknr:  exactly what I was looking for :P09:45
strigazibrtknr: well not easier than fedora09:46
brtknrhttps://seashells.io/p/2MkCnqdw for plaintext09:46
strigazi5 chars vs 2109:46
strigazi6 chars :)09:46
brtknrnc seashells.io 1337 is platform agnistic :P09:46
strigaziand not community managed09:47
jakeyipok can we concentrate on the error message please :P09:47
brtknrtbh i didnt know about fpaste, good to know...09:47
strigazijakeyip: ssh to master, docker ps | grep flannel09:48
strigazidocker logs <flannel container>09:48
strigazibrtknr: jakeyip flwang1 before continueing with debugging, anything else for the meeting?09:49
jakeyipblank when I run logs09:49
jakeyiphttp://paste.openstack.org/raw/786024/09:49
brtknrare we happy with the shopping list for stein-8.2.009:49
strigaziTo sync via email for the online planning/PTG09:49
*** ykarel|lunch is now known as ykarel09:49
brtknranything else people want to ad09:49
strigazijakeyip: docker ps -a | grep flannel | grep -v pause09:50
jakeyipoh I have a minor bug. I upgraded to stein and my public templates were all not visible to the users anymore09:50
flwang1strigazi: i'd like to know the master resize work you mentioned before09:50
jakeyipturns out the new column in DB 'hidden' had the values set to 'NULL' instead of 1 or 009:50
strigaziflwang1: We did some work on adding/dropping members of the clusters. That's it.09:51
strigaziflwang1: We did some work on adding/dropping members from the etcd clusters. That's it.09:51
jakeyipI told brtknr it's minor and don't need to bother fixing it. But since there's going to be a new stein version not sure if we should fix this.09:51
flwang1jakeyip: it can be fixed by update the existing cluster's 'hidden' field09:51
flwang1strigazi: where can i see the code?09:51
jakeyipflwang1: yes all fixed but just to bring it up because it's a breaking behaviour09:52
brtknrjakeyip: if you can locate the commit, please cherry-pick it to stein-8.1.1... i agree 8.2.0 implies there are new features but its mostly bug fixes09:53
strigaziwe haven't pushed it. But we need to decide first on VMs vm k8s cluster for master nodes.09:53
strigaziflwang1: ^^09:53
strigaziflwang1: You have fork that runs the control in k8s, the work I mentioned is irrelevant to that use case.09:54
strigaziflwang1: You have fork that runs the control-place in k8s, the work I mentioned is irrelevant to that use case.09:54
strigaziflwang1: It makes sense only if the master nodes are in dedicated VMs and run etcd09:54
flwang1strigazi: ok09:55
flwang1i will think about it again09:55
jakeyiphttp://paste.openstack.org/show/786025/09:55
flwang1thanks for sharing that09:55
strigazijakeyip: so flannel, calico etc, can't read the token to talk to the k8s api.09:57
strigazijakeyip: I couldn't make it work without podman.09:58
flwang1https://stackoverflow.com/questions/46178684/flannel-fails-in-kubernetes-cluster-due-to-failure-of-subnet-manager09:58
strigazijakeyip: but this was for 1.16.x09:58
brtknrlooks like they have backported the same changes to 1.14.7 and 1.14.809:58
flwang1it sounds like we need another mount for the kubelet atomic system container09:58
strigaziwe have /var/lib/kubelet already.09:59
flwang1:(09:59
strigazilooks like they have backported the same changes to 1.14.7 and 1.14.8 What this means??10:00
strigaziwhich changes?10:00
flwang1i think brtknr doesn't know the changes, he just guess there are some changes :)10:00
strigazioh, ok :)10:01
brtknryes, its a guess10:01
flwang1should we call this meeting done ?10:01
strigazi+10:01
flwang1i'm going to leave10:01
strigazi+110:01
brtknrgoodnight!10:01
flwang1thank you guys10:01
flwang1#endmeeting10:01
*** openstack changes topic to "OpenStack Containers Team | Meeting: every Wednesday @ 9AM UTC | Agenda: https://etherpad.openstack.org/p/magnum-weekly-meeting"10:01
openstackMeeting ended Wed Nov 13 10:01:27 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/magnum/2019/magnum.2019-11-13-09.01.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/magnum/2019/magnum.2019-11-13-09.01.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/magnum/2019/magnum.2019-11-13-09.01.log.html10:01
flwang1i will send email to you guys to follow up the online PTG10:02
strigazi+110:02
brtknrhttps://seashells.io/p/xaudCkCB10:03
strigazithis is fine10:03
brtknrthis is what i see in install-cni pod10:03
jakeyipstrigazi: does CERN runs its own registry ?10:03
strigaziDone configuring CNI.  Sleep=true10:03
strigazijakeyip: yes10:04
strigazijakeyip: gitlab10:04
strigazijakeyip: gitlab on prem, storage cephs rados-gw10:04
strigazicephs rados-gw -> s3 API10:04
jakeyipmight need to set up one thinking how to make it HA10:05
brtknrthe k8s_POD_calico-node-8x8tw_kube-system_c436a68e-05fa-11ea-afbb-fa163e226df0_0 container doesnt appear to have any logs10:05
jakeyipimages are in ceph using S3 API?10:06
jakeyipis there any databases for the metadata e.g. tags and such10:06
strigazijakeyip: I don't know, I'm an end user10:06
jakeyipah I see10:07
strigazijakeyip: if are looking deploying one. gitlab is not implementing the registry v2 api. Which is not good.10:07
strigazibrtknr: I'm deploying a 1.14.8 cluster I'll let you know.10:08
brtknrstrigazi: on devstack?10:08
strigaziIs there a story where I can put info?10:08
strigazibrtknr: in our production10:08
brtknrI'll create one now10:08
jakeyipstrigazi: I see. thanks that's useful information10:09
brtknrstrigazi: https://storyboard.openstack.org/#!/story/200684610:16
brtknrjakeyip: do you get the same errors with 1.14.8?10:22
brtknri saw you were using 1.14.710:22
jakeyipI think so but I don't remember exactly. I can spin something up10:23
openstackgerritBharat Kunwar proposed openstack/magnum stable/stein: k8s_fedora_atomic: Add PodSecurityPolicy  https://review.opendev.org/69403210:23
*** ianychoi has quit IRC10:24
openstackgerritBharat Kunwar proposed openstack/magnum stable/stein: k8s_fedora_atomic: Add PodSecurityPolicy  https://review.opendev.org/69403210:24
brtknrwith regards to 8.2.0 or 8.1.1, it would be nice to also backport the PSP change to support 1.15.x10:28
brtknrI've tested 1.15.3 on devstack with the patch and it works10:28
brtknrstrigazi: with the above branch10:29
strigazi1.14.8 doesn't work for me either.10:45
*** udesale has quit IRC11:15
openstackgerritMerged openstack/magnum master: Support TimeoutStartSec for k8s systemd services  https://review.opendev.org/69044511:20
brtknrstrigazi: \o/ i am not completely delusional then :)11:36
*** henriqueof1 has quit IRC12:04
*** rcernin has quit IRC12:54
*** ianychoi has joined #openstack-containers13:00
*** ykarel is now known as ykarel|afk13:39
openstackgerritBharat Kunwar proposed openstack/magnum stable/stein: k8s_fedora_atomic: Add PodSecurityPolicy  https://review.opendev.org/69403213:39
brtknrstrigazi: Any joy? Is this failing for the same reason 1.16.x was failing?14:00
strigazibrtknr: yes14:05
*** bline has quit IRC14:07
*** bline has joined #openstack-containers14:12
*** lixingxing has joined #openstack-containers14:36
*** ykarel|afk has quit IRC14:43
*** ykarel has joined #openstack-containers14:49
*** lpetrut has joined #openstack-containers14:58
*** lixingxing has quit IRC15:37
*** lpetrut has quit IRC16:08
*** ykarel is now known as ykarel|away16:16
*** ivve has quit IRC16:26
*** goldyfruit has joined #openstack-containers16:55
*** mgariepy has quit IRC16:56
*** ykarel|away has quit IRC17:51
*** flwang1 has quit IRC19:36
*** rcernin has joined #openstack-containers22:32
*** goldyfruit has quit IRC23:49

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