RohanK-Calsoft
commented
5 years ago The panic trace log corresponding to it, is in the attachment. Trace.txt
Open RohanK-Calsoft opened 5 years ago
RohanK-Calsoft
commented
5 years ago The panic trace log corresponding to it, is in the attachment. Trace.txt
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
Steps of the test-case:-
Step1:- Create and configure dummy-interfaces on all invaders. Then make the necessary configuration changes in /etc/bird/bird.conf file (The detailed files related to config of every invader are in the attachment below.)
Step2:- Restart the 'bird' service and check the 'bird' status.
Step3:- Wait for the convergence and check all the routes are converged using command "sudo birdc show route"
Step4:- Bring the link down, and wait for the routes to get disappeared and then again check the birdc routing table using the above command to verify if the changes are reflected.
Step5:- Again bring the links up and check the birdc routing table again to verify if the new changes are reflected again.
Now, the observation is when the links are brought down (Step-4). We lose the ssh-connectivity on those Invaders where the link is brought down and the test-case execution stops. SSH connectivity is loosing since invader becomes unresponsive due to kernel panic.
This issue is verified and reproduced on both the setups and the ssh-connectivity loss was observed on Invader44 (setup-2) and Invader30 (setup-1) Regress_GeneralRouting_BGP_BIRD_BGP Peering_StatesPropagation_013.docx