After system reboots for OS patching, VNA is not starting properly.
We have the Spectrum integration disabled presently, but it's showing down in NetOps Portal, and the rest page is unavailable.
I've tried stopping / restarting wildfly and mysql, as well as rebooting the system, but still a no go.
The environment is our lab, though we need to determine whether its related to the OS patching prior to patching in production.
After an in place OS upgrade on the VNA server, RH 7.x to RH 8.x, the VNA Gateway shows Operational Status Down in the Portal System Status VNA Gateway table. The same is seen in the VNA Administration page (Portal UI Administration -> Monitored Items Management -> VNA Administration.
Sample server.log file error from a VNA 23.3.2 install whose OS was updated from RH 7 to 8. Post OS update when trying to start the environment this error appears.
2025-04-10 17:02:51,344 WARN [org.jboss.modules.define] (MSC service thread 1-1) Failed to define class com.ca.em.sdn.gateway.broker.core.flow.FlowManager in Module "deployment.core-23.3.2-RELEASE.war" from Service Module Loader: java.lang.UnsupportedClassVersionError: Failed to link com/ca/em/sdn/gateway/broker/core/flow/FlowManager (Module "deployment.core-23.3.2-RELEASE.war" from Service Module Loader): com/ca/em/sdn/gateway/broker/core/flow/FlowManager has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
All supported Network Observability DX NetOps Virtual Network Assurance releases
System patching cycle removed the required Java version for VNA, or set the systems Java release to an unsupported version.
Install the Java version required by your VNA version. After ensuring the correct required Java version is set for use, restart the VNA Wildfly service.
What Java version is required for our VNA version? Review the System Requirements "Default JDK" section of the VNA Installation Requirements and Considerations documentation topic.