| *** mhen_ is now known as mhen | 02:57 | |
| yasufum | Hi tacker team. | 08:02 |
|---|---|---|
| shivam | Hello | 08:03 |
| yasufum | hi | 08:04 |
| yasufum | #startmeeting tacker | 08:04 |
| opendevmeet | Meeting started Mon Dec 22 08:04:55 2025 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:04 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:04 |
| opendevmeet | The meeting name has been set to 'tacker' | 08:04 |
| yasufum | #link https://etherpad.opendev.org/p/tacker-meeting | 08:05 |
| yasufum | hi | 08:06 |
| takahashi-tsc | hi, sorry for the delay. | 08:06 |
| yasufum | We,ve just started the meeting. | 08:06 |
| yasufum | me too actually | 08:06 |
| yasufum | One topic on the etherpad from shivam | 08:07 |
| yasufum | shivam: Can you start the item? | 08:07 |
| shivam | yes | 08:07 |
| shivam | The discussion topic is related to an error related to "DemoVirtualStorage" Images which caused Tacker Compliance Test Failures | 08:08 |
| shivam | Some Tacker compliance tests are failing during VNF instantiation because of duplicate images named DemoVirtualStorage already present. | 08:10 |
| shivam | As per investigation, root cause seems that compliance testcases dynamically create images (e.g., DemoVirtualStorage) as part of test execution. These images are not getting cleaned up after the test execution completes. | 08:11 |
| shivam | As a result, when a subsequent test run attempts to create an image with the same name, it finds multiple images with identical names, causing the instantiation to fail due to non-unique image matches. | 08:12 |
| shivam | Error Message: "Error validating value 'DemoVirtualStorage': No images unique match found for {'name': 'DemoVirtualStorage'}" | 08:12 |
| shivam | On local setups, this issue was temporarily resolved by manually deleting the already existing images before re-running the tests. | 08:13 |
| shivam | But, since the same issue is also occurring in Zuul, a manual cleanup approach is not feasible, and a permanent fix solution is required. | 08:13 |
| shivam | Possible fix approaches could be a post-test cleanup logic which should automatically delete the created DemoVirtualStorage images. | 08:14 |
| shivam | or Modifying the image creation configuration/parameter so that a unique image name is created for each test case. | 08:15 |
| shivam | A launchpad bug has been created for the same: https://bugs.launchpad.net/tacker/+bug/2136980 | 08:15 |
| shivam | So, I would like to know the community’s thoughts on our bug, root cause analysis and fix suggestions. | 08:16 |
| shivam | Also, if there are any additional fix suggestions/approach from community members? | 08:16 |
| shivam | Thank you. | 08:16 |
| YuyaKuno | Sorry for stupid question. In general, who should clean up after testing? | 08:17 |
| yasufum | thanks | 08:17 |
| shivam | kuno: As per my understanding, Ideally, it should be cleaned up by tacker test code itself because it is being created during test execution | 08:18 |
| YuyaKuno | OK, thank you. In NFV, the point was challenge of TST010. Currently no mechanism to clean up test environment by Robot framework. | 08:20 |
| shivam | ok | 08:21 |
| yasufum | IMO, cleanup resources is not an essential issue without some specific usecases such as re-use a resource or so. | 08:23 |
| yasufum | In this case from shivam, I agree to shivam's stragegy since it's simple and feasible for the issue. | 08:23 |
| yasufum | Any other comment? | 08:24 |
| takahashi-tsc | I also agree, simple approach is better. | 08:25 |
| yasufum | thx | 08:25 |
| yasufum | good | 08:26 |
| shivam | Thank you. will proceed with the cleanup approach then. | 08:27 |
| yasufum | thanks | 08:27 |
| yasufum | All the topics done for today. | 08:27 |
| yasufum | Before closing, I'd like to skip the next meeting, and also the first meeting next year. | 08:29 |
| yasufum | So, it's the last one in this year. | 08:29 |
| takahashi-tsc | Sorry, just confirmation. Conclusion is that we adopt suggestion 2 "2. Modify the image creation configuration/parameter so that a unique image name is created for each test case.", right? | 08:29 |
| yasufum | yes | 08:30 |
| takahashi-tsc | OK, thanks | 08:30 |
| shivam | Oh.. ok, sorry I though it was first one | 08:31 |
| shivam | anyways, thanks for confirmation | 08:31 |
| yasufum | In my understanding, deleting img is to release useless resource and renaming is to avoid duplicated name, so both are not contradictory. | 08:36 |
| takahashi-tsc | Yes, both apporach is possible, and one of them is enough. My suggestion is to adopt only suggestion 2 because it is easy approach. | 08:37 |
| YuyaKuno | Is there any capacity issue by suggestion 2? | 08:38 |
| takahashi-tsc | Shivam, do you have any views on it? It is an important point of views. | 08:41 |
| shivam | kuno-san: Hmm... I think yes there might be storage problem | 08:41 |
| shivam | if the images are created for each testcase uniquely. Eventually, it will be required to delete those images to avoid any storage issue | 08:42 |
| YuyaKuno | I see. | 08:43 |
| shivam | But since, we ar referring to only compliance testcase (on zuul) so, I am not sure whether it will cause the storage issue on zuul | 08:44 |
| shivam | because for each build, a fresh environment will be created for execution | 08:45 |
| yasufum | The amount of resources is not enough sometimes on zuul. So, we'd better to take care about. | 08:47 |
| shivam | ok... | 08:50 |
| yasufum | I'm not sure it can be critical problem or not, it might be helpful to estimate the size of strage totally for the tests. | 08:57 |
| shivam | ok.. In that case, i think we can check the resource utilization after applying second fix suggestion and then discuss the result with community. | 08:57 |
| yasufum | thanks | 08:57 |
| shivam | Thank you. | 08:58 |
| yasufum | Any other comment? | 08:58 |
| yasufum | good | 08:59 |
| yasufum | Thank you for the discussion, guys. | 08:59 |
| shivam | thanks | 09:00 |
| yasufum | I've told that today is the last meeting in this year. | 09:00 |
| yasufum | I'll announce the first our meeting next year on the ML. | 09:01 |
| yasufum | Thank you for joining. | 09:01 |
| yasufum | Have a great holiday, and happy new year! | 09:01 |
| yasufum | Bye! | 09:02 |
| shivam | Thank you. Bye | 09:02 |
| takahashi-tsc | bye! | 09:02 |
| yasufum | #endmeeting | 09:03 |
| opendevmeet | Meeting ended Mon Dec 22 09:03:02 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:03 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-12-22-08.04.html | 09:03 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-12-22-08.04.txt | 09:03 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-12-22-08.04.log.html | 09:03 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!