08:19:21 <yasufum> #startmeeting tacker
08:19:21 <opendevmeet> Meeting started Mon Jun 16 08:19:21 2025 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:19:21 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:19:21 <opendevmeet> The meeting name has been set to 'tacker'
08:19:24 <kuno316> Yes.
08:20:07 <yasufum> #link https://etherpad.opendev.org/p/tacker-meeting
08:22:00 <kuno316> Sorry, since these type of meeting is 1st time for me, I may bother to you.
08:22:11 <yasufum> it's ok
08:22:43 <yasufum> This is a link of etherpad for our weekly meeting.
08:23:08 <kuno316> Thank you. I am also checking the etherpad.
08:23:18 <yasufum> If you have any topic, please write down before the meeting.
08:23:53 <yasufum> Three topics on the etherpad, and the third one is a new one.
08:24:47 <yasufum> So, I'm going to check other two topics quickly, then discuss the third item.
08:24:59 <kuno316> OK.
08:25:12 <yasufum> So, let's start from the first item.
08:25:49 <yasufum> It's is a list of failure patches of heat-translator or tosca-parser.
08:26:05 <kuno316> OK.
08:26:33 <yasufum> I've fixed the problems one by one, and three patches are still remained.
08:27:41 <kuno316> Thank you. I do not have any comment.
08:27:44 <yasufum> All of remained patches are for stable branches.
08:27:48 <yasufum> ok
08:28:43 <yasufum> So, it's not so critical for our development since master branch is fine.
08:28:58 <yasufum> ok
08:29:07 <yasufum> Go to the next item.
08:29:26 <hi-koba_> ok
08:29:30 <yasufum> hi
08:29:47 <yasufum> I wonder you've already joined at once.
08:29:49 <kuno316> OK
08:30:04 <yasufum> Sorry for late for starting the meeting.
08:30:30 <yasufum> Now, we're on the second topic.
08:30:52 <yasufum> It's just a confirm the change of timeslot.
08:31:21 <kuno316> It is fine for me, and this meeting is new timeslot.
08:32:01 <hi-koba_> I thought my irc-app was not working, so I tried joining with the browser.
08:32:26 <yasufum> what application you're using?
08:32:41 <hi-koba_> This timeslot is good for me.
08:32:47 <yasufum> yeah
08:33:24 <hi-koba_> I'm using HexChat.But The meeting just hadn't started yet...
08:33:45 <yasufum> OK
08:35:05 <kuno316> One question, will you update this meeting information. https://meetings.opendev.org/#Tacker_(NFV_Orchestrator_and_VNF_Manager)_Team_Meeting
08:35:40 <yasufum> I'll do that, thanks.
08:35:53 <kuno316> Thank you.
08:36:42 <yasufum> good
08:36:59 <yasufum> So, let's move on to the third item if no more comment.
08:37:37 <yasufum> ok
08:37:39 <kuno316> no comment from my side.
08:38:06 <yasufum> thanks
08:38:26 <hi-koba_> ok
08:39:01 <yasufum> For the third topic, it's about an issue of devstack on zuul.
08:39:22 <yasufum> shivam: joining here?
08:39:33 <shivam> yes
08:39:51 <yasufum> Could you share your topic shortly?
08:39:57 <shivam> ok
08:40:28 <shivam> The next topic is "Zuul Patch Failures in Tacker Project: Devstack Stack Creation Errors Across OpenStack and Kubernetes Jobs".
08:41:10 <shivam> There are consistent Zuul job failures (RETRY_LIMIT issue) on the Tacker patches, specifically during the devstack stack creation phase in both OpenStack and Kubernetes job environments.
08:41:42 <shivam> For example, you can refer to this patch: https://review.opendev.org/c/openstack/tacker/+/939386
08:42:37 <shivam> In OpenStack-based tacker jobs, during stack creation, the compute nodes fail due to Nova services not registering in time, likely caused by issues with nova-conductor communication.
08:43:09 <shivam> The controller node fails with a Neutron API 500 error while adding a router interface, possibly due to a race condition or lock issue in security group handling.
08:43:42 <shivam> The controller-tacker node experiences image service discovery failures, preventing test image creation.
08:44:17 <shivam> In Kubernetes-based jobs, all nodes fail due to a setuptools error: missing the "get_requires_for_build_editable" attribute.
08:45:14 <shivam> Hence, I would like to hear the community member's input or opinions on this issue and if there are any suggestions on how we can resolve it.
08:45:26 <shivam> thanks
08:45:33 <yasufum> Thanks
08:46:37 <yasufum> Some of them, I've also found on another patch.
08:47:12 <yasufum> Although I don't still know the reason.
08:47:33 <kuno316> One stupid question, is there any good sample VNF in Tacker to pass these type of environmental error?
08:49:18 <yasufum> It's might happened before the environment is setup.
08:49:37 <shivam> yes
08:50:03 <yasufum> In other word, before Tacker is ready to use.
08:50:42 <kuno316> Thank you.
08:51:19 <yasufum> shivam: I'd agree to your suggestion, asking gurus.
08:52:59 <shivam> ok
08:53:07 <yasufum> By the way, for kubernetes-based tacker jobs, is there any similar issue on other projects?
08:53:35 <yasufum> Since it looks a problem of common package.
08:54:09 <shivam> I did check but did not found this issue on other projects
08:54:21 <yasufum> hmm, OK, thanks.
08:56:28 <yasufum> Thanks shivam, I also would like to follow the details later.
08:56:58 <shivam> ok
08:57:17 <shivam> thanks
08:57:17 <yasufum> Is there any other comment or question?
08:58:01 <yasufum> good
08:58:28 <yasufum> Thank you guys for the discussion.
08:58:40 <shivam> Thank you
08:58:46 <kuno316> Thank you.
08:58:54 <yasufum> All topics done, so let's close this meeting.
08:59:04 <yasufum> Thank you for joining, bye!
08:59:19 <kuno316> Thank you. Bye.
08:59:25 <shivam> thanks, bye
08:59:38 <yasufum> #endmeeting