| 2017-02-23 20:32:22 |
Andreas Hasenack |
bug |
|
|
added bug |
| 2017-02-23 20:43:08 |
Chad Smith |
canonical-livepatch-client: importance |
Undecided |
Critical |
|
| 2017-02-23 20:43:10 |
Chad Smith |
canonical-livepatch-client: status |
New |
Confirmed |
|
| 2017-02-23 20:52:10 |
Bryan Quigley |
bug |
|
|
added subscriber Canonical Support |
| 2017-02-23 20:52:28 |
Bryan Quigley |
bug |
|
|
added subscriber Bryan Quigley |
| 2017-02-23 20:53:07 |
Paul Collins |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2017-02-23 20:54:59 |
Andreas Hasenack |
description |
A fresh install of livepatch on an updated xenial ubuntu machine doesn't recognize it and refuses to start:
Feb 23 20:01:09 node-6 /usr/bin/snap[25852]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 23 20:01:09 node-6 snap[25852]: 2017/02/23 20:01:09 Only Ubuntu 16.04 LTS is supported, exiting.
Some debugging showed that /usr/bin/lsb_release doesn't exist in the latest core snap (see https://bugs.launchpad.net/snappy/+bug/1619420 and comments #11 and #14). livepatch uses that to determine if it can be used or not.
Existing systems that upgraded to that core snap don't exhibit the problem, we are not entirely sure why. Looks like livepatch in those cases is still seeing the old core snap, even though it was disabled. But if these systems reboot, livepatch stops working. |
A fresh install of livepatch on an updated xenial ubuntu machine doesn't recognize it and refuses to start:
Feb 23 20:01:09 node-6 /usr/bin/snap[25852]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 23 20:01:09 node-6 snap[25852]: 2017/02/23 20:01:09 Only Ubuntu 16.04 LTS is supported, exiting.
Some debugging showed that /usr/bin/lsb_release doesn't exist in the latest core snap (see https://bugs.launchpad.net/snappy/+bug/1619420 and comments #11 and #14). livepatch uses that to determine if it can be used or not.
Existing systems that upgraded to that core snap are not affected unless they reboot. |
|
| 2017-02-23 20:55:52 |
Andreas Hasenack |
description |
A fresh install of livepatch on an updated xenial ubuntu machine doesn't recognize it and refuses to start:
Feb 23 20:01:09 node-6 /usr/bin/snap[25852]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 23 20:01:09 node-6 snap[25852]: 2017/02/23 20:01:09 Only Ubuntu 16.04 LTS is supported, exiting.
Some debugging showed that /usr/bin/lsb_release doesn't exist in the latest core snap (see https://bugs.launchpad.net/snappy/+bug/1619420 and comments #11 and #14). livepatch uses that to determine if it can be used or not.
Existing systems that upgraded to that core snap are not affected unless they reboot. |
A fresh install of livepatch on an updated xenial ubuntu machine doesn't recognize it and refuses to start:
Feb 23 20:01:09 node-6 /usr/bin/snap[25852]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 23 20:01:09 node-6 snap[25852]: 2017/02/23 20:01:09 Only Ubuntu 16.04 LTS is supported, exiting.
Some debugging showed that /usr/bin/lsb_release doesn't exist in the latest core snap (see https://bugs.launchpad.net/snappy/+bug/1619420 and comments #11 and #14). livepatch uses that to determine if it can be used or not. Without it, it fails and shows that error message about not running on xenial.
Existing systems that upgraded to that core snap are not affected unless they reboot. |
|
| 2017-02-23 21:01:26 |
Andreas Hasenack |
description |
A fresh install of livepatch on an updated xenial ubuntu machine doesn't recognize it and refuses to start:
Feb 23 20:01:09 node-6 /usr/bin/snap[25852]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 23 20:01:09 node-6 snap[25852]: 2017/02/23 20:01:09 Only Ubuntu 16.04 LTS is supported, exiting.
Some debugging showed that /usr/bin/lsb_release doesn't exist in the latest core snap (see https://bugs.launchpad.net/snappy/+bug/1619420 and comments #11 and #14). livepatch uses that to determine if it can be used or not. Without it, it fails and shows that error message about not running on xenial.
Existing systems that upgraded to that core snap are not affected unless they reboot. |
A fresh install of livepatch on an updated xenial ubuntu machine doesn't recognize it and refuses to start:
Feb 23 20:01:09 node-6 /usr/bin/snap[25852]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 23 20:01:09 node-6 snap[25852]: 2017/02/23 20:01:09 Only Ubuntu 16.04 LTS is supported, exiting.
Some debugging showed that /usr/bin/lsb_release doesn't exist in the latest core snap (see https://bugs.launchpad.net/snappy/+bug/1619420 and comments #11 and #14). livepatch uses that to determine if it can be used or not. Without it, it fails and shows that error message about not running on xenial.
Existing systems that upgraded to that core snap are not affected unless they reboot. If they reboot, they can "snap revert core" and reboot one more time to restore livepatch functionality by using the old core snap. |
|
| 2017-02-23 21:02:30 |
Andreas Hasenack |
description |
A fresh install of livepatch on an updated xenial ubuntu machine doesn't recognize it and refuses to start:
Feb 23 20:01:09 node-6 /usr/bin/snap[25852]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 23 20:01:09 node-6 snap[25852]: 2017/02/23 20:01:09 Only Ubuntu 16.04 LTS is supported, exiting.
Some debugging showed that /usr/bin/lsb_release doesn't exist in the latest core snap (see https://bugs.launchpad.net/snappy/+bug/1619420 and comments #11 and #14). livepatch uses that to determine if it can be used or not. Without it, it fails and shows that error message about not running on xenial.
Existing systems that upgraded to that core snap are not affected unless they reboot. If they reboot, they can "snap revert core" and reboot one more time to restore livepatch functionality by using the old core snap. |
A fresh install of livepatch on an updated xenial ubuntu machine doesn't recognize it and refuses to start:
Feb 23 20:01:09 node-6 /usr/bin/snap[25852]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 23 20:01:09 node-6 snap[25852]: 2017/02/23 20:01:09 Only Ubuntu 16.04 LTS is supported, exiting.
Some debugging showed that /usr/bin/lsb_release doesn't exist in the latest core snap (see https://bugs.launchpad.net/snappy/+bug/1619420 and comments #11 and #14). livepatch uses that to determine if it can be used or not. Without it, it fails and shows that error message about not running on xenial.
Existing systems that upgraded to that core snap are not affected unless they reboot. If they reboot, they can "snap revert core" and reboot one more time to restore livepatch functionality by using the old core snap. Probably not a very useful workaround since the goal of livepatch is to prevent reboots, but hey :) |
|
| 2017-02-23 21:22:28 |
Chad Smith |
canonical-livepatch-client: assignee |
|
Chad Smith (chad.smith) |
|
| 2017-02-23 22:48:52 |
Haw Loeung |
bug |
|
|
added subscriber Haw Loeung |
| 2017-02-24 02:06:25 |
David Britton |
canonical-livepatch-client: status |
Confirmed |
In Progress |
|
| 2017-02-24 02:06:31 |
David Britton |
information type |
Proprietary |
Public |
|
| 2017-02-24 11:47:28 |
Zygmunt Krynicki |
bug task added |
|
snap-confine |
|
| 2017-02-24 11:47:32 |
Zygmunt Krynicki |
snap-confine: assignee |
|
Zygmunt Krynicki (zyga) |
|
| 2017-02-24 11:47:35 |
Zygmunt Krynicki |
snap-confine: status |
New |
Confirmed |
|
| 2017-02-24 18:10:04 |
Adam Collard |
bug |
|
|
added subscriber Adam Collard |
| 2017-02-24 18:12:13 |
Chad Smith |
canonical-livepatch-client: status |
In Progress |
Fix Committed |
|
| 2017-02-24 19:16:36 |
Chad Smith |
canonical-livepatch-client: status |
Fix Committed |
Fix Released |
|
| 2017-02-27 16:17:49 |
Zygmunt Krynicki |
snap-confine: status |
Confirmed |
In Progress |
|
| 2017-06-06 20:53:42 |
Amr Ibrahim |
snap-confine: status |
In Progress |
Fix Released |
|
