Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1848901

Summary:	OCPRHV-206: When trying to resolve engine FQDN, let's try to strip it from both ends
Product:	OpenShift Container Platform	Reporter:	Jan Zmeskal <jzmeskal>
Component:	Installer	Assignee:	Douglas Schilling Landgraf <dougsland>
Installer sub component:	OpenShift on RHV	QA Contact:	Lucie Leistnerova <lleistne>
Status:	CLOSED WORKSFORME	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	dougsland
Version:	4.6	Keywords:	UpcomingSprint
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
URL:	https://issues.redhat.com/browse/OCPRHV-206
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-19 15:03:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Zmeskal 2020-06-19 08:11:19 UTC

Description of problem:
Before we ask user for authentication data, we try to resolve provided engine FQDN. However, if the user provides a valid engine FQDN that is either prefixed with "https://" or suffixed e.g. with "/ovirt-engine", the installation exits as this address cannot be resolved. I know this is technically correct, as https://engine.com/ovirt-engine/api is not really a FQDN. However I think the UX would be better if, in such case, we first stripped http(s) prefix and whatever follows after top-level domain (.com, .org, .us), and only after that tried to resolve the FQDN.

Version-Release number of the following components:
openshift-install-linux-4.6.0-0.nightly-2020-06-19-020835

How reproducible:
100 %

Steps to Reproduce:
1. Run openshift-install create install-config
2. Provide some valid engine FQDN either preffixed with https:// or suffixed with /ovirt-engine

Comment 1 Douglas Schilling Landgraf 2020-06-19 15:03:35 UTC

Hey Jan,

Thanks for this report. I believe we should be fine as it's. FQDN is common keyword for sysadmins and also avoid adding more logic's in the code.
On top of that, our help is straightforward:

? Engine FQDN[:PORT] ?
? The Engine FQDN[:PORT] (engine.example.com:443)

Closing this bug report but fell free to re-open if you still consider we must address it.