Description of problem: More informative message in event when a VM started in Paused Mode. Now: Starting VM win7_32bit was initiated by portaluser4. Maybe good msg: Starting in paused mode VM win7_32bit was initiated by portaluser4. Version-Release number of selected component (if applicable): SI24.5 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Starting VM win7_32bit was initiated by portaluser4. Expected results: ...something like... Starting in paused mode VM win7_32bit was initiated by portaluser4. Additional info:
Trying to figure out why is this interesting?
> Trying to figure out why is this interesting? For logging. One can ask: why was not a VM accessible? RHEV admin would check history logged events and see 'Starting VM ...'. He would not know that somebody started the VM in Paused mode... So, just to provide good overview what was going on in history of the VM in events.
is8 - I still can reproduce.
Yes... There was a bug in the fix that shows the message only when debugger present (because it took more time and the VM was already pause) This fix the issue: http://gerrit.ovirt.org/#/c/17701/ Tested on Run VM and Run Once.
the new fix is merged at: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=b8e7b713947352411403e3042fa2c83fb06acbfc
ok, is10.
This bug is currently attached to errata RHEA-2013:15231. 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: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 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. http://rhn.redhat.com/errata/RHSA-2014-0038.html