subiquity calls probert's Storage.probe with incorrectly typed probe_types
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In https:/
2019-12-22 17:18:03,207 block-discover:74 starting probe
2019-12-22 17:18:03,317 probert.
2019-12-22 17:18:03,328 probert.
2019-12-22 17:18:08,223 block-discover:99 probing failed restricted=True
Traceback (most recent call last):
File "/snap/
storage = fut.result()
File "/snap/
return self.__get_result()
File "/snap/
raise self._exception
File "/snap/
result = self.fn(*self.args, **self.kwargs)
File "/snap/
lambda: self._bg_
File "/snap/
return self.prober.
File "/snap/
results = storage.
File "/snap/
to_probe = probe_types.
AttributeError: 'list' object has no attribute 'intersection'
2019-12-22 17:18:43,432 block-discover:86 ignoring result <Future at 0x7f646e9b3f60 state=finished returned dict> for timed out probe
AFAICT, this hasn't been fixed in master (but I've only examined GitHub to determine that, no testing has been performed).
We only call it with NoneType or Set =/ i fear something odd is happpening with argument passing that we do with switch to async.