Open Stack

Hm, nothing too troubling there too, besides Kubernetes not answering
on /healthz endpoint. Are those full logs, including the moment you
tried spawning a container there? It seems like you only pasted the
fragments with tracebacks regarding failures to read /healthz endpoint
of kube-apiserver. That is another problem you should investigate -
that causes Kuryr pods to restart.

At first I'd disable the healthchecks (remove readinessProbe and
livenessProbe from Kuryr pod definitions) and try to get fresh set of
logs.

On Thu, 2020-02-06 at 10:46 +0000, VeeraReddy wrote:
> Hi mdulko,
> Please find kuryr-cni logs
> http://paste.openstack.org/show/789209/
> 
> 
> Regards,
> Veera.
> 
> 
> On Thursday, 6 February, 2020, 04:08:35 pm IST, <mdulko at redhat.com> wrote:
> 
> 
> Hi,
> 
> The logs you provided doesn't seem to indicate any issues. Please
> provide logs of kuryr-daemon (kuryr-cni pod).
> 
> Thanks,
> Michał
> 
> On Thu, 2020-02-06 at 07:09 +0000, VeeraReddy wrote:
> > Hi,
> > I am trying to run kubelet in arm64 platform
> > 1.    Generated kuryr-cni successfullly. using kur-cni Dockerfile
> > 2.    Generated kuryr-cni-arm64 container.
> > 3.    my kube-kuryr-arm64.yml (http://paste.openstack.org/show/789208/)
> > 
> > My master node in x86 installed successfully using devstack
> > 
> > While running kubelet in arm platform , not able to create kubelet interface (kubelet logs: http://paste.openstack.org/show/789206/)
> > 
> > COntroller logs: http://paste.openstack.org/show/789209/
> > 
> > Please help me to fix the issue
> > 
> > Veera.
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Regards,
> > Veera.
> 
>