Bug 985813
Summary: | [Admin Portal] Host's Display address is not immediately applied - entity (VM) data seems to be cached | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> |
Component: | ovirt-engine-webadmin-portal | Assignee: | Tomas Jelinek <tjelinek> |
Status: | CLOSED WONTFIX | QA Contact: | Jiri Belka <jbelka> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.3.0 | CC: | acathrow, ecohen, iheim, lsvaty, michal.skrivanek, Rhev-m-bugs |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | virt | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-09 13:38:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jiri Belka
2013-07-18 10:03:21 UTC
The problem is that the display address is a host property so it's update is the update of the host. The display address of the VM is a VM's dynamic property managed in the VDSM polling thread. So the display address is not really cached - it is updated after the VM's dynamic data get updated. So basically the steps to reproduce could be simplified to: 1: go to the host tab and change the display address 2: quickly go back to the VMs tab and open the console (if you where quick enough the display address will be still the old) 3: wait couple of seconds and try again (the new address will be used) I'm not sure if this is a bug or a correct behavior according to our architecture. I see the following options how to proceed: 1: accept the fact that the display address is managed by the host polling thread. Since the host console address is not expected to be changed too often, it should be ok to wait few seconds until the VMs get updated. 2: after updating the host, update all the VMs running on it. It can bring some issues by interfering with the polling thread but can be certainly solved. @Michal: what do you think? this would rarely happen in real life and it is updated correctly in the next refresh period, the same way as all the other things (except VM state changes). We are investigating how to address that globally, so eventually the delay would be shorter, but it's far from getting in. For now I suggest to CLOSE as no specific action/change is needed |