Federation VNC issues

Community Support
1

Hello Community

We have federated two OpenNebula as master/slave, but we have detected a strange issue. Below the details.
Using the Master Sunstone, we can change to the Slave Sunstone. It works well, but if we try to lunch the VNC console from any virtual machine it fails (slave side). If we login directly in the slave Sunstone we do not have any problem.

In the same way, using the Slave Sunstone, we can change to the Master Sunstone. It works well, but if we lunch the VNC console from any virtual machine it fails (Master side). If we login directly in the Master Sunstone we do not have any problem.

OpenNebula version: 4.10.2
We do not see any error in the logs.
we do not have connectivity issues.

Thanks for your support!

2

Hii Eddy,

I’m afraid this is a known issue http://dev.opennebula.org/issues/2757. A
way to forward noVNC connections across zones is needed.

As you described to start the VNC console you need to login into the
sunstone of the zone hosting the VM…

Cheers

3

Thanks for your answer Ruben. We will work directly with the Sunstone for each Zone as workaround.