installing cloud-init on a non-ec2/UEC server results in a 20 minute boot wait
Bug #635188 reported by
Clint Byrum
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: cloud-init
Normally nobody would install cloud-init, but if they accidentally do, the next time they reboot, they'll have to wait about 20 minutes for the system to be usable, as it will wait forever for the EC2 metadata provider.
A high priority debconf alert warning the user of this, and/or a lower default timeout, would probably be ideal.
Related branches
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
To post a comment you must log in.
I suggest ether
* The package depends on the ec2 kernel
* A warning at install happens that the user has to accept
* The init script actually detects if they are/are-not in the cloud