Reading the pull link in comment #3 and the conversation linked to from that in turn: https://github.com/canonical/cloud-init/pull/4298 It looks like this fix got reverted because of personnel policy (user committing the fix wasn't allowed to make packaging changes at the time, or similar). So even though 23.3 finally got released two weeks ago, this fix isn't listed in the release notes for https://github.com/canonical/cloud-init/releases/tag/23.3 and doesn't seem to have made it in.
So, other sysadmins: for now you'll still need to clean up the directories manually to avoid the otherwise harmless warnings from dpkg. This fix will be committed eventually once Canonical's paperwork catches up.
Status a month later:
Reading the pull link in comment #3 and the conversation linked to from that in turn: https:/ /github. com/canonical/ cloud-init/ pull/4298 It looks like this fix got reverted because of personnel policy (user committing the fix wasn't allowed to make packaging changes at the time, or similar). So even though 23.3 finally got released two weeks ago, this fix isn't listed in the release notes for https:/ /github. com/canonical/ cloud-init/ releases/ tag/23. 3 and doesn't seem to have made it in.
So, other sysadmins: for now you'll still need to clean up the directories manually to avoid the otherwise harmless warnings from dpkg. This fix will be committed eventually once Canonical's paperwork catches up.