Comment 4 for bug 1747499

Actually, I think there's more to it. Here are some thoughts

1. The compelling use case for livepatch is in fact to minimize and control the need to reboot; this is what customers pay us for. For many of them, rebooting every 3 weeks is either impossible or at least very painful. Let's not lose sight of that.

2. The output of canonical-livepatch status clearly says when you are up to date and when a reboot is required. In other words, the client does know when all patches are applied, and alternatively, when it is time to reboot.

3. Every external tool we've had customers ask us (AWS Patch Manager, Azure Patch Management) looks at /var/run/reboot-required and uses that to decide whether to reboot or not.

The net effect of #3 is that canonical-livepatch is rendered useless, basically, because every 3 weeks everything needs to be rebooted. And it's a critical use case, so we do need to address this in order to retain value in the proposition.