Merge ~jocave/plainbox-provider-checkbox:ethernet-detect-testing into plainbox-provider-checkbox:master
Status: | Merged |
---|---|
Approved by: | Jonathan Cave |
Approved revision: | 8e6c4d9ec57f120df42f634a91d05722914e93da |
Merged at revision: | 62e8080b7d05d3e82328972f53e2b00c0cf8dbad |
Proposed branch: | ~jocave/plainbox-provider-checkbox:ethernet-detect-testing |
Merge into: | plainbox-provider-checkbox:master |
Diff against target: |
217 lines (+72/-71) 4 files modified
bin/network_device_info.py (+63/-68) units/ethernet/jobs.pxu (+4/-2) units/ethernet/manifest.pxu (+4/-0) units/info/jobs.pxu (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sylvain Pineau (community) | Approve | ||
Review via email: mp+363443@code.launchpad.net |
Description of the change
Bug #1815992 raised the question of how the ethernet/detect job should behave, specifically when the system is known to ship without any ethernet adapters.
Most detect jobs are written such that they fail if no devices belonging to their category are found. Expected presence of a device is typically indicated by the presence of a manifest entry. In this case the detect job merely reported information about devices found by udev and compared this to those found by network-manager expect in the case when network-manager wasnt present. The exact same task was repeated in the attachment job info/network_
These changes maintain behaviour of the info/network_
LGTM, +1 for the new manifest entry