Comment 2 for bug 1476612

However I found a possible issue with metadata:

By default we're creating a router-plugged network with a subnet with /22 prefix, having 2 IP allocation pools.
I see that for some reason the subnet has gateway ip being the first one of the _second_ pool while dnsmasq is providing a route to 169.254 via a gateway ip being the first ip of the first interval.
It was like if gateway ip address was changed.

Restart of DHCP agent however seems to fix this.

Initial state might have resulted in inability to get metadata.