neutron-server pods in CrashLoopBackOff state
search cancel

neutron-server pods in CrashLoopBackOff state

book

Article ID: 321782

calendar_today

Updated On:

Products

VMware Integrated OpenStack

Issue/Introduction

  • neutron-server.log generated following error:

2023-08-08T08:23:33.595Z INFO http-nio-127.0.0.1-7440-exec-35 NsxBaseRestController 88112 SYSTEM [nsx@6876 audit="true" comp="nsx-manager" level="INFO" subcomp="manager"] UserName:'####' ModuleName:'common-services' Operation:'GET@/api/v1/infra/sites/default/enforcement-points/default/transport-zones/########-####-####-####-#############' Operation status: 'failure' Error: The requested object : /infra/sites/default/enforcement-points/default/transport-zones/########-####-####-####-############# could not be found. Object identifiers are case sensitive.

  • In nsx.ini, nsx_id of TZs that we can see in the result of "GET policy/api/v1/infra/sites/default/enforcement-points/default/transport-zones" NSX Policy API is set to default_overlay_tz and default_vlan_tz :

default_overlay_tz = ########-####-####-####-#############

default_vlan_tz = ########-####-####-####-#############

 

 

Environment

7.x

Cause

This issue is caused by a difference between transport zones generated with MP and transport zones generated with Policy.

As a result, NSX plugin for VIO cannot handle IDs of transport zones (enforcement point) created using policy API then the policy identifier.

Resolution

This issue can be avoided by creating transport zones in using Manager API:

POST api/v1/transport-zones/