find_ip_via_arp() results in unpredictable, and in some cases, incorrect IP addresses

MAAS was changed recently to have the AMT power template require MAC addresses rather than IP addresses, in that there is a race condition, when AMT is expecting DHCP to provide an address, and the MAAS DHCP server may not be running yet.

The solution was to create a function, find_ip_via_arp() in src/provisioningserver/utils/__init__.py that resolves MAC addresses to IP addresses.

Unfortunately, the output of this function is somewhat unpredictable, particularly in a MAC address resolves to multiple IP addresses.

That's easily reproducible, if you set AMT to use a static IP address, while the OS running on the system draws its own DHCP address from MAAS. In this case, there are actually multiple MAC addresses with the same IP address.

To at least provide consistent results by this function, I strongly recommend that this code sorts the results, so that the lowest IP address is returned. While not perfect, it's at least predictable, and we can work with that.

=== modified file 'src/provisioningserver/utils/__init__.py'
--- src/provisioningserver/utils/__init__.py 2014-03-28 15:23:38 +0000
+++ src/provisioningserver/utils/__init__.py 2014-04-14 22:14:09 +0000
@@ -819,7 +819,7 @@

     output = call_capture_and_check(['arp', '-n']).split('\n')

- for line in output:
+ for line in sorted(output):
         columns = line.split()
         if len(columns) == 5 and columns[2] == mac:
             return columns[0]