Comment 10 for bug 1317197

I've proposed a fix for this on trunk; will backport if/when it is accepted.

Status updates are nice, and we should definitely do them, but that's a bigger kettle of fish. There's some complication with this at the moment, because the code that runs the host initialisation (for containers) runs outside the scope of the provisioner. The instance broker for each container type is created on-demand after container initialisation succeeds.

I haven't thought about it deeply about this, but I think it'd be simpler in general, and for status updates in particular, if the provisioner triggered off the host initialisation.