Bug 1676928

Summary:	Add flags to let the user explicitly force IPv6 or IPv4
Product:	[oVirt] ovirt-hosted-engine-setup	Reporter:	Simone Tiraboschi <stirabos>
Component:	Network	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	2.3.2	CC:	bugs, mburman
Target Milestone:	ovirt-4.3.1	Flags:	sbonazzo: ovirt-4.3?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-hosted-engine-setup-2.3.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-01 10:17:46 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 Simone Tiraboschi 2019-02-13 15:57:43 UTC

Description of problem:
Not the setup chooses to deploy the engine VM with IPv4 or IPv6 according to how the host address got resolved (as other tools do) but this could be confusing or error prone in mixed env not properly configured.

Let's add a couple of flags to force IPv4 or IPv6; they should be added also on the cockpit wizard.

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

How reproducible:
100%

Steps to Reproduce:
1. try to deploy hosted-engine on a mixed IPv4/IPv6 env
2.
3.

Actual results:
There is no way to explicitly choose between IPv4 and IPv6

Expected results:
The user can user -4 or -6 flags to force IPv4 or IPv6; they have to be added also to the cockpit wizard.


Additional info:

Comment 1 Michael Burman 2019-02-27 08:58:38 UTC

The user can now explicitly force IPv4 or IPv6 

By Running cmd 

hosted-engine --deploy --4
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup

hosted-engine --deploy --6
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup


--4 Force IPv4 on dual stack env

--6 Force IPv6 on dual stack env

Verified on - ovirt-hosted-engine-setup-2.3.5-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
ovirt-ansible-hosted-engine-setup-1.0.11-1.el7ev.noarch
4.3.1.1-0.1.el7
vdsm-4.30.9-1.el7ev.x86_64
using rhvh-4.3.0.5-0.20190225.0+1 and rhvm-appliance-4.3-20190220.2.el7.x86_64

Comment 2 Sandro Bonazzola 2019-03-01 10:17:46 UTC

This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.