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):
No, I be believe we need to teach it in ovirt too.
After consulting with Elad, this issue should be checked in RHHI env, moving this bug to Sas(sasundar)
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 ?.
Any update on when this is planned for testing?
Hi, is the verification of this bug planned?
(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
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
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.