Monday, 2025-12-08

*** mhen_ is now known as mhen02:15
yasufumhi, tacker team08:03
hi-kobahello08:04
yasufum#startmeeting tacker08:05
opendevmeetMeeting started Mon Dec  8 08:05:08 2025 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.08:05
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:05
opendevmeetThe meeting name has been set to 'tacker'08:05
yasufumLet's start the regular meeting.08:05
yasufum#link https://etherpad.opendev.org/p/tacker-meeting08:06
yasufumTwo topics on the etherpad08:07
yasufumand the first item is continuous discussion from the previous meeting.08:07
yasufumhi-koba: Any update on your topic for today?08:08
hi-kobayes. I want to share what we did and check the next actions.08:08
hi-kobaI updated the bug descriptions for the VNF multi-tenant issue and handled the duplicate bug.08:08
yasufumok08:08
hi-kobahttps://bugs.launchpad.net/tacker/+bug/212998308:09
hi-kobaFor the next action, I want to start working on fixing the bug.08:09
hi-kobawe plan to add "tenant_id" to the "vnf_package_vnfd" table and make VNFD tenant-scoped.08:10
hi-kobaMy discussion item is: Should I write a spec for this?08:11
hi-kobaI thought a spec isn’t needed for a bug fix... but since this changes the DB schema, I can write if needed.08:12
yasufumI'd suggest to propose a spec since your proposal is for changing a behavior although it might be tiny change.08:14
hi-kobaok08:14
yasufumthanks08:15
hi-kobaI have to submit it before the G-release spec deadline?08:15
yasufumAlthough I didn't join the day1 of the previous vPTG and don't know any discussion for spec freeze, do you have any target date for your spec?08:17
hi-kobaI think I can finish it in December.08:18
yasufumOK, fine.08:18
hi-kobaI think we didn't discussed the spec-freeze schedule at the vPTG.08:19
yasufumyeah08:19
hi-kobaI’ll start the spec. AI makes it easier now.08:21
yasufumIs it better to fix a date for spec although it's might be nothing other proposal for this release?08:21
yasufum31th Dec is acceptable if you'd better to do so?08:23
hi-kobaYes, it would be helpful for me if we fix a date for the spec.08:25
hi-kobaok 08:25
yasufumgood08:25
hi-kobaThat’s all for my item.08:26
hi-kobaThank you.08:26
yasufumPlease add this conclusion at the end of your topic, thanks.08:26
hi-kobaok, I'll add08:26
yasufumSo, let's get on to the next topic.08:26
yasufumshivam: Could you share your topic?08:27
shivamyes08:27
shivamThe next discussion topic is regarding tacker-v1-k8s helm-based tests are failing during CNF instantiation because VDU2 pods stay in `Init:ImagePullBackOff` and the CNF never reaches the Ready state.08:28
shivamFailing Testcases: "tacker.tests.functional.sol_kubernetes.vnflcm.test_kubernetes_helm.VnfLcmKubernetesHelmTest.test_vnflcm_with_helmchart" and "tacker.tests.functional.sol_kubernetes.vnflcm.test_kubernetes_helm.VnfLcmKubernetesHelmTest.test_cnf_insta_with_extra_field_v1"08:29
shivamThe failure occurs because the external Bitnami Apache Helm chart used in these tests still references the old image repository `bitnami/apache`, where the required image tag no longer exists.08:30
shivamBitnami has migrated the image to a new repository `bitnamilegacy/apache`, causing Kubernetes to fail pulling the image and resulting in repeated ImagePullBackOff errors.08:31
shivamThis issue is a critical one because it impacts CI stability causing zuul build failure.08:32
shivamI have also raised bug on Launchpad: https://bugs.launchpad.net/tacker/+bug/213433608:33
yasufumthanks08:33
shivamThe fix that we have identified is to update the helm parameter in test code to override the image repository mentioned in Helm chart’s `values.yaml` (bitnami/apache`) to the correct repository `bitnamilegacy/apache`.08:33
shivamI would like to hear the community’s feedback on our analysis and fix approach, and whether any alternative solutions are recommended.08:34
shivamthanks08:34
yasufumFor your discussion point, I have nothing other approach.08:35
yasufumI think your suggestion is reasonable for the issue.08:36
yasufumThanks.08:36
yasufumAny other comment?08:37
shivamYasufum: As per our analysis, I think this can be a temporary fix to ensure CI stability08:37
shivamBut i think the ideal fix should be in the bitnami apache helm chart itself in its values.yaml08:37
shivamhttps://github.com/bitnami/charts/blob/main/bitnami/apache/values.yaml#L71C1-L75C1308:38
yasufumsure08:38
yasufumthanks08:38
shivamThank you. For now, we will proceed with tacker code temporary fix itself 08:39
shivamthanks08:40
yasufumthx08:40
shivamThat’s all for my item from my side.08:41
shivamThank you.08:41
yasufumOK, all the topics done.08:41
yasufumSo, let's close this meeting.08:42
yasufumThank you for joining, bye!08:42
shivamThank you, bye.08:42
yasufum#endmeeting08:42
opendevmeetMeeting ended Mon Dec  8 08:42:40 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:42
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-12-08-08.05.html08:42
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-12-08-08.05.txt08:42
opendevmeetLog:            https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-12-08-08.05.log.html08:42
*** jgwentworth is now known as melwitt19:01
*** melwitt is now known as jgwentworth22:31
*** jgwentworth is now known as melwitt22:32

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