A run of 'sudo cloud-init collect-logs' should create a cloud-init.tar.gz in your current working directory that could be attached to this bug. It'd give us the logs and config files that would aid triage in this case so we can see why cloud-init thought it should overwrite this file.
A run of 'sudo cloud-init collect-logs' should create a cloud-init.tar.gz in your current working directory that could be attached to this bug. It'd give us the logs and config files that would aid triage in this case so we can see why cloud-init thought it should overwrite this file.