proton service is observed to be continually crashing every 4 min on each node, which halts the upgrade process.In /var/log/proton/proton-tomcat-wrapper.log you can see this as well with the log line below.
INFO | jvm 1 | <Time stamp> | java.lang.NullPointerException: Cannot invoke "com.vmware.nsx.management.model.switching.transportzoneprofile.TransportZoneProfileTypeIdEntry.getBuilder()" because "value" is null
INFO | jvm 1 | <Time stamp> | at com.vmware.nsx.management.switching.infrastructure.model.TransportZone.lambda$setTransportProfileIds$1(TransportZone.java:147)
/var/log/syslog of the NSX manager you can see this as well with the log line below.<Time Stamp> <NSX Manager FQDN> NSX 27225 FABRIC [nsx@4413 comp="nsx-manager" level="WARNING" reqId="########-####-####-##############" subcomp="manager" username="admin"] Policy entity of TransportZoneProfile is null : /infra/transport-zone-profiles/####-###_Profile_#######
VMware NSX 9.0.2
This issue occurs when a transport zone is referencing a non-existent transport zone profile. This invalid reference causes the proton service to crash, leading to the random appliance reboots.
If you believe you have encountered this issue, open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.