Closed viniarck closed 1 year ago
On yesterday's nightly execution, same error but in a different test test_120_patch_queue_id
:
------------------------------- start/stop times -------------------------------
tests/test_e2e_10_mef_eline.py::TestE2EMefEline::test_120_patch_queue_id: 2022-10-18,04:49:24.183312 - 2022-10-18,04:49:34.604396
=========================== short test summary info ============================
FAILED tests/test_e2e_10_mef_eline.py::TestE2EMefEline::test_120_patch_queue_id
= 1 failed, 171 passed, 2 skipped, 18 xfailed, 8 xpassed, 758 warnings in 10641.94s (2:57:21) =
Oct 18 04:49:24 runner-rmtk68xb-project-107-concurrent-0 2022-10-18 04:49:24,479 (Thread-108) werkzeug:INFO _internal:225: 127.0.0.1 - - [18/Oct/2022 04:49:24] "POST /api/kytos/pathfinder/v2/ HTTP/1.1" 200 -
Oct 18 04:49:24 runner-rmtk68xb-project-107-concurrent-0 2022-10-18 04:49:24,492 (Thread-103) werkzeug:INFO _internal:225: 127.0.0.1 - - [18/Oct/2022 04:49:24] "#033[35m#033[1mPOST /api/kytos/mef_eline/v2/evc/ HTTP/1.1#033[0m" 201 -
Oct 18 04:49:24 runner-rmtk68xb-project-107-concurrent-0 2022-10-18 04:49:24,489 (Thread-103) kytos.napps.kytos/mef_eline:WARNING evc:659: EVC(a9903606afaf42, Vlan_100) was not deployed. No available path was found.
Over the past 3 days this issue hasn't occurred, https://github.com/kytos-ng/pathfinder/pull/35 fixed it from the evidence that we have so far.
I'll go ahead and close the issue.
On October 16th,
test_020_create_evc_inter_switch
failed, since no path was found it didn't get deployed:It's unexpected since looking at the debug event logs pathfinder got the topology updated accordingly:
I haven't found any other cause on topology that might have led to this yet.
On another test case, there was a similar behavior where the EVC didn't get deployed as highlighted on this comment https://github.com/amlight/kytos-end-to-end-tests/issues/160#issuecomment-1278151550, consistency check didn't get triggered pre-maturely with a short interval this time.