ok I can reproduce with just this shell script. The weird thing is, it only reproduces if I watch the log and kill the container after it fully boots.
cloud init will report that it is done booting like this:
cloud-init boot finished at Fri, 05 Oct 2012 20:15:32 +0000. Up 200.15 seconds
if you run the script, and wait until you see that message, then press enter, which triggers stop/destroy, the bug will reproduce on 3.6.0 upstream kernel [1] as well as quantal's
ok I can reproduce with just this shell script. The weird thing is, it only reproduces if I watch the log and kill the container after it fully boots.
cloud init will report that it is done booting like this:
cloud-init boot finished at Fri, 05 Oct 2012 20:15:32 +0000. Up 200.15 seconds
if you run the script, and wait until you see that message, then press enter, which triggers stop/destroy, the bug will reproduce on 3.6.0 upstream kernel [1] as well as quantal's
[1] http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.6-quantal/