Bug 1080908 - [branding] engine-setup says "login into oVirt Engine"
Summary: [branding] engine-setup says "login into oVirt Engine"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.4.0
Assignee: Simone Tiraboschi
QA Contact: sefi litmanovich
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-26 10:02 UTC by Lev Veyde
Modified: 2014-06-12 14:09 UTC (History)
12 users (show)

Fixed In Version:
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 27401 0 master MERGED Cleaning a message due to a branding issue Never
oVirt gerrit 27404 0 ovirt-engine-3.4 MERGED Cleaning a message due to a branding issue Never

Description Lev Veyde 2014-03-26 10:02:15 UTC 
Description of problem:

engine-setup says:

Please use the user "admin" and password specified in order to login into oVirt Engine

It may be more preferable to have it branded by RHEV i.e. to say:

Please use the user "admin" and password specified in order to login into RHEVM

or (Sbonazzo's suggestion) to have a neutral message of i.e.:

Please use the user "admin" and password specified in order to login


Version-Release number of selected component (if applicable):
rhevm.noarch 0:3.4.0-0.1000.2129.b205e30.beta2.el6ev

How reproducible:
100%

Steps to Reproduce:
1. install rhevm
2. run engine-setup
Comment 1 Sandro Bonazzola 2014-05-06 10:05:05 UTC 
Back to post, 27404 has not been merged yet.
Comment 2 sefi litmanovich 2014-05-12 16:34:04 UTC 
Verified with rhevm-3.4.0-0.18.el6ev.noarch.

'Please use the user "admin" and password specified in order to login'
Comment 3 Itamar Heim 2014-06-12 14:09:47 UTC 
Closing as part of 3.4.0
Note You need to log in before you can comment on or make changes to this bug.