[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Cannot retrieve ignition config from machine-config-server - expired certs



On Tue, Oct 1, 2019 at 4:33 PM W. Trevor King <wking redhat com> wrote:
>
> On Mon, Sep 30, 2019 at 4:50 PM Jon Stanley wrote:
> > Attached the logs.
>
> ./bootstrap/journals/bootkube.log has loops like:
>
> Sep 30 23:32:55 localhost.localdomain bootkube.sh[1605]:
> https://etcd-1.openshift4poc.example.local:2379 is unhealthy: failed
> to connect: dial tcp 172.16.1.11:2379: connect: no route to host
> Sep 30 23:32:55 localhost.localdomain bootkube.sh[1605]:
> https://etcd-2.openshift4poc.example.local:2379 is unhealthy: failed
> to connect: dial tcp 172.16.1.13:2379: connect: no route to host
> Sep 30 23:32:55 localhost.localdomain bootkube.sh[1605]:
> https://etcd-0.openshift4poc.example.local:2379 is unhealthy: failed
> to connect: dial tcp 172.16.1.10:2379: connect: connection refused
> Sep 30 23:32:55 localhost.localdomain bootkube.sh[1605]: Error:
> unhealthy cluster
> Sep 30 23:32:56 localhost.localdomain bootkube.sh[1605]: etcdctl
> failed. Retrying in 5 seconds...
>
> so you never formed an etcd cluster.  ./control-plane/ has no
> meaningful content, so we were unable to SSH in and gather logs on
> that side.  ./bootstrap/containers/machine-config-server-dc163e7947214728da3d0d83183e525d87121ebbab42650c472406a4ef68677b.log
> has lots of:

Yeah, it never got past Ignition on the control plane side, so no ssh
to the control plane yet....

> So everything looks reasonable on this side.  Grab the console logs
> from the control-plane machines?

Not super useful, but attached :).

Attachment: image.png
Description: PNG image


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]