Bug 950388 - ovirt-engine-cli: Name parameter is not relevant for show event command
Summary: ovirt-engine-cli: Name parameter is not relevant for show event command
Keywords:
Status: CLOSED DUPLICATE of bug 866448
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-cli
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.3.0
Assignee: Michael Pasternak
QA Contact: Elena
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-10 07:49 UTC by Oded Ramraz
Modified: 2016-02-10 19:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-10 08:26:27 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Oded Ramraz 2013-04-10 07:49:55 UTC
Description of problem:

Auto complete suggest name parameter when running show event command . 
I don't think it is relevant for this object , since the event name doesn't appear when listing or showing specific event . 


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

[RHEVM shell (connected)]# list events --max 1 --show-all 

id         : 43096
description: User admin@internal logged in.
code       : 30
custom_id  : -1
flood_rate : 30
origin     : oVirt
severity   : normal
time       : 2013-04-10T10:47:12.792+03:00
user-id    : fdfc627c-d875-11e0-90f0-83df133b58cc

[RHEVM shell (connected)]# 
[RHEVM shell (connected)]# 
[RHEVM shell (connected)]# show event 43096

id         : 43096
description: User admin@internal logged in.
code       : 30
custom_id  : -1
flood_rate : 30
origin     : oVirt
severity   : normal
time       : 2013-04-10T10:47:12.792+03:00
user-id    : fdfc627c-d875-11e0-90f0-83df133b58cc

[RHEVM shell (connected)]# show event 
id    name

Comment 1 Michael Pasternak 2013-04-10 08:26:27 UTC

*** This bug has been marked as a duplicate of bug 866448 ***


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