Canonical Livepatch Client

  1. Bug #1852667
  2. Comment #2

Comment 2 for bug 1852667

Revision history for this message
Nobuto Murata (nobuto) wrote : Re: livepatch status is less user-friendly once kernel-upgrade-required "cannot send status to server: bad server status 403"

Nov 15 02:01:33 livepatch canonical-livepatch[7195]: error in livepatch check state: needs-check
Nov 15 02:01:33 livepatch canonical-livepatch[7195]: Checking with livepatch service.
Nov 15 02:01:34 livepatch canonical-livepatch[7195]: updating last-check
Nov 15 02:01:34 livepatch canonical-livepatch[7195]: touched last check
Nov 15 02:01:50 livepatch canonical-livepatch[7195]: Applying update 59.1 for 4.15.0-58.64-generic
Nov 15 02:02:01 livepatch canonical-livepatch[7195]: Applied patch version 59.1 to 4.15.0-58.64-generic
Nov 15 02:04:52 livepatch canonical-livepatch[7195]: Client.Check
Nov 15 02:04:52 livepatch canonical-livepatch[7195]: Checking with livepatch service.
Nov 15 02:04:54 livepatch canonical-livepatch[7195]: Module already inserted.
Nov 15 02:04:54 livepatch canonical-livepatch[7195]: during refresh: cannot check: cannot send status to server: bad server status 403 (URL: https://livepatch.canonical.com/api/machine/b7a6c33062c9427ab25dd5a95c9353bf): {"error": "Not checking for new patches based on reported livepatch state. State: kernel-upgrade-required"}
Nov 15 02:04:54 livepatch canonical-livepatch[7195]: error in livepatch check state: check-failed
Nov 15 02:05:02 livepatch canonical-livepatch[7195]: error in livepatch check state: check-failed