Bug 1000068
| Summary: | [TEXT] change "Cannot run VM. The VM status is illegal." to "Cannot run VM. The VM is already running" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Andrew Cathrow <acathrow> |
| Component: | ovirt-engine | Assignee: | Tomas Jelinek <tjelinek> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.0 | CC: | acathrow, iheim, lpeer, michal.skrivanek, pstehlik, rbalakri, Rhev-m-bugs, tjelinek, yeylon |
| Target Milestone: | --- | ||
| Target Release: | 3.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt | ||
| Fixed In Version: | is18 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-21 22:19:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Andrew Cathrow
2013-08-22 15:26:07 UTC
this particular message is used in various places, where exactly did it happen to you? (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 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?
(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" > 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".
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. Checked on is16 Verified on is18 Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released |