Comment 10 for bug 1353008

Let's keep in mind the way juju creates containers: first, it creates a template container. Then, it clones it.

From the cloud init logs, I can't see cloud-init from the cloned container waiting 120s for an IP. In fact, doesn't look like it waited even 60s.

- template container ends: Cloud-init v. 0.7.5 finished at Mon, 04 Aug 2014 23:56:18
- cloned container starts: Cloud-init v. 0.7.5 running 'init' at Mon, 04 Aug 2014 23:57:12
- cloned container fails at, or before: Cloud-init v. 0.7.5 running 'modules:config' at Mon, 04 Aug 2014 23:57:12
- dhcp server gets a lease request, offers it, and the container ACKs it: all within this second: 23:57:13