Bug 996191 - [Admin Portal] Changing TZ of running Windows VM is possible but the value is not saved in DB
Summary: [Admin Portal] Changing TZ of running Windows VM is possible but the value is...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.0
Assignee: Martin Betak
QA Contact: Pavel Novotny
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-12 15:34 UTC by Jiri Belka
Modified: 2015-09-22 13:09 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-06 12:55:21 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
engine.log (3.59 KB, application/x-gzip)
2013-08-12 15:34 UTC, Jiri Belka
no flags Details

Description Jiri Belka 2013-08-12 15:34:52 UTC
Created attachment 785760 [details]
engine.log

Description of problem:
In is9.1 I can change TZ of running Windows VM, thus no error, but the value is still the old one, it is not saved into DB.

Version-Release number of selected component (if applicable):
is9.1

How reproducible:
100%

Steps to Reproduce:
1. create a new Windows VM
2. start VM
3. when running try to change TZ
4. check again VM properties for TZ and DB

Actual results:
UI allows the user to change TZ for running Windows VM but the value is not change

Expected results:
UI should not allow this change at all when Windows Vm is running - error popup

Additional info:
in the past it was not possible => UI error popup, it was even not possible to select different TZ because the list was inactive and gray

Comment 1 Martin Betak 2013-09-06 11:23:16 UTC
jbelka: can you please check if this behavior also occurs on the latest is?

Comment 2 Jiri Belka 2013-09-06 12:42:01 UTC
is13 - i cannot reproduce as i get:

"Error while executing action:

test:

    There was an attempt to change VM values while the VM is not down. Please shut down the VM in order to modify these properties."


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