usb ethernet dongle device name be truncated then commission failed

[Alex Tu]

When using usb ethernet dongle, the device will truncated and cause failure on commission.

MaaS version:
 - 2.3.0-6434-gd354690-0ubuntu1~16.04.1

dongle:
 - BROWAY BW-L1069A (realtek rtl8153)
 - this issue not only happens to this dongle but all ethernet dongle which has long name string.

00-maas-01-lshw:

   <logicalname>enx00e04c7003c5</logicalname>

00-maas-05-dhcp-unconfigured-ifaces:

Device "enx00e04" does not exist.
Traceback (most recent call last):
  File "/tmp/user_data.sh.M5ccSz/scripts/commissioning/00-maas-05-dhcp-unconfigured-ifaces", line 61, in <module>
    dhcp_explore(*args, **kwargs)
  File "/tmp/user_data.sh.M5ccSz/scripts/commissioning/00-maas-05-dhcp-unconfigured-ifaces", line 36, in dhcp_explore
    iface for iface in configured_ifaces if has_ipv4_address(iface)]
  File "/tmp/user_data.sh.M5ccSz/scripts/commissioning/00-maas-05-dhcp-unconfigured-ifaces", line 36, in <listcomp>
    iface for iface in configured_ifaces if has_ipv4_address(iface)]
  File "/tmp/user_data.sh.M5ccSz/scripts/commissioning/00-maas-05-dhcp-unconfigured-ifaces", line 15, in has_ipv4_address
    output = check_output(('ip', '-4', 'addr', 'list', 'dev', iface))
  File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
    **kwargs).stdout
  File "/usr/lib/python3.6/subprocess.py", line 418, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '('ip', '-4', 'addr', 'list', 'dev', b'enx00e04')' returned non-zero exit status 1.

[Alex Tu (alextu)]

$dpkg -l '*maas*'|cat

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================================-============-=================================================
ii maas 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)

[Andres Rodriguez (andreserl)]

Hi There,

I believe this issue has already been fixed in the latest releases of MAAS. AS such, I'd recommend you upgrade to MAAS 2.3.5, which is the latest 2.3 available.

On the other hand, for information, this issue is not just MAAS but an overall issue with older versions of Ubuntu: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744

[Andres Rodriguez (andreserl)]

FWIW< i believe this was fixed on 2.3.3:

https://bugs.launchpad.net/maas/+bug/1759284

[Rex Tsai (chihchun)]

@alextu please double check if this is still an issue for OEM team.