| 2020-12-28 03:56:54 |
Mike Wilson |
bug |
|
|
added bug |
| 2021-01-04 22:28:07 |
George Kraft |
bug task added |
|
vault-charm |
|
| 2021-01-04 22:28:27 |
George Kraft |
charm-kubernetes-worker: status |
New |
Invalid |
|
| 2021-01-04 22:31:12 |
George Kraft |
bug task deleted |
charm-kubernetes-worker |
|
|
| 2021-01-04 22:33:45 |
George Kraft |
summary |
new node waiting on kube-proxy to start |
failure to generate cert: cannot satisfy request, as TTL would result in notAfter 2030-12-26T02:40:00.829770137Z that is beyond the expiration of the CA certificate at 2030-10-15T09:14:03Z |
|
| 2021-03-09 15:22:41 |
Aurelien Lourot |
vault-charm: status |
New |
Triaged |
|
| 2021-03-09 15:22:44 |
Aurelien Lourot |
vault-charm: importance |
Undecided |
Medium |
|
| 2021-03-09 15:24:34 |
Aurelien Lourot |
description |
I just added a new node to my cluster and it is stuck waiting for kube-proxy to start. The snap isn't configured with any options like my other nodes and so it fails to start:
kubernetes-worker/15 waiting idle 21 10.0.4.38 Waiting for kube-proxy to start.
$ sudo snap get kube-proxy
error: snap "kube-proxy" has no configuration
No real information in the logs about any errors. I'm running k8s 1.20.1 and kubernetes-worker charm version 718. |
EDIT(lourot on 2021-03-09): the real issue here is that the charm logs this error but doesn't put itself in error state, so that the system doesn't work properly later on although everything is green. See comment #8
I just added a new node to my cluster and it is stuck waiting for kube-proxy to start. The snap isn't configured with any options like my other nodes and so it fails to start:
kubernetes-worker/15 waiting idle 21 10.0.4.38 Waiting for kube-proxy to start.
$ sudo snap get kube-proxy
error: snap "kube-proxy" has no configuration
No real information in the logs about any errors. I'm running k8s 1.20.1 and kubernetes-worker charm version 718. |
|
| 2021-03-09 15:25:09 |
Aurelien Lourot |
description |
EDIT(lourot on 2021-03-09): the real issue here is that the charm logs this error but doesn't put itself in error state, so that the system doesn't work properly later on although everything is green. See comment #8
I just added a new node to my cluster and it is stuck waiting for kube-proxy to start. The snap isn't configured with any options like my other nodes and so it fails to start:
kubernetes-worker/15 waiting idle 21 10.0.4.38 Waiting for kube-proxy to start.
$ sudo snap get kube-proxy
error: snap "kube-proxy" has no configuration
No real information in the logs about any errors. I'm running k8s 1.20.1 and kubernetes-worker charm version 718. |
EDIT(lourot on 2021-03-09): the real issue here is that the charm properly logs this valid error but then doesn't put itself in error state, so that the system doesn't work properly later on although everything is green. See comment #8
I just added a new node to my cluster and it is stuck waiting for kube-proxy to start. The snap isn't configured with any options like my other nodes and so it fails to start:
kubernetes-worker/15 waiting idle 21 10.0.4.38 Waiting for kube-proxy to start.
$ sudo snap get kube-proxy
error: snap "kube-proxy" has no configuration
No real information in the logs about any errors. I'm running k8s 1.20.1 and kubernetes-worker charm version 718. |
|
