Description of problem:
In CFME-5.11.4, v2v migration failed on bug 1807570,
and next to the migrated VM, there is a message that is not relevant,
because the source VM was down:
"Powering on virtual machine: Migration cancelled"
Version-Release number of selected component (if applicable):
There should not be a powering up message for a down source VM.
This message seem to be relevance only for "warm migration" / when source VM is running.
Created attachment 1666146 [details]
failing vm migration screenshot
The message is about the state where we are the migration state machine. The last state when cancelling is powering on the source VM if it was on.
But you're right, the message should be something like "Restoring VM power state". @Vince, what do you think?
"Restoring VM power state" makes sense to me, but I don't believe this is something controlled by the UI. @mturley please confirm that we're just passing thru messages generated by the backend.
Vince is correct, in this case the "Powering on virtual machine" message is being displayed because an equivalent message was passed from the backend (task.options.progress.current_description). The "Migration cancelled" piece is appended in the UI based on cancellation status, however.
If the API's task.options.progress.current_description value matches one of the `apiString`s in that map, the corresponding `text` value from the map is used. If not, the API value is used directly. (In this specific case, the API string is "Power on virtual machine", which the map changes to "Powering on virtual machine" in order to keep the grammar consistent.)
So, if we are changing this message we need to do so in the backend, but we should also add any new expected status messages to the map in the UI (until Milan finishes his work to make that map unnecessary).
Moving to 5.11.Z. It doesn't have an impact on users and it requires translation.
No impact on users. Closing as WONTFIX.