Description of problem:

When a vm pool or a stateless vm are based on some template's 'latest version', any new template version of that template should invoke the re creation of the vm/s if it is down and in case the vm is up then re creation occurs once the vm is down at some point.

This RFE raises the question, should we provide an indicator in such a case (similar to the one that appears when some configuration of the vm was done that requires vm restart), and/or some informative message so the user remembers that a change has been done but did not take effect on the vm yet.