Bug 879894 - rhevm-manage-domains: please fix USAGE in --help to say "rhevm-manage-domains" instead of "engine-manage-domains"
Summary: rhevm-manage-domains: please fix USAGE in --help to say "rhevm-manage-domains...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.1.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Moran Goldboim
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-25 08:43 UTC by Dafna Ron
Modified: 2016-02-10 19:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-29 11:10:28 UTC
oVirt Team: Infra
Target Upstream Version:


Attachments (Terms of Use)

Description Dafna Ron 2012-11-25 08:43:24 UTC
Description of problem:

[root@dafna-web-admin ~]# rhevm-manage-domains 
engine-manage-domains: add/edit/delete/validate/list domains
USAGE:
	engine-manage-domains -action=ACTION [-domain=DOMAIN -provider=PROVIDER -user=USER -passwordFile=PASSWORD_FILE -interactive -configFile=PATH -addPermissions] -report
Where:


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

si24.4

How reproducible:

100%

Steps to Reproduce:
1. run rhevm-manage-domains without any parameters
2.
3.
  
Actual results:

rhevm-manage-domains if referred to as engine-manage-domain

Expected results:

we should be consistent in names

Additional info:

Comment 1 Itamar Heim 2012-11-25 10:21:31 UTC
considering rhevm-manage-domains is a sym-link to engine-manage-domains, not sure if we should fix this.

Comment 2 Simon Grinberg 2012-12-24 18:06:26 UTC
(In reply to comment #1)
> considering rhevm-manage-domains is a sym-link to engine-manage-domains, not
> sure if we should fix this.

But this looks bad. If the process of branding can be automated then I would vote for fixing it.

Comment 4 Itamar Heim 2013-12-29 11:10:28 UTC
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.