After upgrade of OVM servers to 3.4.3 Unable to connect to VM console on Oracle VM Manager
(Doc ID 2273449.1)
Last updated on NOVEMBER 18, 2022
Applies to:
Oracle VM - Version 3.4.1 to 3.4.3 [Release OVM34]Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.
Symptoms
After upgrade of OVM servers from 3.4.x to 3.4.3 and if OVM manager is left alone at old 3.4.x, OVM manager cannot launch VM console.
The OVM console with show "Failed to connect to server (code: 1000)
The Admin Server log will show
javax.net.ssl.SSLException: Received fatal alert: handshake_failure
at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1639)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1607)
at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1776)
at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1068)
at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:890)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:764)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
at com.oracle.ovm.mgr.ras.SSLWorker.doHandshake(SSLWorker.java:367)
at com.oracle.ovm.mgr.ras.SSLWorker.unwrapSSLData(SSLWorker.java:252)
at com.oracle.ovm.mgr.ras.SSLWorker.handle(SSLWorker.java:118)
at com.oracle.ovm.mgr.ras.OutGoingProxyCommandChain.handle(OutGoingProxyCommandChain.java:36)
at com.oracle.ovm.mgr.ras.Dispatcher.run(Dispatcher.java:67)
at java.lang.Thread.run(Thread.java:745)
at com.oracle.ovm.mgr.util.concurrent.OvmThread.run(OvmThread.java:152)
Changes
After OVM severs are upgraded to 3.4.3 and OVM manager is left on the old 3.4.x.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |