Comment 15 for bug 2012689

Now we're seeing strange behaviour when starting new nodes - no arguments are passed to the kubelet args file and we are seeing cloud-init errors (look at screenshots).
But this time I can say that we only see this behaviour on our AMIs that use your AMI as a source and have some additional installations by Packer (I didn't change anything in the packer templates).
It looks like the problem now is a combination of your final fix and our use of Packer. Maybe I should add some delays to Packer scripts?