16.04 Server with Canonical Livepatch Service requires restart - Ask Ubuntu

i'm no means sysadmin, maybe simple oversight. isn't whole point of livepatch service prevent mission-critical servers having restart after kernel update?

livepatch on google cloud compute server in question has been installed since october 18th. before installing livepatch service, performed 1 last restart.

this i'm presented upon login:

login as: ubuntu authenticating public key "key" agent welcome ubuntu 16.04.1 lts (gnu/linux 4.4.0-45-generic x86_64)   * documentation:  https://help.ubuntu.com  * management:     https://landscape.canonical.com  * support:        https://ubuntu.com/advantage  cloud support ubuntu advantage cloud guest:   http://www.ubuntu.com/business/services/cloud  1 package can updated. 0 updates security updates.  *** system restart required *** last login: tue nov  1 09:57:46 2016 x.x.x.x 

if check status of livepatch service, looks fine:

ubuntu@server:~$ canonical-livepatch status kernel: 4.4.0-45.66-generic fully-patched: true version: "" 

anything else need doing prevent these required restarts? there other packages need full restart? packages managed through ubuntu's own package manager.

here can find lengthy faq ubuntu live patch: http://blog.dustinkirkland.com/2016/10/canonical-livepatch.html copied questions of interest you:

q: kinds of updates provided canonical livepatch service?

a: canonical livepatch service intended address high , critical severity linux kernel security vulnerabilities, identified ubuntu security notices , cve database. note there limitations kernel livepatch technology -- linux kernel code paths cannot safely patched while running. our best supply canonical livepatches high , critical vulnerabilities in timely fashion whenever possible. there may occasions when traditional kernel upgrade , reboot might still necessary. we’ll communicate through usual mechanisms -- usns, landscape, desktop notifications, byobu, /etc/motd, etc.

q: non-security bug fixes, stability, performance, or hardware enablement updates?

a: canonical continue provide linux kernel updates addressing bugs, stability issues, performance problems, , hardware compatibility on our usual cadence -- every 3 weeks. these updates can applied using ‘sudo apt update; sudo apt upgrade -y’, using desktop “software updates” application, or landscape systems management. these standard (non-security) updates still require reboot, have.