On Mon, Jan 31, Gustavo Ezquerro wrote:

Ok so a reinstallation it is then, thought was another way to fix it. Thanks Thorsten!

I'm pretty sure that there are other ways to fix it, but that will most likely take much longer. That's the advantage of "Cattles": don't care if they make problems, replace them ;) Thorsten

On Mon, Jan 31, 2022 at 10:41 AM Thorsten Kukuk wrote:

On Mon, Jan 31, Gustavo Ezquerro wrote:

> Hi to all; > > One of my worker node somehow can't boot, showing me the next message... cri-o > can't start and then it restarts  > > image.png > > Any recommendations?

If it is a plain Kubic worker node: remove node from kubernetes cluster, re-install host, add node again to kubernetes cluster.

It's the fastest and cheapest way. That's why nodes in a kubernetes cluster are no Pets ;)

  Thorsten

-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Ivo Totev (HRB 36809, AG Nürnberg)

-- Saludos. Gustavo Ezquerro Morales

-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Ivo Totev (HRB 36809, AG Nürnberg)