prepare-testbed times out - flag boot_finished not present

[Barry Warsaw]

On Raring, with r145, `bin/prepare-testbed amd64` seems to never exit. I see the countdown timer from 1620s before timeout to 0s, ending in "System failed to setup in 30 minutes. Aborting!"

[Jean-Baptiste Lallement (jibel)]

Thanks for your report.

I've seen that too with yesterday's builds. cloud-init module:final never starts even if installation finished correctly but couldn't figure why yet. Marking as confirmed.

[Jean-Baptiste Lallement (jibel)]

It seems to be a problem with cloud image 20130123. I retried this morning, the cloud-init module 'final' is correctly executed, the boot_finished flag is present and installation finish successfully.

I'll set the status to 'incomplete' and make sure this issue doesn't hide something else, the bug will expire otherwise.

[Jean-Baptiste Lallement (jibel)]

I think I understood what happened:
1. During the initial installation of the cloud image, the cloud-config script executes a dist-upgrade
2. Yesterday (2013.01.23) there was an update for upstart
3. Upstart has been upgraded during the initial setup of the image
4. This "deregistered" (sorry if it is not exactly the right term) the upstart service "cloud-final", which as consequence is never executed.

I'll close this report and will file a separate bug

[Jean-Baptiste Lallement (jibel)]

Closing a "Won't fix" as there is not much we can do at the auto-package-testing level

[Jean-Baptiste Lallement (jibel)]

I filed bug 1103881 to track this issue in cloud-init and upstart

[Barry Warsaw (barry)]

And today it worked! :)