Race with activating livepatch and configuring proxy

[Haw Loeung]

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-module-control interface not connected!
| 2018-04-04 14:22:35 INFO juju-log Unable to activate: Command '['/snap/bin/canonical-livepatch', 'enable', 'XXXXX']' returned non-zero exit status 1
| 2018-04-04 14:22:35 INFO juju-log Invoking reactive handler: reactive/canonical_livepatch.py:223:update_livepatch_proxy

canonical-livepatch client isn't able to activate/enable because the proxy isn't yet configured. It's configured after it (update_livepatch_proxy). Tools such as mojo calls the nagios check to verify but that fails as follows:

| 2018-04-05 15:14:23 [ERROR] 1 FAIL on XXX/4:
| + /usr/lib/nagios/plugins/check_canonical-livepatch.py
| Machine is not enabled
| <function check_status at 0x7f812f3ddb90> raised unknown exception '<type 'exceptions.SystemExit'>'

[José Pekkarinen (koalinux)]

I'm hitting this very same problem as of today in an offline deployment where
the kernel-module-control interface doesn't get connected, no matter if it's
having proxy configuration running or not. Cano you please reopen it?

José

[José Pekkarinen (koalinux)]

Trying to connect manually doesn't help:

# snap connect canonical-livepatch:kernel-module-control core:kernel-module-control
# canonical-livepatch status
2018/11/23 07:55:44 error executing status: Livepatchd error: Snappy kernel-module-control interface not connected!

José.

[Barry Price (barryprice)]

If your connection fails outside of the charm code, I'm not sure how it's a charm bug.

Should this perhaps be better targeted at the livepatch client itself?

[Barry Price (barryprice)]

Okay, the above seems to have been filed as LP#1804810 - leaving this bug resolved.