Traceback in Network script due to unknown MII Tool failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Fix Released
|
High
|
Maciej Kisielewski |
Bug Description
Discovered at a partner lab. Something happened with mii-tool causing it a traceback in th network script:
WARNING:root:test server 192.168.0.5 (192.168.0.5) is NOT
WARNING:root:within 172.16.0.0/22; skipping
ERROR:root:mii-tool returned an error!
ERROR:root:
Traceback (most recent call last):
File "/tmp/nest-
sys.
File "/tmp/nest-
return args.func(args)
File "/tmp/nest-
error_number = run_test(args, test_target)
File "/tmp/nest-
error_number = iperf_benchmark
File "/tmp/nest-
if self.iface.
File "/tmp/nest-
for line in filter(lambda l: 'capabilities' in l, info):
UnboundLocalError: local variable 'info' referenced before assignment
I do not currently have more information than this though. I "think" it may be that a device was up but not configured correctly... perhaps.
Related branches
- Sylvain Pineau: Approve
-
Diff: 71 lines (+37/-20)1 file modifiedbin/network (+37/-20)
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Fix Committed |
milestone: | none → 0.35.0 |
Changed in plainbox-provider-checkbox: | |
status: | Fix Committed → Fix Released |
1) network shouldn't crash on mii-tool returning rubbish - clearly my mistake with the surrounding python code
2) from what I've read on the web mii-tool can fail on some NICs :[ I plan to bring back ethtool and fall back to mii-tool if it's not available (/me glances at ubuntu core).