SSP UI Banner: A "Config Sync in Progress" banner remains displayed at the top of the SSP UI for an extended duration (e.g., more than 1 hour).
Security Explorer Render Error: Navigating to SSP UI -> Monitor-> Security Explorer displays the following error:
visualization query exec error(0)
To confirm if your environment is affected by the NULL createTime issue, inspect the logs of the nsx-config pods.
nsx-config PodsRun the following command from the SSPI CLI to retrieve the exact pod names:
k get pods -A | grep nsx-config
JpaSystemException ErrorsGrep the pod logs and search for the NsxConfigNormalizationServiceImpl error:
k -n nsxi-platform logs nsx-config-0-0
k -n nsxi-platform logs nsx-config-1-0
If affected, you will observe the following NullPointer / JpaSystemException stack trace in the log stream:
NsxConfigNormalizationServiceImpl: INTELLIGENCE [nsx@4413 comp="nsx-manager" errorCode="INT900050" level="ERROR" logger="NsxConfigNormalizationServiceImpl" msgID="INTELLIGENCE" subcomp="manager" threadName="pool-7-thread-2"] Failed synchronizing compute config.
org.springframework.orm.jpa.JpaSystemException: Null value was assigned to a property [class com.vmware.nsx.pace.nsxconfig.model.normalization.NormalizedComputeConfig.createTime] of primitive type: 'com.vmware.nsx.pace.nsxconfig.model.normalization.NormalizedComputeConfig.createTime' (setter)
at org.springframework.orm.jpa.hibernate.HibernateExceptionTranslator.convertHibernateAccessException(HibernateExceptionTranslator.java:223)
at org.springframework.orm.jpa.hibernate.HibernateExceptionTranslator.convertHibernateAccessException(HibernateExceptionTranslator.java:131)
at org.springframework.orm.jpa.hibernate.HibernateExceptionTranslator.translateExceptiSSP 5.2
Legacy or migrated Virtual Machines streamed from NSX Manager may contain a NULL createtime attribute. Because the SSP service expects a valid timestamp, inventory synchronization fails to complete and remains stuck in an "In Progress" state, triggering persistent config sync banners and visualization errors in the SSP UI.
Kindly contact Broadcom support for the resolution