Red Hat Bugzilla – Bug 976122
print warning when accepting vm edits which will require stop/start of the VM to take effect
Last modified: 2014-01-05 04:45:34 EST
Description of problem:
When we try to pin hosts cpu to vm on fly then , rhevm is accepting the value. But, changes are reflecting only if we shut down the vm and again start it(not reboot). So, if anyone try to pin hosts cpu to vm on fly then then RHEVM should throw an error/warning message.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start the vm.
2. Edit the vm.
3. Go to host tab.
4. Try adding value for "CPU Pinning topology".
5. RHEVM will accept the value. But, changes will not reflect on the vm.
RHEVM accept the value even if vm is running.
RHEVM should not accept the value if vm is in running state. OR it should throw some message on RHEVM webUI.
we have a reverse bug to allow editing values to only take action post the reboot, so i prefer we don't fix this one.
(In reply to Itamar Heim from comment #1)
> we have a reverse bug to allow editing values to only take action post the
> reboot, so i prefer we don't fix this one.
I got your point. But, it will be great if RHEVM throw an warning message if any user try to edit "CPU Pinning topology" parameter while vm is running. As RHEVM is accepting the value, users might have an impression that the changes will immediately get reflect.
Also, I saw one case in which customer was thinking in the same way.
I'm pretty sure its a dup
we should somehow visually differentiate between the fields which are applied immediately and which later.
i think i found the dup...
*** This bug has been marked as a duplicate of bug 971967 ***