kubernetes-worker install hook failed to snap install kube-proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes Worker Charm |
Triaged
|
Undecided
|
Unassigned |
Bug Description
During a recent Solutions QA test (https:/
2019-07-23 01:07:30 DEBUG install subprocess.
2019-07-23 01:07:30 ERROR juju.worker.
2019-07-23 01:07:30 DEBUG juju.machinelock machinelock.go:180 machine lock released for uniter (run install hook)
2019-07-23 01:07:30 DEBUG juju.worker.
2019-07-23 01:07:30 INFO juju.worker.uniter resolver.go:126 awaiting error resolution for "install" hook
2019-07-23 01:07:30 DEBUG juju.worker.uniter agent.go:20 [AGENT-STATUS] error: hook failed: "install"
Is this environment still available and could you run `sudo snap install --channel 1.15/stable --classic kube-proxy` on one of the worker units and report the results?
Unfortunately I can't find the actual reason that the snap install failed anywhere in the crashdump logs. It looks like the snap layer swallows the error. I wonder if it might have been a snap store hiccup since it happened on more than one worker unit.