Comment 3 for bug 1979098

Revision history for this message
Renan Rodrigo (renanrodrigo) wrote (last edit ):

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.