Comment 2 for bug 1759284

I have the same issue commissioning power9 system with MAAS version: 2.3.2 (6485-ge93e044-0ubuntu1~16.04.1), and is easily reproduced by commissioning dradis.maas on server teams's maas server.

Device "enP2p1s0" does not exist.
Traceback (most recent call last):
  File "/tmp/user_data.sh.nF9cl2/scripts/commissioning/00-maas-05-dhcp-unconfigured-ifaces", line 61, in <module>
    dhcp_explore(*args, **kwargs)
  File "/tmp/user_data.sh.nF9cl2/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.nF9cl2/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.nF9cl2/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'enP2p1s0')' returned non-zero exit status 1.

The correct interfaces it should look for are:
enP2p1s0f1
enP2p1s0f0
enP2p1s0f3
enP2p1s0f2

MAAS machine output yaml also lists the correct interface, so may be this is a regex error in the scripts?