Bug 1439281

Summary:	Upgrading procedures hardcodes admin@internal
Product:	[oVirt] ovirt-hosted-engine-setup	Reporter:	Simone Tiraboschi <stirabos>
Component:	Plugins.General	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Artyom <alukiano>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.1.0.4	CC:	bgraveno, bugs, didi, ylavi
Target Milestone:	ovirt-4.1.3	Keywords:	Triaged
Target Release:	2.1.1	Flags:	rule-engine: ovirt-4.1+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	The self-hosted engine Manager virtual machine upgrade procedure from Red Hat Enterprise Virtualization 3.6 on Red Hat Enterprise Linux 6 to Red Hat Virtualization 4.0 on Red Hat Enterprise Linux 7 no longer tries to connect to the Manager API as admin@internal, instead it prompts for the username, and defaults to admin@internal if no username is provided.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-06 13:11:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1455606

Description Simone Tiraboschi 2017-04-05 15:15:08 UTC

Description of problem:
The procedure for upgrading the engine VM from 3.6/el6 -> 4.0/el7 requires API access but it hardcodes the login as admin@internal while the user could also disable it on the engine.

So let's always ask an administrative login and not just the password proposing admin@internal as the default

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


How reproducible:
100%

Steps to Reproduce:
1. disable admin@internal on 3.6 engine
2. try upgrading the engine VM from 3.6/el6 -> 4.0/el7
3.

Actual results:
it requires admin@internal

Expected results:
It asks a different administrative user

Additional info:

Comment 1 Artyom 2017-06-11 13:34:24 UTC

Verified on ovirt-hosted-engine-setup-2.1.3-1.el7ev.noarch
[ INFO  ] Connecting to the Engine
[ ERROR ] The engine API didnt accepted the administrator password you provided Please enter it again to retry.
          Enter engine admin username [admin@internal]: admin@internal
          Enter engine admin password: 
[ INFO  ] Connecting to the Engine
[ INFO  ] Connecting to the Engine
[ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...

Comment 2 Yedidyah Bar David 2017-07-03 06:09:54 UTC

Byron - it's the other way around. It used to always use admin@internal, now it does not always use that - instead it prompts also for the username (and defaults to admin@internal).