Comment 2 for bug 1491594

@nobuto what i am seeing here is e.g.

With pool like:

  static: 10.0.0.2 -> 10.0.0.10
  dynamic: 10.0.0.11 -> 10.0.0.20

And one extra node with:

  name: node1
  sticky_ip_address:
    mac_address: "38:63:bb:43:19:dc"
    requested_address: 10.0.0.2

If you run maas-deployer and it will create the bootstrap vm first which, since it has not requested a sticky ip, will get allocated one by MAAS which in the above case will most probably be 10.0.0.2 so it will conflict with the address requested by node1. We can simply get round this by having the bootstrap node also request a sticky ip which it should do in any case since we never want its address to change.