kuryr-kubernetes

Kuryr-cni pod status changes from Running to CrashLoopBackOff

Bug #1900750 reported by Tabitha Fasoyin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-kubernetes
New
Undecided
Unassigned

Bug Description

Using the containerized installation of kuryr-kubernetes[1], the created kuryr-cni pod status changes back and forth from 'Running' to 'CrashLoopBackOff' and the kuryr-cni daemonset becomes unavailable and not ready.

[1] https://docs.openstack.org/kuryr-kubernetes/rocky/installation/devstack/containerized.html

Revision history for this message
Michal Dulko (michal-dulko-f) wrote :

Can you provide logs of kuryr-cni pod? You can use `kubectl logs` to get them.

Revision history for this message
Michal Dulko (michal-dulko-f) wrote :

Also `-p` parameter will give you logs of a previous run, so probably with all the errors.

Revision history for this message
Tabitha Fasoyin (tabbie-fash) wrote :

Hi Michal, @maysa provided a workaround fix, manually deleting the container created by the noncontainerized installation and deleting the kuryr-cni pod. That restored the kuryr-cni pod to normal behaviour. I will try to reproduce the error and provide the logs.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.