Ubuntu Server installer internal error when checking Pro subscription status

[Ken Sharp]

When installing both Ubuntu Server 18.04.6 and 20.04.6 from the live CD you are asked if you would like to attach to an Ubuntu Pro/Advantage subscription. In both cases an "Internal Error" occurs. 22.04.3 doesn't have this issue.

Video attached for 20.04.6.

[Lucas Albuquerque Medeiros de Moura (lamoura)]

Hi Ken,

Thanks for reporting this. I am also adding the subiquity team on the loop here, since they are the ones responsible for the installer. I will let them say how we should approach this issue.

[Olivier Gayot (ogayot)]

I just tested it on the focal ISO (after refreshing the installer to 23.10.1) and reproduced the error.

The logs show:

2024-01-22 18:02:19,796 DEBUG subiquitycore.utils:135 arun_command ('/snap/subiquity/5270/usr/bin/python3.10', '/snap/subiquity/5270/usr/bin/ubuntu-advantage', 'status', '--format', 'json', '--simulate-with-token', '<redacted>') exited with code 1
2024-01-22 18:02:19,796 DEBUG subiquity.server.ubuntu_advantage:261 error reported by u-a-c: None: Failed running command 'apt list --installed' [exit(1)]. Message: apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/subiquity/5270/usr/lib/x86_64-linux-gnu/libsystemd.so.0)
apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/subiquity/5270/usr/lib/x86_64-linux-gnu/libsystemd.so.0)
apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/subiquity/5270/usr/lib/x86_64-linux-gnu/libsystemd.so.0)
apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/core22/current/lib/x86_64-linux-gnu/libcap.so.2)

2024-01-22 18:02:19,796 DEBUG root:30 finish: subiquity/UbuntuPro/check_token_GET: SUCCESS: 200 {"status": "UNKNOWN_ERROR", "subscription": null}

[Olivier Gayot (ogayot)]

This also affects the invocation of sshd -T:

2024-01-22 18:02:22,216 DEBUG subiquitycore.utils:98 run_command ['sshd', '-T'] exited with code 1
2024-01-22 18:02:22,216 DEBUG subiquitycore.ssh:36 sshd -T failed "sshd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/subiquity/5270/usr/lib/x86_64-linux-gnu/libsystemd.so.0)\nsshd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/subiquity/5270/usr/lib/x86_64-linux-gnu/libsystemd.so.0)\nsshd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/subiquity/5270/usr/lib/x86_64-linux-gnu/libsystemd.so.0)\nsshd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/core22/current/lib/x86_64-linux-gnu/liblzma.so.5)\nsshd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/core22/current/lib/x86_64-linux-gnu/liblzma.so.5)\nsshd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/core22/current/lib/x86_64-linux-gnu/libcap.so.2)\nsshd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/core22/current/lib/x86_64-linux-gnu/libgcrypt.so.20)\nsshd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/core22/current/lib/x86_64-linux-gnu/libgpg-error.so.0)\nsshd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/core22/current/lib/x86_64-linux-gnu/libgpg-error.so.0)\n"

[Olivier Gayot (ogayot)]

It looks like the refreshed 23.10.1 subiquity snap runs with a LD_LIBRARY_PATH, whereas the 22.02.1 did not.

$ grep environment -A 2 /snap/subiquity/5270/meta/snap.yaml

environment:
  LD_LIBRARY_PATH: ${SNAP_LIBRARY_PATH}${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}:$SNAP/lib:$SNAP/usr/lib:$SNAP/lib/x86_64-linux-gnu:$SNAP/usr/lib/x86_64-linux-gnu
  PATH: $SNAP/usr/sbin:$SNAP/usr/bin:$SNAP/sbin:$SNAP/bin:$PATH

https://github.com/snapcore/snapcraft/issues/4187 seems relevant.

[Olivier Gayot (ogayot)]

Rebuilding the snap with the version of snapcraft 8.0.1 (currently on latest/stable) fixes the issue.

[Michael Hudson-Doyle (mwhudson)]

Is that something that is going to happen soon in the natural course of things or do we need to trigger a rebuild / republish explicitly for this?

[Renan Rodrigo (renanrodrigo)]

As the bug is not in the Pro Client, and the subiquity people are looking into it, I am marking it invalid for ubuntu-advantage-tools.