| *** hemna2 is now known as hemna | 01:36 | |
| *** hemna7 is now known as hemna | 07:38 | |
| yasufum | Hi tacker team. | 08:00 |
|---|---|---|
| manpreetk | Hi | 08:00 |
| ueha | hi | 08:00 |
| takahashi-tsc | hi | 08:00 |
| h_asahina | hi | 08:00 |
| masaki-ueno | hello | 08:00 |
| yasufum | #startmeeting tacker | 08:01 |
| opendevmeet | Meeting started Tue Feb 8 08:01:20 2022 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:01 |
| opendevmeet | The meeting name has been set to 'tacker' | 08:01 |
| yasufum | #link https://etherpad.opendev.org/p/tacker-meeting | 08:02 |
| yasufum | start the meeting | 08:02 |
| yasufum | The first item is mine. | 08:03 |
| yasufum | As mentioned in the previous meeting, I'd like to share the contents for the next summit. | 08:04 |
| yasufum | There are three items from us. | 08:04 |
| yasufum | I'd appreciate if you give us your feedback on the etherpad. | 08:05 |
| yasufum | Do you have any comment, or can we go to the next topic? | 08:06 |
| yasufum | good | 08:07 |
| yasufum | The second item is about the next vPTG. | 08:07 |
| yasufum | It will be held from April 4th to 8th. | 08:08 |
| yasufum | I've already reserved rooms for our team. | 08:09 |
| yasufum | It's the same as previous vPTG, 6-8 UTC each day, at Austin. | 08:11 |
| yasufum | Although I believe it's OK for everyone, but give me ask if you have any request for. | 08:12 |
| yasufum | The deadline is Marth 11th, so I'd like to fix it before the week. | 08:13 |
| yasufum | Anyway, I'll send a e-mail to announce our candidate dates on ML. | 08:14 |
| yasufum | Let's move on to the next topic. | 08:15 |
| yasufum | esto-aln: can you share your topic? | 08:15 |
| esto-aln | yes | 08:16 |
| esto-aln | thank you for having me.. I would like to proceed with my topic.. | 08:16 |
| esto-aln | We found some issue with tacker during the compliance test (of robot patch).. | 08:16 |
| esto-aln | Please refer to line 17 for the Log snippet... I indicated in bold those logs that I need to highlight.. | 08:17 |
| esto-aln | This issue only occurs sometimes... | 08:18 |
| esto-aln | so it is difficult to reproduce this issue.. we have not successfully reproduced such issue in our environment.. | 08:18 |
| esto-aln | Based on our investigation, we saw to possible causes (2 points) which I shared in Line 30. | 08:19 |
| esto-aln | We would like to consult, if someone from community team is familiar at this part of tacker.. | 08:20 |
| esto-aln | whether our assumption is correct or if they have another idea for the cause? | 08:20 |
| yasufum | thanks | 08:21 |
| yasufum | Is the error happened only on your patch, or all? | 08:21 |
| yasufum | I'm not sure the details of logs you shared. | 08:22 |
| esto-aln | <yasufum> Is the error happened only on your patch, or all? --> We encountered this issue on our patch.. | 08:24 |
| ueha | It's not a fundamental solution, but how about changing the vnfInstance name for each test? | 08:25 |
| ueha | Have you already tried it? | 08:25 |
| esto-aln | Yes, we already did it.. | 08:27 |
| esto-aln | but probably this is still an issue.. | 08:27 |
| esto-aln | since vnfInstance name might probably be set with the same name. | 08:28 |
| esto-aln | by some use.. | 08:28 |
| esto-aln | sorry... by some "user" | 08:28 |
| ueha | Does it mean that VnfInstance name is defined on the side of SOL test codes? | 08:30 |
| *** akekane_ is now known as abhishekk | 08:31 | |
| esto-aln | Yes, vnfInstance name was defined in the SOL test codes.. and the errors that occurred corresponded to these test cases which contains vnfInstance name (having the same name) | 08:32 |
| ueha | umm.. I understood.. | 08:33 |
| esto-aln | Currently, we have removed the vnfInstance name so that tacker generates the vnf Instance name... | 08:33 |
| esto-aln | but the point is that using the vnfInstance name and having deleted_at to be updated up to the seconds.. will trigger this issue.. | 08:35 |
| esto-aln | using the vnfInstance name ---> using the same vnf Instance name | 08:35 |
| esto-aln | sorry for the mistake.. | 08:36 |
| takahashi-tsc | I heart that now there is no issues for development of applying Robot, because we can controll VNF name by test code. esto-aln's question is, is it OK that "deleting VNFs in 1 second leads to error"? | 08:37 |
| yasufum | I think it's acceptable. | 08:37 |
| yasufum | By the way, such a case can be happened on the test, but usual cases, right? | 08:38 |
| esto-aln | Our assumption is that this might be possible bug.. | 08:38 |
| esto-aln | Yes, it will happen in usual cases. | 08:40 |
| yasufum | Do you mean we should fix the code itself other than test anyway? | 08:40 |
| esto-aln | Yes, I think so.. | 08:42 |
| takahashi-tsc | I think it is OK that Tacker team just decide whether this issue will be fix or not. But at least, "DBDuplicateEntry" seems a little strange for users. | 08:46 |
| takahashi-tsc | This is just my opinion. | 08:46 |
| yasufum | Simply we can have two choices, changing the format of the key, or waiting for a second in the function. | 08:47 |
| yasufum | Although I don't want to take the former one. | 08:47 |
| yasufum | Do you have any other idea? | 08:47 |
| takahashi-tsc | Does "waiting~~~" mean users should wait 1 second(and we should explain it in docs)? or Tacker wait a second in delete procedure when DBDuplicateEntry is detected? | 08:49 |
| yasufum | I mean later one, waiting inside tacker. | 08:50 |
| yasufum | I'm not still sure it's feasible or not. | 08:50 |
| yasufum | I don't oppose the idea to ask users to wait as a second best solution... | 08:53 |
| takahashi-tsc | Hmm, I think we do not need to decide today, We will confirm it(wait a second) is feasible or not and will share the result. | 09:00 |
| yasufum | i see | 09:01 |
| yasufum | esto-aln: Why don't you continue to discuss on gerrit? | 09:02 |
| esto-aln | yes, it's okay or let's discuss at IRC.. | 09:05 |
| yasufum | thanks | 09:07 |
| yasufum | All topics done for today. | 09:07 |
| yasufum | let's close this meeting. | 09:12 |
| yasufum | Thanks for joining, bye! | 09:12 |
| takahashi-tsc | thanks bye | 09:12 |
| ueha | thanks, bye | 09:12 |
| esto-aln | thank you very much, bye! | 09:12 |
| manpreetk | bye. | 09:13 |
| ma-ooyama | thanks, bye | 09:13 |
| masaki-ueno | bye | 09:13 |
| yasufum | #endmeeting | 09:13 |
| opendevmeet | Meeting ended Tue Feb 8 09:13:54 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:13 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-02-08-08.01.html | 09:13 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-02-08-08.01.txt | 09:13 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-02-08-08.01.log.html | 09:13 |
| *** lifeless_ is now known as lifeless | 09:24 | |
| *** dasm|off is now known as dasm | 13:55 | |
| *** osmanlicilegi is now known as Guest1 | 20:56 | |
| *** dasm is now known as dasm|off | 23:02 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!