ako pod in CrashLoopBackOff status
search cancel

ako pod in CrashLoopBackOff status

book

Article ID: 386424

calendar_today

Updated On:

Products

VMware vSphere with Tanzu

Issue/Introduction

ako pod is on  CrashLoopBackOff  status:

vmware-system-ako                           vmware-system-ako-ako-controller-manager-xxxxxxxxxx-xxxxx         1/2     CrashLoopBackOff   7 (2m4s ago)    14m

 

On ako pod logs you can see something similar to:

2025-01-22T09:57:46.184Z        ESC[34mINFOESC[0m       avirest/handle_netinfo.go:48    
Got data LS LR Map: map[/infra/segments/avi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_0:/infra/tier-1s/t1_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_rtr 
                        /infra/segments/avi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_0:/infra/tier-1s/t1_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_rtr 
                       /infra/segments/avi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_0:/infra/tier-1s/t1_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_rtr 
[...]
                       /infra/segments/avi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_0:/infra/tier-1s/t1_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_rtr 
                       /infra/segments/avi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_0:/infra/tier-1s/t1_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_rtr 
                       /infra/segments/avi_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_0:/infra/tier-1s/t1_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_rtr], from NetworkInfo CR
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x17fc18a]

 

Cause

There is inconsistencies on the NSX -CLOUD Data Network Segments, and at least one of the Logical Routers is not mapped to an Overlay Segment.

Resolution

To solve this issue, make sure all Logical Routers are mapped to an Overlay segment, and assign an Overlay Segment if there is not assignment.

See the example:

Powered by Wolken Software