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
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.