cannot disable livepatch when /etc/lsb-release is edited

[Jingkai Wang]

I use the wechat program which will detect whether the system is "Kylin", if not, the program cannot run correctly. So I modify the /etc/lsb-release and then the wechat program could use normally. However, I cannot use Ubuntu Pro livepatch because it says “livepatchd error: The platform Kylin V10 is not supported. exiting.”

Then I re-modified the /etc/lsb-release and try to re-install livepatch, but failed.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 32.3~22.04
ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 30 16:45:42 2024
InstallationDate: Installed on 2024-04-23 (37 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
PackageArchitecture: all
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
cloud-id.txt-error: Invalid command specified 'cloud-id'.
jobs-status.json: {"metering": {"last_run": "2024-05-30T08:28:05.567778+00:00", "next_run": "2024-05-30T12:28:05.567778+00:00"}, "update_contract_info": null, "update_messaging": {"last_run": "2024-05-30T08:28:05.567778+00:00", "next_run": "2024-05-30T14:28:05.567778+00:00"}}
livepatch-status.txt-error: Failed running command '/snap/bin/canonical-livepatch status' [exit(1)]. Message: error executing status: open /var/snap/canonical-livepatch/278/livepatchd.err: permission denied
uaclient.conf:
 contract_url: https://contracts.canonical.com
 log_level: debug

[Renan Rodrigo (renanrodrigo)]

Hello, jkwang28, thanks for reporting this bug.

Livepatch seems to be relying on the output of /etc/lsb-release to verify compatibility on all operations (including disable/status/etc). I would say editing /etc/lsb-release or /etc/os-release is not something supported from the Pro side.

I see the report says you are using Ubuntu Jammy Jellyfish (22.04). If that is the case, and the /etc/lsb-release was edited back to the original content, then Livepatch should work fine.

Can you please confirm the content of /etc/lsb-release now, and the output you see when disabling/enabling Livepatch again?