Bug 967557 - Pools should use same event wording logic as VMs (stateless)
Pools should use same event wording logic as VMs (stateless)
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.2.0
Unspecified Unspecified
low Severity low
: ---
: 3.4.0
Assigned To: Nobody's working on this, feel free to take it
virt
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-27 09:00 EDT by Jiri Belka
Modified: 2014-01-05 05:54 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-01-05 05:54:38 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jiri Belka 2013-05-27 09:00:24 EDT
Description of problem:
Pooled VM use 'was started' and 'started' wording in events messages. This seems to be odd in regards to BZ907997 which declared following:

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)

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

How reproducible:
100%

Steps to Reproduce:
1. run a pool and check events
2.
3.

Actual results:
a pooled vm's event msg uses wording related to stateful mode.

Expected results:
follow same style as VM do

Additional info:
See BZ907997#1
Comment 1 Itamar Heim 2014-01-05 05:54:38 EST
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.

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