Bug 1439281 – Upgrading procedures hardcodes admin@internal

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1439281 - Upgrading procedures hardcodes admin@internal

Summary:	Upgrading procedures hardcodes admin@internal

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	ovirt-hosted-engine-setup
Classification:	oVirt
Component:	Plugins.General (Show other bugs)
Sub Component:
Version:	2.1.0.4
Hardware:	Unspecified Unspecified

Priority	high Severity high (vote)
Target Milestone:	ovirt-4.1.3
Target Release:	2.1.1
Assigned To:	Simone Tiraboschi
QA Contact:	Artyom
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:	1455606
	Show dependency tree / graph

Reported:	2017-04-05 11:15 EDT by Simone Tiraboschi
Modified:	2017-07-17 18:57 EDT (History)
CC List:	4 users (show)

See Also:
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 09:11:19 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Integration
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	rule-engine: ovirt‑4.1+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	76168	master	MERGED	engineapi: avoid hardcoding admin@internal	2017-05-23 01:41 EDT
oVirt gerrit	77148	ovirt-hosted-engine-setup-2.1	MERGED	engineapi: avoid hardcoding admin@internal	2017-05-24 15:09 EDT

Groups: None (edit)

Description Simone Tiraboschi 2017-04-05 11:15:08 EDT

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 09:34:24 EDT

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 02:09:54 EDT

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).

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