detached ua key and and attached back, now on extensive security maintenance until 31/12/9999

[Thierry Scalcon Gonçalves Basseto]

I have detached Ubuntu Advantage key and attached again, to make livepatch work. When I realized the updates tab changed to Extensive Security Maintenance until 31/12/9999 (essentially until Y10K)

I tried re-opening the app, didn't work. Restarted the PC, didn't work. A partial upgrade, didn't work. I have a screenshot, it has been attached.

Ubuntu Release: 22.04
Version of software-properties-gtk: 0.99.22.2
What I expected to happen: Livepatch working again, on the free subscription of LTS until 2027.
What happened instead: Somehow got support until 31/12/9999 (again, Y10K.)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.22.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 17 19:03:59 2022
InstallationDate: Installed on 2022-06-14 (2 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for your bug report. The information displayed there is indeed incorrect, it is using the value returned by

$ ua status --format=json

so reassing to this component

[Renan Rodrigo (renanrodrigo)]

Hello Thierry, thanks for reporting it.

1 - Livepatch should be on Jammy, showing as enabled but with no patches available yet. This is the output I get here:
```
user@ubuntu-jammy:~$ canonical-livepatch status
last check: 58 minutes ago
kernel: 5.15.0-39.42-generic
server check-in: succeeded
patch state: ✓ no livepatches needed for this kernel yet
tier: stable

```

2 - When you need to update contract definitions for any reason, you can run `sudo ua refresh`, and then there is no need to detach/reattach.

3 (and finally to this bug's point...) This is expected if you are using a free UA subscription. Those should not expire at all, and year 9999 just implies that.

`ua status --format=json` is returning `expires` as the expiry date for the contract, and I think the problem here is that while the contract does not expire, there are the LTS + ESM support dates, which should be taken into consideration on the UI.

You do have the support until LTS ends, plus the ESM support, given that you are attached to a valid token.

I reassigning the bug back - What can be done there is that the UI says that the subscription is valid until that date, or present the ESM expected support date instead of the contract expiry from ua status.