Comment 8 for bug 1977493

On Fri, Jun 03, 2022 at 03:58:24PM -0000, Frank Heimes wrote:

> Fwiw - I just took the system that I used for the description above and
> did a 'do-release-upgrade' and it work fine

Yes, this problem only occurs because the submitter has references to the
obsolete pam_tally module in their config and PAM blocks the upgrade to
prevent the user from having a broken config after upgrade (and potentially
be locked out of administering the system to fix it). It will not happen on
a system with a stock config.

It is unfortunately not safe for us to automatically edit the configs to
remove references to pam_tally on upgrade, as this may also result in an
admin lock-out.