Bug 987941 - Error message should be changed when trying to set VNC keyboard layout for suspended VM
Summary: Error message should be changed when trying to set VNC keyboard layout for su...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Martin Betak
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-24 12:46 UTC by Yair Zaslavsky
Modified: 2015-03-05 00:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 07:27:55 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 17594 0 None None None Never

Description Yair Zaslavsky 2013-07-24 12:46:08 UTC
Description of problem:

The error message in case there is an attempt to change the VNC keyboard layout for suspended VM should be changed -


Current message is -

 Failed updating the properties of the VM. This may be caused either by:
    1. The values selected are not appropriate for the VM; or
    2. Its values cannot be updated while the VM is in UP state (Please shut down the VM in order to modify properties such as CPU or cluster).

I suggested for the 2nd part to rephrase to:

2. 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.

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


How reproducible:

1. Run VM
2. Suspend VM
3. Edit VM - Try to change VNC Keyboard layout 


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Itamar Heim 2013-08-21 16:40:41 UTC
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)

Comment 2 Itamar Heim 2013-09-23 07:27:55 UTC
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)


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