do-release-upgrade fails if ESM enabled

I have the exact same problem. I have attached a screenshot of the message that I received.

Unfortunately, I am not skilled with computers and could not understand your work around. Can you please detail it a bit more. What file did you change and how? Where can I find this file?

Much obliged.

Hi Thomas Mustafa, and the Ubuntu Team,

Exactly the same issue

This solution is here (worked for me) : https://ubuntu.com/pro/beta#
A Ubuntu Pro account has been open but any service.

Create a service (free) for this desktop.

And enjoy your 22.04 upgrade :)

See this: https://askubuntu.com/questions/1437617/22-04-upgrade-could-not-download-the-upgrades-unauthorized-ip-200167c1
thank you Thomas Ward :).

José from France.

Status changed to 'Confirmed' because the bug affects multiple users.

I got the same 401 errors running apt-get upgrade from 18.04

The following packages will be upgraded:
  libnghttp2-14 libpython2.7 libpython2.7-dev libpython2.7-minimal
  libpython2.7-stdlib libpython3.6 libpython3.6-dev libpython3.6-minimal
  libpython3.6-stdlib python2.7 python2.7-dev python2.7-minimal python3.6
  python3.6-dev python3.6-minimal python3.6-venv sysstat vim vim-common
  vim-runtime vim-tiny xxd
...
E: Failed to fetch https://esm.ubuntu.com/infra/ubuntu/pool/main/s/sysstat/sysstat_11.6.1-1ubuntu0.2+esm1_amd64.deb 401 Unauthorized [IP: 91.189.91.47 443]

ran pro disable esm-infra

ran apt-get upgrade, saw that it no longer listed those packages.

ran pro enable esm-infra

ran apt-get upgrade, and now it is downloading the packages in question.

Note that I have not rebooted since adding the free Ubuntu Pro token.

This confuses me from the u-r-u/apt perspective because either the system is enrolled and the sources are there or it's not and the sources shouldn't be there.

Adding an ubuntu-advantage-tools task for further investigation and marking ubuntu-release-upgrader as Incomplete

Thanks Julian for the redirect
We do have upgrade-related integration tests in place and passing for all releases, so this seems indeed a non-catched bug. Will investigate further.

I cannot reproduce this issue - I have executed upgrades ( X -> B -> F -> J ) with all esm services enabled and all worked.

From a theoretical perspective, 401s should be there only if the esm credentials are invalid. Note that apt update will work, as only the packages themselves need the auth to work to be accessed.

I will try it out on desktop though, to see if there is any problem or discrepance.

To further investigate, it would be nice to have some logs from our side to look at. Anyone having this problem could please run `pro collect-logs` and attach the resulting tarball?

Tried desktop, F-> J works fine

Is it possible to check if those packages existed at the time this was logged?

What happens if a package is missing? Does it still give 401 and fail?

I can't do either of those myself.

Hi kennybobs,

I don't think the 401 are related to missing packages. It seems that your issue is related to
the esm-apps APT source file being present, but not together with its associated preference file.

However, as is, we cannot reproduce this issue and we would need the logs renanrodrigo mentioned to better investigate why this happened in the first place