Comment 14 for bug 2038648

(comment #12)
> IMHO we first should understand the issue/criteria for reproducing the problem;
> so I'd wait for Branimir to reply, or we try proactively to reproduce the issue,
> e.g., should pro not be enabled? (there are no 'esm' versions in attached logs.)

I tried to reproduce this scenario too (or close to it): launched 16.04 Pro VM in GCP and downgraded the packages with 'esm' version suffix to the version in xenial-updates (this changes package status, so might not reflect the reporter's environment), then do-release-upgrade.

The issue didn't reproduce.

$ grep -A1 'Setting up sosreport' /var/log/dist-upgrade/apt-term.log
Setting up sosreport (4.4-1ubuntu0.18.04.1) ...
Setting up xfsprogs (4.9.0+nmu1ubuntu2) ...