08:01:47 #startmeeting tacker 08:01:48 Meeting started Tue Jun 1 08:01:47 2021 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:01:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:01:51 The meeting name has been set to 'tacker' 08:03:12 * yasufum #link https://etherpad.opendev.org/p/tacker-meeting 08:03:53 We have two topics today 08:04:43 The second one is just a FYI, updating docs for oftc 08:04:57 Thanks 08:05:11 I have uploaded a patch for the change 08:05:51 ueha: can you start from your topic? 08:06:14 Thanks, I reviewed the patch and already +1! 08:06:17 Yes. 08:06:43 I have a topic about the patch for resolving FT error we discussed last week. 08:06:52 https://review.opendev.org/c/openstack/tacker/+/791252 08:07:00 Let me report on the progress. 08:07:22 As of patchset 8, all but sol-Kubernetes job were successful. 08:08:07 There is other problem with the sol-Kubernetes job, it seems to be occurred by kuryr-kubernetes patch [4] that changes to use kubeadm for installing Kubernetes on devstack. 08:08:24 [4] "Use kubeadm for installing Kubernetes on devstack.": https://review.opendev.org/c/openstack/kuryr-kubernetes/+/779250 08:08:50 Merged on May 25. 08:09:25 I tried changing the setting of ".zuul.yaml" to use kubeadm, but it didn't work now. 08:10:38 And the multi node job is failed but merged patch of kuryr-kubernetes [4]. The patch for fixing mutinode job was merged, but multinode job still fails in the patch. 08:11:15 Enable multinode gate: https://review.opendev.org/c/openstack/kuryr-kubernetes/+/791915 08:12:15 It will take a while to solve it.. 08:13:53 I have question and suggestion. 08:14:36 Should we temporarily remove sol-kubenetes job from voting? 08:15:21 Or should we temporarily use kuryr-kubernetes stable branch (e.g. wallaby) instead of master branch? 08:16:37 That all. Any comments or question? 08:18:20 Could I confirm “It will take a while to solve it.. “? 08:19:02 Sure 08:22:31 There is no solution proposed for fixing the issue yet? 08:23:38 Yes, it seems that a patch has not been posted yet. 08:26:18 I am not sure that your patch is passed if the issue of kuryr-kubernetes is fixed. 08:27:20 Is there the same error occurred between on your test result and kuryr-kubernetes? 08:29:20 No, I don't see the same error, so I don't think the kuryr-Kubernetes fix will make it work. 08:29:48 possibly? 08:30:03 Sorry for the confusion. Yes, possibly. 08:31:49 I feel like I'm stuck with another error before going to that one. 08:32:31 thanks 08:33:05 I have got understood the situation from your log… 08:33:56 I just report the bug to kuryr-kubernetes: https://bugs.launchpad.net/kuryr-kubernetes/+bug/1930368 08:33:58 Launchpad bug 1930368 in kuryr-kubernetes "go command not found when "KURYR_K8S_CONTAINERIZED_DEPLOYMENT: false"" [Undecided,New] - Assigned to Roman Dobosz (roman-dobosz) 08:35:12 If this bug is fixed, it might work well or failed multinode job.. 08:37:01 Umm 08:37:17 I don't know when the modification will be finished because other projects are involved. 08:37:34 So I would like to discuss what to do with sol-Kubernetes jobs. 08:38:28 Probably, we cannot make conclusion at this meeting... So should we discuss ueha's question, i.e. disable sol-kubernetes or use stable kuryr-kubernetes 08:38:36 ? 08:39:22 Anyway, it might be unstable for the changes to migrate to OVN, and fixes are expected to be uploaded. 08:40:00 I think it is better to wait the fixes for a while before dropping our test temporary. 08:41:09 Okay. Are there any patches that need to be merged urgently? 08:42:21 And I will try to make it a stable branch once and see if it works. 08:43:14 you mean, use kuryr-kubernetes stable/wallaby? 08:43:52 Yes 08:44:46 May It not be easy to change in the zuul test..? 08:45:07 OK. I think it is good. But what is next step if it works? We proceed with tacker development with wallaby kuryr-kubernetes? 08:47:36 It’s acceptable as a temporal solution, but not for tacker “xena” release. 08:48:01 So, we should fix it for anyway. 08:49:34 I think so, I will try to find a solution until IRC next week. Let me report it again. 08:49:46 OK, I write conclusion in etherpad L61- 08:49:49 Is it correct? 08:51:29 thanks 08:51:30 Thank you! I think it is correct. 08:52:02 OK thanks, let's continue to discuss it. 08:54:37 It seems done for the topic today. 08:54:48 Is there any other topic? 08:55:03 not from my side 08:55:25 me too 08:55:46 good 08:56:24 I’d like to close this meeting. 08:56:35 Thank you for joining, bye 08:56:44 Thanks! bye 08:56:46 thanks bye 08:56:47 thank you, bye 08:56:57 #endmeeting