I like the idea of working this into cloud-init clean.
My use case is that I use cloud-init to initially configure an instance
that will later be manually configured, so I don't want files lying around
that say things like "if you edit this file it will be overwritten on the
next boot" (I forget
Thanks for the bug and triage folks.
While this is confirmed/known behavior, I don't think cloud-init should
be automatically removing core configuration files that are not packaged
by cloud-init's deb package especially if removal of those config files
can have catastrophic consequences on the
Reproduced with:
```sh
$ lxc launch ubuntu:jammy jj
$ lxc exec jj -- cloud-init status --wait
$ lxc exec jj -- cloud-init --version
/usr/bin/cloud-init 22.1-14-g2e17a0d6-0ubuntu1~22.04.5
$ lxc exec jj -- apt purge -y cloud-init
...
dpkg: warning: while removing cloud-init, directory '/etc/cloud'
It also seems to leave build.info in /etc/cloud and doesn't remove that
directory for that reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975744
Title:
purging cloud-init doesn't remove its
