Network speed incorrectly detected as "-1"
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Certification Docs |
Fix Released
|
Medium
|
Jeff Lane | ||
| Checkbox Provider - Base |
Fix Released
|
Medium
|
Jeff Lane | ||
| Provider for Plainbox - Canonical Certification Server |
Fix Released
|
Medium
|
Jeff Lane | ||
Bug Description
In testing of the impending next Checkbox release, I've discovered a bug, and verified it exists in the current version (plainbox-
ERROR:root:Detected link speed (-1) is lower than detected max speed (1000)
ERROR:root:Check your device configuration and try again.
ERROR:root:If you want to override and test despite this under-speed link, use
ERROR:root:the --underspeed-ok option.
For more context and details, see:
https:/
All four NICs are connected to the network and have IP addresses. The fourth NIC (the first one listed, actually) passes its test fine.
Related branches
- Rod Smith: Approve
-
Diff: 12 lines (+1/-0)1 file modifieddebian/canonical-certification-server.install (+1/-0)
- Rod Smith: Approve
-
Diff: 75 lines (+45/-5)3 files modifiedlauncher/test-network-underspeed (+19/-0)
units/network-only-18.04.pxu (+1/-5)
units/network-only-underspeed.pxu (+25/-0)
- Rod Smith: Approve
-
Diff: 62 lines (+43/-0)2 files modifiedunits/ethernet/jobs.pxu (+19/-0)
units/ethernet/test-plan.pxu (+24/-0)
| Changed in plainbox-provider-checkbox: | |
| assignee: | nobody → Rod Smith (rodsmith) |
| Changed in plainbox-provider-checkbox: | |
| importance: | Undecided → Medium |
| Jeff Lane (bladernr) wrote | #1 |
| Changed in plainbox-provider-checkbox: | |
| assignee: | Rod Smith (rodsmith) → Jeff Lane (bladernr) |
| status: | New → In Progress |
| Changed in certification-docs: | |
| status: | New → In Progress |
| assignee: | nobody → Jeff Lane (bladernr) |
| importance: | Undecided → Medium |
| Changed in plainbox-provider-certification-server: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Jeff Lane (bladernr) |
| Changed in certification-docs: | |
| status: | In Progress → Fix Committed |
| Changed in plainbox-provider-certification-server: | |
| status: | In Progress → Fix Committed |
| Changed in plainbox-provider-checkbox: | |
| status: | In Progress → Fix Committed |
| Changed in certification-docs: | |
| status: | Fix Committed → Fix Released |
| Changed in plainbox-provider-certification-server: | |
| milestone: | none → 0.42.0 |
| Changed in plainbox-provider-checkbox: | |
| milestone: | none → 0.48.0 |
| Changed in plainbox-provider-checkbox: | |
| status: | Fix Committed → Fix Released |
| Changed in plainbox-provider-certification-server: | |
| status: | Fix Committed → Fix Released |
| tags: | added: servcert-285 |
This is a problem with how some drivers are reporting link speed via sysfs.
We check the speed entry in /sys/devices/
The network script is configured to cease testing on any link speed less than advertised max.
On OUR end, we need to change this to cease on any speed less max that is < 0.
For anything 0 or less, we should assume underspeed-ok and continue testing. but still fail the test run. This will trigger a review but give us usable test data to determine if we should accept the results anyway.