ec2-run-user-data should be run after ec2-fetch-credentials
Bug #308533 reported by
Eric Hammond
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on EC2 |
Fix Released
|
Undecided
|
Unassigned | ||
Beta2 |
Invalid
|
Undecided
|
Chuck Short | ||
VMBuilder |
Invalid
|
Undecided
|
Unassigned | ||
ec2-init (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
AMI: ami-814aaee8 (official Ubuntu 8.10 Intrepid 32-bit beta AMI)
In the script
/etc/
it first calls
ec2-run-user-data
then
ec2-fetch-
The order of these should be reversed (first fetch ssh credentials, then run user-data).
The user-data script may take a long time to run (tens of minutes, an hour, or even forever if it has a bug in it) and the current order prevents the user from being able to ssh in to the instance until the script has completed.
This bug was fixed in the package ec2-init - 0.2
---------------
ec2-init (0.2) jaunty; urgency=low
* debian/init: Run fetch-credentials before anything else. hostname. py: Queries ec2 metdada for public-hostname
(LP: #308533)
* Add ec2-set-
and then sets it (LP: #316201)
-- Chuck Short <email address hidden> Tue, 13 Jan 2009 15:20:21 -0500