ec2-init: Move wait for network to top level
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
EC2 init scripts |
Fix Released
|
Undecided
|
Unassigned | ||
Ubuntu on EC2 |
Fix Released
|
High
|
Unassigned |
Bug Description
For a while now, I've been recommending that the "wait for network" code be moved out of /usr/sbin/
I've finally found a bug which is caused by this.
When a running instance is rebundled as a new image and the new image is run as a new instance, the new instance does not wait for the network and may fail to install the public ssh keys correctly, preventing access to the instance. See also bug #308530.
This happens because the call to ec2-set-defaults is inside of a "run once ever" check so the "wait for network" requirement is not run on the new instance of the rebundled image.
This problem may not show up on every instance start as the network may be available more quickly sometimes but not others.
I propose creating a new /usr/sbin/
Related branches
Changed in ubuntu-on-ec2: | |
status: | New → Confirmed |
importance: | Undecided → High |
I believe the fix incorporated for bug 308530 (present in karmic/ 20090811. 2/ubuntu- ec2-karmic- amd64.img. gz) should address your concerns that were listed above. In short, the /etc/init. d/ec2-init script now runs ec2-wait- for-meta- data-service before doing anything else in 'start'. and that program will block until meta-data service is up.
Please re-open if you believe this isn't fixed.