Feature #4308
OpenNebula Federation VNC MASTER/SLAVE
| Status: | Closed | Start date: | 01/25/2016 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Sunstone | |||
| Target version: | - | |||
| Resolution: | duplicate | Pull request: |
Description
Good morning
¿How to solve this problem?
We have federated two OpenNebula as master/slave, but we have detected a strange issue.
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 and reverse slave change master.
OpenNebula version: 4.14
We do not see any error in the logs.
we do not have connectivity issues.
Thanks for your support!
about the federation
I do not understand how to solve
Could you explain me please!
-Federation Master-> Slave
Failed to connect to VNC server (code: 1006)
Related issues
History
#1
Updated by Ruben S. Montero over 5 years ago
- Status changed from Pending to Closed
- Resolution set to duplicate
#2
Updated by Ruben S. Montero over 5 years ago
- Duplicates Feature #2757: Make noVNC proxy work in a federation to access VMs in any zones added
#3
Updated by Ruben S. Montero over 5 years ago
This need some logic in the NoVNC server to forward request to the target Sunstone. The only workaround right now is to login directly in the Sunstone Slave.