Bug 1618676 - [RFE] add IPv6 support to ovirt-hosted-engine-setup
Summary: [RFE] add IPv6 support to ovirt-hosted-engine-setup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ovirt-4.3.0
: ---
Assignee: Simone Tiraboschi
QA Contact: Michael Burman
URL:
Whiteboard:
: 1571216 (view as bug list)
Depends On: 1467332 1618433
Blocks: RHEV_IPv6 1372134
TreeView+ depends on / blocked
 
Reported: 2018-08-17 09:43 UTC by Dominik Holler
Modified: 2019-03-01 10:16 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-03-01 10:16:50 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.3+
mavital: testing_plan_complete?
mtessun: planning_ack+
sbonazzo: devel_ack+
mburman: testing_ack+


Attachments (Terms of Use)
seesion log with the proposed modifications (458.97 KB, text/plain)
2018-08-17 09:43 UTC, Dominik Holler
no flags Details

Description Dominik Holler 2018-08-17 09:43:52 UTC
Created attachment 1476592 [details]
seesion log with the proposed modifications

Description of problem: Deployment of hosted engine should work in IPv6-only scenarios.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install ovirt-hosted-engine-setup ovirt-engine-appliance
2. Disable IPv4 and enable IPv6
3. hosted-engine --deploy


Actual results:
Deployment fails in multiple steps 

Expected results:
Deployment succeeds.

Additional info:
https://gerrit.ovirt.org/#/c/93367/ highlights the code locations which has to be modified for IPv6 support.
Additional to this changes, IPv6 has to be enabled in
libvirt's default network, which is used for the temporary VM:

echo 2 > /proc/sys/net/ipv6/conf/eth0/accept_ra
systemctl start libvirtd
virsh net-edit default
# add the line
# <ip family='ipv6' address='fd00:1234:5678:900::1'
prefix='64'/>  
virsh net-destroy default
virsh net-start default

The IPv6 address in libvirt's network is not important, it is only
important to enable IPv6.

The host has to be configured using a static IPv6 address, e.g.:

echo "fde4:e66c:9a7c:dd91::2 ipv6test9" >> /etc/hosts
echo "fde4:e66c:9a7c:dd91::3 hengine.local" >> /etc/hosts
echo IPV6INIT="yes" >> /etc/sysconfig/network-scripts/ifcfg-eth0
echo IPV6ADDR="fde4:e66c:9a7c:dd91::2/64" \
  >> /etc/sysconfig/network-scripts/ifcfg-eth0  
echo BOOTPROTO="none" >> /etc/sysconfig/network-scripts/ifcfg-eth0
echo IPV6_AUTOCONF="no" >> /etc/sysconfig/network-scripts/ifcfg-eth0
systemctl restart network

Comment 1 Yaniv Lavi 2018-08-23 10:41:59 UTC
*** Bug 1571216 has been marked as a duplicate of this bug. ***

Comment 2 Sandro Bonazzola 2018-09-21 07:07:25 UTC
Not identified as blocker for 4.2.7, moving to 4.2.8

Comment 3 Dominik Holler 2018-12-17 15:45:24 UTC
Is this a duplicate of bug 1372134?

Comment 4 Michael Burman 2019-01-28 14:14:51 UTC
Hi Simone, please see Dominik's need info from comment 3^^
Is this a duplicate of bug 1372134?

Comment 5 Simone Tiraboschi 2019-01-30 15:05:05 UTC
(In reply to Michael Burman from comment #4)
> Hi Simone, please see Dominik's need info from comment 3^^
> Is this a duplicate of bug 1372134?

The only difference is that 1372134 has been opened downstream specific.
You can verify them together.

Comment 6 Sandro Bonazzola 2019-02-12 07:43:17 UTC
Anything blocking this bug fix verifcation?

Comment 8 Michael Burman 2019-02-27 09:12:07 UTC
Verified on - ovirt-hosted-engine-setup-2.3.5-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
ovirt-ansible-hosted-engine-setup-1.0.11-1.el7ev.noarch
4.3.1.1-0.1.el7
vdsm-4.30.9-1.el7ev.x86_64
using rhvh-4.3.0.5-0.20190225.0+1 and rhvm-appliance-4.3-20190220.2.el7.x86_64

Verified with and over an IPv6 static address only

Comment 9 Sandro Bonazzola 2019-03-01 10:16:50 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.


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