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

Bug 1594823

Summary:	Deployment should fail early if bridge name is not ovirtmgmt
Product:	[oVirt] ovirt-hosted-engine-setup	Reporter:	Ido Rosenzwig <irosenzw>
Component:	General	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED NOTABUG	QA Contact:	meital avital <mavital>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.2.23	CC:	benjamin.merot, bugs, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-26 10:06:28 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:

Description Ido Rosenzwig 2018-06-25 13:42:15 UTC

Description of problem:

Since we have 'ovirtmgmt' hard-coded in different places in the code as the expected bridge name, we should do the following:
1. Verify the bridge name at an early stage
2. Remove the bridge name from the answerfile as it shouldn't be altered


How reproducible:
100%

Steps to Reproduce:
1. Deploy hosted-engine with 
'OVEHOSTED_NETWORK/bridgeName=str:something' in the answerfile


Actual results:
Deployment failing on 'Create hosted engine local vm' stage

Expected results:
Deployment should fail in before the deployment starts

Comment 1 Yaniv Kaul 2018-06-26 08:28:02 UTC

There was a reason we wanted to allow this flexibility. I also don't think this is documented as a requirement somewhere.

Comment 2 Ido Rosenzwig 2018-06-26 10:06:28 UTC

closing this bug as NOTABUG.

Comment 3 Benjamin Merot 2018-06-26 11:48:30 UTC

What is that flexibility mentioned since the installation does not work if the host is not setup with a bridge named ovirtmgmt? And shouldn't there be documentation reflecting either?

Comment 4 Yaniv Kaul 2018-06-26 11:53:53 UTC

(In reply to Benjamin Merot from comment #3)
> What is that flexibility mentioned since the installation does not work if
> the host is not setup with a bridge named ovirtmgmt? And shouldn't there be
> documentation reflecting either?

Well, we need to fix this if possible.
I'm not entirely sure we support, end-to-end, the ability to use a different name   - but we really need to look into it. There's a good chance that even if we set (in Engine) the DefaultManagementNetwork to be something other than ovirtmgmt, it still doesn't work. But the solution is to fix it, not enforce that name.