|
2020-12-17
§
|
| 21:42 |
<bstorm> |
doing the same procedure to increase the timeouts more T267966 |
[tools] |
| 19:56 |
<bstorm> |
puppet enabled one at a time, letting things catch up. Timeouts are now adjusted to something closer to fsync values T267966 |
[tools] |
| 19:44 |
<bstorm> |
set etcd timeouts seed value to 20 instead of the default 10 (profile::wmcs::kubeadm::etcd_latency_ms) T267966 |
[tools] |
| 18:58 |
<bstorm> |
disabling puppet on k8s-etcd servers to alter the timeouts T267966 |
[tools] |
| 14:23 |
<arturo> |
regenerating puppet cert with proper alt names in tools-k8s-etcd-4 (T267966) |
[tools] |
| 14:21 |
<arturo> |
regenerating puppet cert with proper alt names in tools-k8s-etcd-5 (T267966) |
[tools] |
| 14:18 |
<arturo> |
regenerating puppet cert with proper alt names in tools-k8s-etcd-6 (T267966) |
[tools] |
| 14:17 |
<arturo> |
regenerating puppet cert with proper alt names in tools-k8s-etcd-7 (T267966) |
[tools] |
| 14:15 |
<arturo> |
regenerating puppet cert with proper alt names in tools-k8s-etcd-8 (T267966) |
[tools] |