search

platinasystems / go

Other
9 stars 68 forks source link

"docker_quagga_ospf_traffic_subports" test-case failing during regression. #150

Open RohanK-Calsoft opened 5 years ago

RohanK-Calsoft commented 5 years ago

Build version:-

root@invader42:/home/rohan# goes vnetd -version fe1: v1.1.3 fe1a: v1.1.0 vnet-platina-mk1: v1.0.0

root@invader42:/home/rohan# goes version v1.1.1

BuildID[sha1]=5046b7c2cdea8604d331dd7e5dd2fb9c85fa21ff

This test case covers verification of OSPF traffic between quagga containers on Platina switches. Each switch has total of 128 interfaces (sub-ports).

Steps of the test-cases:-

Step1:- To create sub-port: We need to create port-provision file located in /etc/goes directory and then restart goes. (If there pre-exists a portprovision file, take a backup of it and apply it back once we complete the testcase) We have created 4 sub-ports for each interface with 25g speed.

The detailed architecture and between the interfaces of the Invader and the containers is in the file below.

Step2:- Run ' ./updown.sh up ' script on all the switches. This would automatically create the containers, create 1 dummy interface for each container and also map the interfaces(and it's corresponding IP addresses) to the containers.

Step3:- Then enter a container and check the OSPF neighbourships and see if ospf has learned the routes to all 4 routers by using the command "docker exec -it R105 bash" , "vtysh" and"show ip ospf neighbor" .

Step4:- Run ' ./updown.sh down ' to stop the containers and release the interfaces back to switch.

Now, the observation is that test-case is failing due to routes not being visible in the routing table. The reason for that is on Invader32 in the neighbourship list , Invader30 is not visible.

Regress_Container_subport_GeneralRouting_Quagga_OSPF_Traffic_021-1.docx

Ad9195 commented 5 years ago

I'll look into it, but I don't thinks this issue is from automation point of view, still I'll verify it once.