Description of problem:
If vm from vm-pool is started by admin (not running as stateless)
and while it is running, a new template version is created,
and vm-pool is set to use latest version,
this vm is not updated, only after it is run by user (as stateless) and stops again. 

Version-Release number of selected component (if applicable):
3.5

How reproducible:
always

Steps to Reproduce:
1. create vm-pool, set to use template latest version
2. run a vm from the pool, using the webadmin
3. create new version for the template that the pool is using
4. stop the vm and verify version didn't change

Actual results:
vm version is not updated

Expected results:
vm version should be updated

Additional info:
this only happens to vms that are run by the admin and while it was running new template version was created.
a simple workaround is to run the vm from user portal (as user) and stop the vm.
another option is to use run-once and start the vm as stateless, then stop the vm.