Bug 1403675

Summary:	[RFE] [IPv6] - Allow and enable management network with only static ipv6 address
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	BLL.Network	Assignee:	eraviv
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:	Rolfe Dlugy-Hegwer <rdlugyhe>
Priority:	medium
Version:	4.1.0	CC:	bugs, danken, eraviv, mburman, mtessun, pkovar, rdlugyhe, rvdwees
Target Milestone:	ovirt-4.3.0	Keywords:	FutureFeature
Target Release:	---	Flags:	rule-engine: ovirt-4.3+ mburman: testing_plan_complete+ mtessun: planning_ack+ danken: devel_ack+ mburman: testing_ack+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, Red Hat Virtualization Manager did not handle hosts added to it over an IPV6-only network. In the current release, you can use the Manager's Administration Portal and REST API to add and manage hosts over a statically configured IPV6-only network.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-01 10:16:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1360839, 1467332, 1507543, 1507587, 1595130, 1597113, 1614345, 1665153
Bug Blocks:	1080725, 1576077

Description Michael Burman 2016-12-12 07:14:40 UTC

Description of problem:
[IPv6] - allow and enable management network with only ipv6 boot protocol.

Engine currently expect we set an ipv4 bootproto as well.

Cannot setup Networks. Role (migration/display/gluster) network 'aaa' hasn't boot protocol assigned.

Version-Release number of selected component (if applicable):
4.1.0-0.2.master.20161210231201.git26a385e.el7.centos

How reproducible:
100

Comment 2 Dan Kenigsberg 2018-08-12 09:18:56 UTC

Moving to MODIFIED as nothing is left to be done on Engine side, and in 4.3 we are going to support only static ipv6 addresses when adding a new host.

Comment 3 Michael Burman 2018-08-21 07:34:00 UTC

Note for QE - 

- Test scenario will be - Add host with only IPv6 static address
- Enable dhcpv6 + autoconf on ovirtmgmt

Comment 4 Michael Burman 2018-10-17 11:40:01 UTC

We are blocked from testing this RFE 

1. No support for default route IPV6 - this leave the host in out-of-sync state for the ovirtmgmt bridge

2. Can't mount nfs with ipv6 address - do we have a bug for that?

Comment 5 Michael Burman 2018-10-17 11:56:58 UTC

Eitan, do we have a bug for nfs storage connection over IPV6?

Comment 6 eraviv 2018-10-25 07:58:50 UTC

https://bugzilla.redhat.com/show_bug.cgi?id=1597113

Comment 9 Rolfe Dlugy-Hegwer 2019-01-18 01:07:58 UTC

Please tech review the updated Doc Text.

Comment 11 eraviv 2019-01-20 11:03:35 UTC

pleas ack the doc text

Comment 12 Michael Burman 2019-01-20 13:39:52 UTC

(In reply to eraviv from comment #11)
> pleas ack the doc text

ack

Comment 13 Michael Burman 2019-02-26 14:16:43 UTC

Verified on - 4.3.1.1-0.1.el7 with vdsm-4.30.9-1.el7ev
using rhvh-4.3.0.5-0.20190221.0+1

Comment 14 Sandro Bonazzola 2019-03-01 10:16:47 UTC

This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

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

Comment 15 eraviv 2019-04-07 08:21:10 UTC

Rolfe,

A caveat to the current doc text is that strictly speaking, the host deploy phase of adding a host to the manager requires an ipv4 configuration for the NIC on which it creates the initial management network. This is because it needs access to rpm repos which are only published on the ipv4 www. But after this phase completes and the host is 'up', the ipv4 configuration on any of the host networks can be set to 'none' and ipv6-only communication between the host and the manager is supported.

Thanks