syncronize-issues-to-jira[bot]
commented
9 months ago Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/CHECKBOX-1118.
This message was autogenerated
This issue was migrated from https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1910451
Summary
Description
Network devices must be connected to a network segment that is at or above their max line rate. As you know, a 10Gb controller has to be connected to a network of at least 10Gb/s capability (or faster).
There's a new crop of low-end NICs out there that are 2.5 and 5Gb ethernet.
https://certification.canonical.com/hardware/202012-28475/submission/191584/test/64025/result/15449384/
Settings for eno1: Supported ports: [ TP ] Supported link modes: 100baseT/Full 1000baseT/Full 2500baseT/Full 5000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 100baseT/Full 1000baseT/Full 2500baseT/Full 5000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: g Wake-on: d Link detected: yes
This advertises a 5Gb max speed, but was connected to a 1Gb network, and still passed the network stress test.
What SHOULD have happened is that the network test should have failed because 1GbE is too slow for a 5GbE NIC.
This NIC would need to be connected to a 10Gb Lan segment (I don't know if 5Gb switches exist) in order to be tested at the proper speed.
Need to figure out why the network test created a false positive here instead of failing this test case.
Attachments
No attachments
Tags: ['blocks-hwcert-server']