Red Hat Bugzilla – Bug 891279
[RFE] Backend: 'migration complete' event should include the destination VDS, not the source [TEXT]
Last modified: 2014-07-13 19:18:31 EDT
cloning for rhev documenation/tracking
+++ This bug was initially created as a clone of Bug #586754 +++
Description of problem:
Currently, the event is:
Migration complete (VM: STRESS-C-044, Source Host: master-vdsd.qa.lab.tlv.redhat.com)
The source is less interesting for the user than the destination - please either have both (as in the starting migration message) or the destination only, not the source.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from Miki Kenneth on 2010-04-29 09:54:51 EDT ---
I vote for both
--- Additional comment from Itamar Heim on 2012-12-11 01:41:11 EST ---
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
--- Additional comment from Yaniv Kaul on 2012-12-11 02:35:45 EST ---
Should be fixed, really annoying.
--- Additional comment from Libor Spevak on 2012-12-14 08:19:48 EST ---
New sample output:
"Migration failed (VM: Fedora17, Source: dev-18.DOMAIN, Destination: dev-17.DOMAIN)."
"Migration cancelled (VM: Fedora17, Source: dev-18.DOMAIN, User: admin@internal)."
"Migration started (VM: Fedora17, Source: dev-18.DOMAIN, Destination: dev-17.DOMAIN, User: admin@internal)."
"Migration completed (VM: Fedora17, Source: dev-17.DOMAIN, Destination: dev-18.DOMAIN)."
--- Additional comment from Libor Spevak on 2013-01-02 05:30:44 EST ---
Merged to master.
Migration completed (VM: LinuxPool-1, Source: aqua-vds4, Destination: aqua-vds5).
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.