Bug 1403087

Summary: NIC test failed because “Error: could not bounce interface"
Product: Red Hat Certification Program Reporter: Kyle IK Chen <kyle_ik_chen>
Component: redhat-certification-hardwareAssignee: brose
Status: CLOSED NOTABUG QA Contact: Brian Brock <bbrock>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0CC: gnichols, kyle_ik_chen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-19 01:32:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Ping -I enp53s0f1 -Ac1 192.168.0.118 none

Description Kyle IK Chen 2016-12-09 02:34:52 UTC 
Description of problem:
Using 4.1-20161031 testkit version to test NIC that will be failed because “Error: could not bounce interface

Version-Release number of selected component (if applicable):
4.1-20161031

How reproducible:


Steps to Reproduce:
1. Install RHEL 7.3.
2. Install Testkit
3. Run NIC Test

Actual results:
Shutting down interface enp53s0f1
interface enp53s0f1 is down
Bringing up interface enp53s0f1
ifup enp53s0f1 returned 0
Interface enp53s0f1 is UP
Checking via ping to 192.168.0.118... Error: could not ping test server 192.168.0.118 
Error: could not bounce interface enp53s0f1

Expected results:


Additional info:
Comment 1 brose 2016-12-11 04:28:07 UTC 
Please ssh into the SUT and try these commands, letting us know the results:

ifdown enp53s0f1
ifup enp53s0f1
ping -I enp53s0f1 -Ac1 192.168.0.118
Comment 2 Kyle IK Chen 2016-12-12 00:42:59 UTC 
Please see the attachment.
Comment 3 Kyle IK Chen 2016-12-12 00:43:32 UTC 
Created attachment 1230676 [details]
Ping -I enp53s0f1 -Ac1 192.168.0.118
Comment 4 brose 2016-12-14 15:45:32 UTC 
[root@ele732016 Desktop]# ping -I enp53s0f1 -Ac1 192.168.0.118
PING 192.168.0.118 (192.168.0.118) from 192.168.0.142 enp53s0f1: 56(84) bytes of data.

--- 192.168.0.118 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


Above is the problem.

Try this.  ssh into SUT, see what the ip address for enp53s0f1 is, go into the LTS web ui, remove any SUT associated, add that ip address you found for enp53s0f1, and run the ethernet test you tried to run on it.
Comment 5 Kyle IK Chen 2016-12-19 00:28:08 UTC 
Hi Brose,
We could get passed result with following network environment.
SUT Port1 connect to TestServer Port1 directly(Without any network device).
And following this configuration to test each port.