Comment 2 for bug 1667470

Revision history for this message
Francis Ginther (fginther) wrote :

Confirmed failure can be observed with the livepatch-client system_test. I did have to tweak system-tests to get them working:

$ git diff
diff --git a/tests/system_test.go b/tests/system_test.go
index 72c8d36..7f34364 100644
--- a/tests/system_test.go
+++ b/tests/system_test.go
@@ -529,7 +529,7 @@ func init() {
        // Create test system
        Vm = SystemTest{Name: "livepatchd-vm", User: "ubuntu", Series: "xenial",
                Arch: "amd64", Flavor: "generic", PackageVersion: TestPackageVersion,
- KernelVersion: "4.4.0-21.37", KernelABI: "4.4.0-21"}
+ KernelVersion: "4.4.0-63.84", KernelABI: "4.4.0-63"}
        Vm.setup()
 }

The 4.4.0-21.37 kernel was failing to boot in the KVM.

The error in /var/log/syslog:
Feb 23 20:49:01 livepatchd-vm snap[1939]: 2017/02/23 20:49:01 Only Ubuntu 16.04 LTS is supported, exiting.
Feb 23 20:49:01 livepatchd-vm systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 20:49:01 livepatchd-vm systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Unit entered failed state.
Feb 23 20:49:01 livepatchd-vm systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Failed with result 'exit-code'.
Feb 23 20:49:01 livepatchd-vm systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Service hold-off time over, scheduling restart.
Feb 23 20:49:01 livepatchd-vm systemd[1]: Stopped Service for snap application canonical-livepatch.canonical-livepatchd.
Feb 23 20:49:01 livepatchd-vm systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Start request repeated too quickly.
Feb 23 20:49:01 livepatchd-vm systemd[1]: Failed to start Service for snap application canonical-livepatch.canonical-livepatchd.