Race with activating livepatch and configuring proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Livepatch Charm |
Fix Released
|
High
|
Barry Price |
Bug Description
Hi,
There are environments where proxies are needed in order for Livepatch to activate/enable. Unfortunately, there's a race condition as per logs below:
| 2018-04-04 14:22:35 INFO juju-log Activating canonical-livepatch with your key
| 2018-04-04 14:22:35 DEBUG install 2018/04/04 14:22:35 error executing enable: Livepatchd error: Snappy kernel-
| 2018-04-04 14:22:35 INFO juju-log Unable to activate: Command '['/snap/
| 2018-04-04 14:22:35 INFO juju-log Invoking reactive handler: reactive/
canonical-livepatch client isn't able to activate/enable because the proxy isn't yet configured. It's configured after it (update_
| 2018-04-05 15:14:23 [ERROR] 1 FAIL on XXX/4:
| + /usr/lib/
| Machine is not enabled
| <function check_status at 0x7f812f3ddb90> raised unknown exception '<type 'exceptions.
Related branches
- Haw Loeung: Approve
- Stuart Bishop (community): Approve
-
Diff: 16 lines (+5/-0)1 file modifiedreactive/canonical_livepatch.py (+5/-0)
Changed in canonical-livepatch-charm: | |
assignee: | nobody → Barry Price (barryprice) |
status: | New → In Progress |
importance: | Undecided → High |
Changed in canonical-livepatch-charm: | |
status: | In Progress → Fix Committed |
Changed in canonical-livepatch-charm: | |
status: | Fix Committed → Fix Released |
I'm hitting this very same problem as of today in an offline deployment where module- control interface doesn't get connected, no matter if it's
the kernel-
having proxy configuration running or not. Cano you please reopen it?
José