Comment 0 for bug 1543063

it's expected that 'write_files' will be executed at the very end of cloud-init and it must be likely the last module to be executed by cloud-init. At least, it shall be executed before 'runcmd'

cloud-init modules will be executed by the order they were defined in cloud.cfg:
Eg. http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/config/cloud.cfg

having 'write_files' processed before 'runcmd' could indicate a node to be completely provisioned while it's not true. 'runcmd' could be executed and interfere with the first tasks of granular deployment.

in other words, this is the root cause of https://bugs.launchpad.net/fuel/+bug/1536924

provided fix for #1536924 only mitigates the issue.