Comment 16 for bug 2075968

> By providing a quirk if cloud-init gets included in an image that doesn't already contain cloud-init, we can prevent this pitfall by adding something like the following across upgrade.
>
> cat > /etc/cloud/cloud-init.disabled <<EOF
> Disabled by do-release-upgrade because cloud-init was pulled in as a `Recommends:` dependency during upgrade and should not be enabled by default
> EOF

Agreed, it seems like this is something that should be fixed external to cloud-init. Part of cloud-init's job is identifying if an instance is fresh (i.e. hasn't ran before on this instance), so it seems to be doing what it is supposed to do. It's just running in an environment where cloud-init wasn't supposed to do that.