Public bug reported:
cloud-init creates /etc/netplan/50-cloud-init.yaml during its network
configuration step.
However, "apt purge cloud-init" leaves this file intact.
I've seen this behavior on Ubuntu 18, 20, and 22.
I can always remove the file manually, but I'm left wondering what other
files cloud-init might have left lingering around on the system.
Shouldn't a purge remove all files associated with a package?
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
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 network configuration files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1975744/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
