Bug 1000068 - [TEXT] change "Cannot run VM. The VM status is illegal." to "Cannot run VM. The VM is already running"
Summary: [TEXT] change "Cannot run VM. The VM status is illegal." to "Cannot run VM. T...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.0
Assignee: Tomas Jelinek
QA Contact: Artyom
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-22 15:26 UTC by Andrew Cathrow
Modified: 2014-09-07 22:56 UTC (History)
9 users (show)

Fixed In Version: is18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 22:19:11 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


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

Description Andrew Cathrow 2013-08-22 15:26:07 UTC
Change text as described in $summary

Comment 1 Michal Skrivanek 2013-08-23 09:13:36 UTC
this particular message is used in various places, where exactly did it happen to you?

Comment 2 Andrew Cathrow 2013-08-23 11:29:00 UTC
(In reply to Michal Skrivanek from comment #1)
> this particular message is used in various places, where exactly did it
> happen to you?

Start a VM
The refresh was slow to happen (go figure?)
Press start again

Comment 3 Tomas Jelinek 2013-09-12 13:36:03 UTC
There are lots of states the VM can be in in which the VM can not start (resulting in the message: Cannot run VM. The VM status is illegal.). Namely:

WaitForLaunch, Up, PoweringDown, PoweringUp, RebootInProgress, MigratingFrom, SavingState, PreparingForHibernate, RestoringState, ImageIllegal, ImageLocked, NotResponding, Unassigned, Unknown

What granularity do we want? Do we want only the "Up" to return a different message? Or we could change the message to something like:

"Cannot run VM because it is in ${status} status."

Andrew?

Comment 4 Andrew Cathrow 2013-09-12 13:46:28 UTC
(In reply to Tomas Jelinek from comment #3)
> There are lots of states the VM can be in in which the VM can not start
> (resulting in the message: Cannot run VM. The VM status is illegal.). Namely:
> 
> WaitForLaunch, Up, PoweringDown, PoweringUp, RebootInProgress,
> MigratingFrom, SavingState, PreparingForHibernate, RestoringState,
> ImageIllegal, ImageLocked, NotResponding, Unassigned, Unknown
> 
> What granularity do we want? Do we want only the "Up" to return a different
> message? Or we could change the message to something like:
> 
> "Cannot run VM because it is in ${status} status."
> 
> Andrew?

We should give the clearest answer to the end user. Having the customized message per status as above would be the best approach.

Would these messages be translated or would just show "PoweringUp" -vs- "Powering Up"

Comment 5 Tomas Jelinek 2013-09-12 14:27:25 UTC
> Would these messages be translated or would just show "PoweringUp" -vs- 
> "Powering Up"

There is a support to make them localized so they could be like "Powering Up".

Comment 6 Artyom 2013-09-27 06:31:43 UTC
Fast click on run vm give error message "Cannot run VM because it is in Wair for Launch status."
Please correct from "Wair" to "Wait"
After second run button disabled.

Comment 7 Artyom 2013-09-27 06:32:11 UTC
Checked on is16

Comment 8 Artyom 2013-10-10 07:14:47 UTC
Verified on is18

Comment 9 Itamar Heim 2014-01-21 22:19:11 UTC
Closing - RHEV 3.3 Released

Comment 10 Itamar Heim 2014-01-21 22:25:23 UTC
Closing - RHEV 3.3 Released


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