Hide Forgot
Description of problem: During the cert run, the Ethernet tests fails. The report states it cannot bounch the port, then fails the ping - Checking installed rpms: ethtool-4.5-3.el7.x86_64 All required packages installed <output name="Setup" description="prepare for network testing"> Verifying rhcert Server None (150.166.33.200): rhcert-server Version 4.1 Release 20161031 IP address at server: 150.166.33.203 Status: running Network test verified for enp4s0f1 at 150.166.33.203 <summary data-value="PASS">PASS</summary> </output> <output name="Interface Configuration"> Shutting down interface enp4s0f1 interface enp4s0f1 is down Bringing up interface enp4s0f1 ifup enp4s0f1 returned 0 Interface enp4s0f1 is UP Checking via ping to 150.166.33.200... Error: could not ping test server 150.166.33.200 Error: could not bounce interface enp4s0f1 <summary data-value="FAIL">FAIL</summary> Version-Release number of selected component (if applicable): rhcert-server Version 4.1 Release 20161031 How reproducible: Both ports fail, even with clean install, switching to a different test server, and switching to a different switch. Steps to Reproduce: 1. After install of cert kit and reboot, start a cert run, select ethernet test. Actual results: See above. Additional info: The system is a C2112-4KL1 - an Intel(R) Xeon Phi(TM) CPU 7250 based platform running RHEL 7.3. Ethernet chip is - 04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
Created attachment 1223359 [details] C2112-4KL1 core cert run showing the failure. Note that this is the third clean install, just to insure everything was proper.
When you registered the SUT, did you use the ip address associated with the NIC and port you are trying to test?
No. Registering the SUT is using the main ip address of the system, the one associated with e*0. Given the test requires all interfaces on the same sub-net, the system is registered using the first interface. Almost always in my case this is - 150.166.33.202, the next interface becomes 150.166.33.203, the next 150.166.33.204, etc. I've recently upgraded the cert kit to 4.6 and see the almost the same results on a different system. The first interface passes, but all other interfaces fail. Here is the example from the latest run with cert kit 4.6: Checking installed rpms: ethtool-4.5-3.el7.x86_64 All required packages installed Verifying rhcert Server None (150.166.33.200): rhcert-server Version 4.6 Release 20170323 IP address at server: 150.166.33.202 Status: running Network test verified for enp1s0f0 at 150.166.33.202 Shutting down interface enp1s0f0 interface enp1s0f0 is down Bringing up interface enp1s0f0 ifup enp1s0f0 returned 0 Interface enp1s0f0 is UP Checking via ping to 150.166.33.200... ping -I 150.166.33.202 -Acl 150.166.33.200 > /dev/null done Shutting down all other network interfaces... enp1s0f1 Shutting down interface enp1s0f1 interface enp1s0f1 is down ens2 Shutting down interface ens2 interface ens2 is down waiting 10 sec...done interface speed is 10000 Mb/s ----- Checking installed rpms: ethtool-4.5-3.el7.x86_64 All required packages installed Verifying rhcert Server None (150.166.33.200): rhcert-server Version 4.6 Release 20170323 IP address at server: 150.166.33.202 Status: running Network test for enp1s0f1 failed verification: Error: Could not determine IP Address. ----- Checking installed rpms: ethtool-4.5-3.el7.x86_64 All required packages installed Verifying rhcert Server None (150.166.33.200): rhcert-server Version 4.6 Release 20170323 IP address at server: 150.166.33.202 Status: running Network test for ens2 failed verification: Error: Could not determine IP Address.