[IEC-48] [IEC][SEBA] CI tests failing sporadically with DHCP failure Created: 11/Jun/20 Updated: 23/Jun/20 Resolved: 23/Jun/20 |
|
| Status: | Done |
| Project: | Integrated Edge Cloud |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Catalin Iova | Assignee: | Catalin Iova |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
There are sporadic tests failures on CI integration during "Validate DHCP and Ping" test, e.g.: https://jenkins.akraino.org/view/iec/job/iec-type2-test-seba_on_arm-fuel-baremetal-ubuntu1804-daily-master/43/console |
| Comments |
| Comment by Catalin Iova [ 11/Jun/20 ] |
|
The "Validate DHCP and Ping" test is sporadically failing due to DHCP timeout. Sometimes it takes longer than 30 seconds to get an IP (e.g. 36 seconds). The robot test is changing the DHCP timeout parameter from 300 to 30 into "Send Dhclient Request K8S" test procedure before running the dhclient into the RG container. The timeout value 300 has to be changed since the "Validate DHCP and Ping" is waiting 90 seconds for the IP. The fix consist in changing "Send Dhclient Request K8S" test so that dhcp timeouts after 80 seconds, value which is lower than 90 seconds and greater than maximum observed DHCP IP address assignment. Fix pushed into github: https://github.com/iecedge/cord-tester/commit/19b93cc71efc0bf7a84d258bae730e65c5f7f212 |