Using Cloud-Init Support manual.
After update, creating new instances from template does not clone cloud-init disk. This leads to the fact that a new instance is not operational.
The workaround for this problem is to re-create the Cloud Init disk on each new instance.
BTW, is it bug or feature?