Maybe simply using "reboot" is enough, but in the past I had problems with ext4 corruption and I consider unclean stopping and rebooting of containers as a possible culprit
Here's related output:
$etcdctl cluster-health
cluster may be unhealthy: failed to list members
Error: client: etcd cluster is unavailable or misconfigured; error #0: dial tcp 127.0.0.1:2379: getsockopt: connection refused
# cat /etc/coreos/update.conf
GROUP=stable
REBOOT_STRATEGY="etcd-lock"
LOCKSMITHD_REBOOT_WINDOW_START="Sun 1:00"
LOCKSMITHD_REBOOT_WINDOW_LENGTH="2h"
locksmithctl status
Error initializing etcd client: client: etcd cluster is unavailable or misconfigured
Cheers and thanks for help
On 26. Mar 2018, at 20:53, Derek Gonyeo <dgo...@redhat.com> wrote:For the locksmith part of the question, set the REBOOT_STRATEGY line to "reboot". The available strategies are described here: https://github.com/coreos/locksmith#configuration
--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.