Bug 907997 - Run Once -> Run Stateless - There's no info that a VM was started in 'stateless' mode
Summary: Run Once -> Run Stateless - There's no info that a VM was started in 'statele...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.3.0
Assignee: Michal Skrivanek
QA Contact: Jiri Belka
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 16:00 UTC by Jiri Belka
Modified: 2015-09-22 13:09 UTC (History)
9 users (show)

Fixed In Version: is1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


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

Description Jiri Belka 2013-02-05 16:00:49 UTC
Description of problem:
Run Once/Run Stateless - There's no info that a VM was started in 'stateless' mode, there's just "VM $vm started on Host $host".

From logging/audit point of view I think it's good to distinguish between VM run in "normal" mode and when it was started in "stateless" mode.

Example: By mistake a user can start a VM in stateless mode, made some modification, shut it down. Then next (valid) start of the VM would not have the modification (obvious!). But from events it is not possible to see where was the error, only digging inside logs would be way to find this "mistake".

Not sure if this is 'RFE' or "oversight" detail in events design. Feel free to put '[RFE]' in summary.

Version-Release number of selected component (if applicable):
sf5

How reproducible:
100%

Steps to Reproduce:
1. run a vm in stateless (run once -> run stateless)
2. check vm's events
3.
  
Actual results:
from events there's no way to find out if the VM was started in stateless mode

Expected results:
log in events reality of VM's life

Additional info:

Comment 1 Libor Spevak 2013-03-26 15:41:12 UTC
Currently, we have several audit log items of the types (a pair of messages, in case of success):

Run as stateful:
1. VM YYYYYY was started by admin@internal (Host: XXXX.redhat.com).    (code=USER_STARTED_VM)
2. VM YYYYYY started on Host XXXX.redhat.com                           (code=USER_RUN_VM)

Run as stateless (DESKTOP only):
1. Starting VM YYYYYY was initiated by admin@internal.                 (code=USER_INITIATED_RUN_VM)
2. VM YYYYYY was restarted on Host XXXX.redhat.com                     (code=VDS_INITIATED_RUN_VM)

RunOnce as stateful:
1. VM YYYYYY was started by admin@internal (Host: XXXX.redhat.com).    (code=USER_STARTED_VM)
2. VM YYYYYY started on Host XXXX.redhat.com                           (code=USER_RUN_VM)

RunOnce as stateless:
1. Starting VM YYYYYY was initiated by admin@internal.                 (code=USER_INITIATED_RUN_VM)
2. VM YYYYYY was restarted on Host XXXX.redhat.com                     (code=VDS_INITIATED_RUN_VM)

So, recommending 2 additional audit messages:

USER_RUN_VM_AS_STATELESS=VM ${VmName} started on Host ${VdsName} as stateless
VDS_INITIATED_RUN_VM_AS_STATELESS=VM ${VmName} was restarted on Host ${VdsName} as stateless

Comment 2 Libor Spevak 2013-03-28 09:52:13 UTC
Merged u/s: 9cabd9d433697badb37765a7a0669fe4b95b7412

Comment 4 Jiri Belka 2013-05-27 13:02:40 UTC
ok, is1. (I've created related BZ - BZ967557 - to make pools to follow same event syntax.)

Comment 5 Itamar Heim 2014-01-21 22:28:27 UTC
Closing - RHEV 3.3 Released

Comment 6 Itamar Heim 2014-01-21 22:28:29 UTC
Closing - RHEV 3.3 Released

Comment 7 Itamar Heim 2014-01-21 22:31:21 UTC
Closing - RHEV 3.3 Released


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