Resource: res_kube_apiserver_snap.kube_apiserver.daemon not running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes API Load Balancer |
Fix Released
|
Critical
|
George Kraft | ||
Kubernetes Control Plane Charm |
Fix Released
|
Critical
|
George Kraft | ||
charm-interface-hacluster |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
k8s 1.17
kubernetes-master rev-788
---
I believe this is related to this bug:
https:/
We could be not monitoring that resource correctly still.
So it *may* be a regression in 1.17.
---
I've got 2/3 masters with blocked hacluster:
kubernetes-master/0 active idle 12/lxd/1 10.246.65.36 6443/tcp Kubernetes master running.
containerd/10 active idle 10.246.65.36 Container runtime available
filebeat/10 active idle 10.246.65.36 Filebeat ready.
flannel/10 active idle 10.246.65.36 Flannel subnet 10.1.30.1/24
hacluster-
kubernetes-master/1 active idle 13/lxd/1 10.246.65.34 6443/tcp Kubernetes master running.
containerd/9 active idle 10.246.65.34 Container runtime available
filebeat/9 active idle 10.246.65.34 Filebeat ready.
flannel/9 active idle 10.246.65.34 Flannel subnet 10.1.57.1/24
hacluster-
---
If I go to any of the masters I can see that the service is in fact active:
$ systemctl status snap.kube-
● snap.kube-
Loaded: loaded (/etc/systemd/
Drop-In: /etc/systemd/
Active: active (running) since Wed 2020-01-08 19:04:15 UTC; 2h 59min ago
Main PID: 486957 (kube-apiserver)
Tasks: 31 (limit: 4915)
CGroup: /system.
└─486957 /snap/kube-
no longer affects: | charm-kubernetes-master |
Changed in charm-kubernetes-master: | |
status: | New → Confirmed |
Changed in charm-kubeapi-load-balancer: | |
status: | New → Confirmed |
Changed in charm-kubeapi-load-balancer: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
What revision of the hacluster charm are you running?