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
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.
Note for QE - - Test scenario will be - Add host with only IPv6 static address - Enable dhcpv6 + autoconf on ovirtmgmt
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?
Eitan, do we have a bug for nfs storage connection over IPV6?
https://bugzilla.redhat.com/show_bug.cgi?id=1597113
Please tech review the updated Doc Text.
pleas ack the doc text
(In reply to eraviv from comment #11) > pleas ack the doc text ack
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
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.
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