Bug 1713304 - Fail to deploy hosted-engine with --6 on a dual-stack host
Summary: Fail to deploy hosted-engine with --6 on a dual-stack host
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: 2.3.8
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ovirt-4.3.6
: 2.3.12
Assignee: Simone Tiraboschi
QA Contact: Roni
URL:
Whiteboard:
Depends On:
Blocks: 1734432
TreeView+ depends on / blocked
 
Reported: 2019-05-23 11:09 UTC by Roni
Modified: 2019-09-26 19:43 UTC (History)
5 users (show)

Fixed In Version: ovirt-hosted-engine-setup-2.3.12
Clone Of:
Environment:
Last Closed: 2019-09-26 19:43:12 UTC
oVirt Team: Integration
Embargoed:
sbonazzo: ovirt-4.3?
sbonazzo: planning_ack?
sbonazzo: devel_ack+
sbonazzo: testing_ack?


Attachments (Terms of Use)
screen capture (58.50 KB, text/plain)
2019-05-23 11:09 UTC, Roni
no flags Details
hosted-engine log (577.79 KB, text/plain)
2019-05-23 11:09 UTC, Roni
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 100350 0 ovirt-hosted-engine-setup-2.3 MERGED Ignore addresses with unexpected IP version 2019-07-12 11:39:30 UTC
oVirt gerrit 101768 0 None None None 2019-07-29 13:29:57 UTC

Description Roni 2019-05-23 11:09:07 UTC
Created attachment 1572442 [details]
screen capture

Description of problem:
Fail to deploy hosted-engine with --6 on a dual-stack host


Version-Release number of selected component (if applicable):
rhvh-4.3.0.8-0.20190516.0+1
ovirt-ansible-hosted-engine-setup-1.0.18-1.el7ev.noarch
python2-ovirt-host-deploy-1.8.0-1.el7ev.noarch
ovirt-host-deploy-common-1.8.0-1.el7ev.noarch
ovirt-hosted-engine-setup-2.3.8-1.el7ev.noarch
ovirt-ansible-engine-setup-1.1.9-1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install RHVH
2. Set host interface to support IPv4 (DHCP) & IPv6 (Static)
3. run hosted-engine --deploy --6

Actual results:
Got an error 
[ ERROR ] The Engine VM (2620:52:0:2e1e:21a:4aff:fe23:1707/24) and this host (10.46.30.2/24) will not be in the same IP subnet.
         Static routing configuration are not supported on automatic VM configuration.

(Note that it adds the mask '24' to the IPv6 address, although it was not entered)

Expected results:
It is expected that the IPv4 will be ignored when entering --6 at the CLI
And the setup will be finished successfully

Additional info:
The setup continues to run after the error and fails at the end
see attached:
1. screen capture
2. engine-setup log

Comment 1 Roni 2019-05-23 11:09:47 UTC
Created attachment 1572443 [details]
hosted-engine log

Comment 2 Dominik Holler 2019-05-28 07:51:25 UTC
(In reply to Roni from comment #0)
> Created attachment 1572442 [details]
> screen capture
> 
> Description of problem:
> Fail to deploy hosted-engine with --6 on a dual-stack host
> 

From my point of view, dual-stack is not expected to work, I expect only IPv6 only scenarios to work.
Simone and Ales, do you agree?

Comment 3 Dominik Holler 2019-05-28 07:54:29 UTC
Admin guide in https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/administration_guide/index#IPv6-networking-support-labels says:
"Dual-stack addressing, IPv4 and IPv6, is not supported."

Comment 4 Ales Musil 2019-05-28 07:58:05 UTC
(In reply to Dominik Holler from comment #2)
> (In reply to Roni from comment #0)
> > Created attachment 1572442 [details]
> > screen capture
> > 
> > Description of problem:
> > Fail to deploy hosted-engine with --6 on a dual-stack host
> > 
> 
> From my point of view, dual-stack is not expected to work, I expect only
> IPv6 only scenarios to work.
> Simone and Ales, do you agree?

Yes

Comment 5 Simone Tiraboschi 2019-05-28 08:14:37 UTC
(In reply to Dominik Holler from comment #3)
> Admin guide in
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/
> html-single/administration_guide/index#IPv6-networking-support-labels says:
> "Dual-stack addressing, IPv4 and IPv6, is not supported."

As for https://bugzilla.redhat.com/show_bug.cgi?id=1676928 , we provided --4 and --6 options as a best effort approach to help upstream users with dual stacks environments (often configured like that just by mistake) but it's definitively not supported in RHV.

Comment 8 Sandro Bonazzola 2019-07-11 07:03:31 UTC
Re-targeting to 4.3.6 not being identified as blocker for 4.3.5.

Comment 9 Roni 2019-08-04 14:54:54 UTC
This should be ON_QA because:
Version 4.3.6-1-001 does not include the fix: 'ovirt-hosted-engine-setup-2.3.12'
(Instead, it includes ovirt-hosted-engine-setup-2.3.11-1.el7ev.noarch)
The problem still exists at 2.3.11-1
Change to Modify

Comment 10 Roni 2019-08-04 14:57:07 UTC
Correction adding "not"

(In reply to Roni from comment #9)
> This should not be ON_QA because:
> Version 4.3.6-1-001 does not include the fix:
> 'ovirt-hosted-engine-setup-2.3.12'
> (Instead, it includes ovirt-hosted-engine-setup-2.3.11-1.el7ev.noarch)
> The problem still exists at 2.3.11-1
> Change to Modify

Comment 11 Roni 2019-08-19 16:04:46 UTC
Verified: 4.3.6.1-0.1.el7

ovirt-hosted-engine-setup-2.3.12-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.4-1.el7ev.noarch

Note that during HE deployment it required to answer ‘Yes’ for the question below:
Add lines for the appliance itself and for this host to /etc/hosts on the engine VM? 
      	Note: ensuring that this host could resolve the engine VM hostname is still up to you
(Yes, No)[No] yes

Comment 12 Sandro Bonazzola 2019-09-26 19:43:12 UTC
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 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.


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