Bug #3469
VNC does not track VM when host changes
| Status: | Closed | Start date: | 12/18/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Javi Fontan | % Done: | 0% | |
| Category: | vCenter | |||
| Target version: | Release 4.10.2 | |||
| Resolution: | worksforme | Pull request: | ||
| Affected Versions: | OpenNebula 4.10 |
Description
Either via manual vMotion, HA or DRS, when a VM changes to a new host the VNC button continues to try to talk to the old host when it opens and then fails. Possibly having VNC button poll to get current host of VM before it attempts to open the console window might be the most straightforward method but a general polling or other call that keeps the current host information accurate would also work.
History
#1
Updated by Ruben S. Montero over 6 years ago
- Category set to vCenter
- Status changed from Pending to New
- Target version set to Release 4.10.2
#2
Updated by Ruben S. Montero over 6 years ago
- Assignee set to Javi Fontan
#3
Updated by Javi Fontan over 6 years ago
- Status changed from New to Closed
- Resolution set to worksforme
It takes a bit (one monitoring cycle) to update the host where it is running (variable ESX_HOST of the VM template) but after that the vnc token is generated correctly.