Comment 6 for bug 2039234

I'm realizing that I didn't try to reproduce this. After doing so in a container, the issue didn't present itself, presumably because ubuntu-release-upgrader actually uses --force-overwrite by default precisely to avoid these issues.

May I ask how exactly you tried to upgrade?