Bug 1321187 - Unable to change any property of running vm that requires reboot to take effect.
Summary: Unable to change any property of running vm that requires reboot to take effect.
Keywords:
Status: CLOSED DUPLICATE of bug 1313369
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.6.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-24 23:00 UTC by Ameya Charekar
Modified: 2019-12-16 05:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-25 05:52:21 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ameya Charekar 2016-03-24 23:00:22 UTC
Description of problem:
If we change any property of running vm that requires vm shutdown and start, then orange icon appears with message "Server with newer configure next run" but once vm started after shutdown newer changes will not take effect and vm will continue to use older setting.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.6.3.4-0.1.el6

How reproducible:
Always.

Steps to Reproduce:
1. Change any setting that requires vm shutdown and start e.g. check "Enable VirtIO serial console" flag of running vm.
2. Then vm will have orange icon with message "Server with newer configure next run".
3. Once vm starts after shutdown orange icon will disappear but vm will continue to use older setting i.e. "Enable VirtIO serial console" flag will be unchecked.

Actual results:
vm continue to use older setting.

Expected results:
vm should start with newer setting.

Additional info:
Currently to change settings need to turn off vm, make changes and then start vm.

Comment 1 Michal Skrivanek 2016-03-25 05:52:21 UTC

*** This bug has been marked as a duplicate of bug 1313369 ***


Note You need to log in before you can comment on or make changes to this bug.