[Bug 861866] Re: cloud-init-nonet does not wait for dhcp

[Scott Moser]

At the moment, cloud-init waits 60 seconds and gives up and goes on.

This is probably lower than it could be.  We picked the reasonably low
number for the case where someone installed cloud-init on their server
to avoid it blocking their boot.

At this point, after bug 838968 and bug 847782, if they're misconfigured they're waiting at least 2 minutes for boot.
So I think it makes sense to double cloud-init's timeout to be 120 seconds also.


** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init
       Status: New => Triaged

** Changed in: cloud-init
     Assignee: (unassigned) => Scott Moser (smoser)

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu)
       Status: New => Triaged

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu)
     Assignee: (unassigned) => Scott Moser (smoser)

** Changed in: cloud-init (Ubuntu)
    Milestone: None => ubuntu-11.10

** Tags added: server-o-rs

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/861866

Title:
  cloud-init-nonet does not wait for dhcp

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/861866/+subscriptions