[IEC-25] [IEC][SEBA][PONSim] Errors while running SIAB robot tests Created: 23/Oct/19  Updated: 08/Apr/20  Resolved: 08/Apr/20

Status: Done
Project: Integrated Edge Cloud
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Ciprian Barbu Assignee: Ciprian Barbu
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File SiaB_robot_1.txt     Text File SiaB_robot_2.txt    
Issue Links:
Relates
relates to IEC-35 [IEC][SEBA] Update and refresh testin... In Progress

 Description   

We have encountered a couple of errors while running the SIAB tests, even on x86 pods, where the robot tests fail after timeout waiting for various conditions.

This bug was identified some while ago, but because of IEC-22 I have postponed working on this. I will update this as soon as we re-test and have a better understanding how it reproduces.

My assumption so far is that the errors happen because we try to run the cord-tester SIAB tests from a Docker container, whereas in opencord everything is run from a single machine, no cross-network kubernetes necessary

 

 Comments   
Comment by Ciprian Barbu [ 08/Apr/20 ]

With the work in IEC-35, I was able to run the SiaB tests from within a Docker container (iecedge/cord-tester) and tests passed successfully. There were a couple of things that needed to be fixed, which now reside in a fork of cord-tester:
https://github.com/iecedge/cord-tester/commits/cord-7.0-arm64

Comment by Ciprian Barbu [ 30/Oct/19 ]

After the failed attempt described in SiaB_robot_1.txt, I ran the robot command line again, and this time the result was different, as described SiaB_robot_2.txt. The first test case failed, but many of the other ones passed. However they took quite a while to complete, I'm not sure if this is normal or not.

Comment by Ciprian Barbu [ 30/Oct/19 ]

A bit of a context:

We try to run the same SIAB robot tests from the cord-tester framework as opencord does in their SIAB Jenkins jobs [1].

Because of various aspects, better described on this email I sent to the Akraino mailing list [2], we are using a Docker image to provide a controlled environment for cord-tester, even though this itself runs in a python virtualenv, there are still a few things to cover like users and password and some broken dependencies for aarch64.

The main problem of running cord-tester this way, is that all the Kubernetes calls will be made remotely to the K8S master on our IEC POD deployed with SEBA. This is different than SEBA-in-a-Box, which runs everything on a single machine.

It is also possible that some other steps, prior to running the tests, are not performed correctly, i.e. there is a PONSim installation script in our iec repo which "fakes" the installation of SiaB [3].

To get back to the actual problem, I'm seeing the robot tests failing in a few different way, and I will add log files here to exemplify.

 

[1] https://jenkins.opencord.org/view/SIAB/job/seba-in-a-box-build-test-stable/

[2] https://lists.akraino.org/g/blueprints/topic/seba_akraino_blueprints/34105677?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,80,34105677

[3] https://gerrit.akraino.org/r/gitweb?p=iec.git;a=blob;f=src/use_cases/seba_on_arm/test/ponsim/install.sh;h=6aa728b4e409846167a4f126afd37d3fcc7ae467;hb=e70f1cbe15e44cc01e3114cd69481e9b33ce351f#l57

Generated at Sat Feb 10 06:02:14 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.