multiple multi_nic tests knock out networking when run on systems with more than one NIC

Bug #1238570 reported by Brendan Donegan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
High
Brendan Donegan

Bug Description

The Calxeda hardware we are testing has two NICs and when running the multi_nic tests on it, the connection (via ssh) will die when running the second test. Using 'screen' to access the system shows that one of the interfaces is non-existent in ifconfig and the other has no IP address allocated. Further investigation is needed to determine the cause of this.

Related branches

tags: added: arm calxeda server
Changed in checkbox:
assignee: nobody → Brendan Donegan (brendan-donegan)
importance: Undecided → High
status: New → In Progress
Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

Ok, slightly weird that ifconfig shows only eth0 on boot, but two tests are generated (one for eth0 and one for eth1)?

Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

Ah, udev shows two however - this may be the cause of the test failure

Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

Well this was fairly simple - on any system with more than one NIC, the test will take down the other interfaces in order to make sure the correct one is being tested. It doesn't however bring them back up where appropriate, so the system may be left in such a state that it cannot be accessed over the network. This needs to be rectified.

summary: - multiple multi_nic tests knock out networking when run on Calxeda
+ multiple multi_nic tests knock out networking when run on systems with
+ more than one NIC
Daniel Manrique (roadmr)
tags: added: scripts
Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

Story 1002: The branch is under review but needs some tweaking before being merged.

Daniel Manrique (roadmr)
Changed in checkbox:
status: In Progress → Fix Committed
Changed in checkbox:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.