Remove needs update logic for SetUsbEthernetMacAddressSource
Remove logic that checks whether MAC address source property on USB Ethernet adapter must be updated. This logic is complicated and doesn't work very well. For example, 0. policy value for MAC address source is "designated_dock_mac" 1. device is not link up and has MAC address source property equals to "designated_dock_mac" 2. we send request to change MAC address source to "usb_adapter_mac" 3. device is link up, but MAC address source property hadn't been updated, so we update path to primary USB Ethernet adapter 4. device MAC address source property was updated to "usb_adapter_mac", but we see that primary USB Ethernet adapter didn't change and policy value is still the same. Here we have to verify that primary Ethernet adapter still has correct property. After applying this CL, each time there will be property value verification. Side effect of this CL is that we may send the same request to shill few times. In practice, it's only 2 requests. BUG=b:152425041 TEST=manual end-to-end TEST=existing unit tests Change-Id: I773aeff67d0aae9a2bb5e7172e3677dbd8a18141 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2150598 Commit-Queue: Oleh Lamzin <lamzin@google.com> Auto-Submit: Oleh Lamzin <lamzin@google.com> Reviewed-by:Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Pavol Marko <pmarko@chromium.org> Cr-Commit-Position: refs/heads/master@{#759619}
Showing
Please register or sign in to comment