Bug 1403677

Summary:	[IPv6] - allow and enable gluster network with only ipv6 boot protocol
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	BLL.Network	Assignee:	eraviv
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1.0	CC:	aefrat, aoconnor, bugs, danken, dholler, eraviv, mburman, mkalinin, mtessun, rdlugyhe, sasundar, sgoodman
Target Milestone:	ovirt-4.4.1	Keywords:	FutureFeature
Target Release:	---	Flags:	pm-rhel: ovirt-4.4+ mtessun: planning_ack+ dholler: devel_ack+ bshetty: testing_ack+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.4	Doc Type:	Enhancement
Doc Text:	With this update, you can connect to a Gluster storage network over IPv6, without the need for IPv4.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-05 06:25:37 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:	1618669, 1676886
Bug Blocks:	1080725, 1721383

Description Michael Burman 2016-12-12 07:21:18 UTC

Description of problem:
[IPv6] - allow and enable gluster 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 3 Dan Kenigsberg 2018-12-18 19:21:27 UTC

No, I be believe we need to teach it in ovirt too.

Comment 6 Avihai 2019-04-15 07:55:39 UTC

After consulting with Elad, this issue should be checked in RHHI env, moving this bug to Sas(sasundar)

Comment 8 RHEL Program Management 2019-04-15 08:18:29 UTC

This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 9 eraviv 2019-04-28 10:09:00 UTC

Hi sasundar,

Any update on when this is planned for testing?

thanks

Comment 10 Dominik Holler 2019-06-20 16:11:30 UTC

Hi, is the verification of this bug planned?

Comment 11 SATHEESARAN 2019-07-17 11:10:26 UTC

(In reply to Dominik Holler from comment #10)
> Hi, is the verification of this bug planned?

Yes, IPv6 support with RHHI-V is planned to be in RHHI-V 1.7.
This bug will be verified as part of that feature validation

Comment 17 SATHEESARAN 2020-07-16 13:00:15 UTC

verified with RHVH 4.4.1 with IPV6 only network.

1. 3 node cluster with self-hosted engine is deployed with pure IPV6 FQDN
2. glusterfs storage domains are created
3. New logical network is created with available interface and this network has role of 'gluster' and 'migration network'
4. Attached that network to host

All works good

Comment 18 Sandro Bonazzola 2020-08-05 06:25:37 UTC

This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

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