Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1507543

Summary: ovn-controller: ovs|01240|stream_ssl|ERR|ssl:${ipv6_addr}: connect: Address family not supported by protocol
Product: [oVirt] ovirt-provider-ovn Reporter: Jiri Belka <jbelka>
Component: driverAssignee: Dominik Holler <dholler>
Status: CLOSED CURRENTRELEASE QA Contact: Roni <reliezer>
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: bugs, danken, dholler, lsvaty, mburman, mmirecki, ylavi
Target Milestone: ovirt-4.2.7Flags: rule-engine: ovirt-4.2+
rule-engine: ovirt-4.3+
mburman: testing_plan_complete-
mburman: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-provider-ovn-0:1.2.15-0.20180829124916.git2cfaeef.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-02 14:30:01 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: 1614345    
Bug Blocks: 1403675    

Description Jiri Belka 2017-10-30 14:26:19 UTC
Description of problem:

when having a host with ipv6 only address, i see:

Oct 30 14:29:03 10-37-138-251 ovn-controller: ovs|01239|socket_util|ERR|2620:52:0:2588:21a:4aff:fed0:402f:6642: bad IPv4 address "2620"
Oct 30 14:29:03 10-37-138-251 ovn-controller: ovs|01240|stream_ssl|ERR|ssl:2620:52:0:2588:21a:4aff:fed0:402f:6642: connect: Address family not supported by protocol

iiuc the ipv6 address should be in squre brackets.

see http://openvswitch.org/support/dist-docs/ovn-controller.8.html

# grep -IR 2620:52 /etc/openvswitch/ 
/etc/openvswitch/conf.db:{"_date":1509360015500,"Open_vSwitch":{"43f90197-78c0-40c0-a35a-268703be4515":{"external_ids":["map",[["hostname","10-37-138-251.example.com"],["ovn-encap-ip","10.37.138.251"],["ovn-encap-type","geneve"],["ovn-remote","ssl:2620:52:0:2588:21a:4aff:fed0:402f:6642"],["system-id","61c1f415-f319-4d5e-93bb-b3bc3c714452"]]]}},"_comment":"ovs-vsctl (invoked by /bin/sh): ovs-vsctl --no-wait set open . external-ids:ovn-remote=ssl:2620:52:0:2588:21a:4aff:fed0:402f:6642"}

/etc/openvswitch/conf.db:{"_date":1509360015680,"Open_vSwitch":{"43f90197-78c0-40c0-a35a-268703be4515":{"external_ids":["map",[["hostname","10-37-138-251.example.com"],["ovn-encap-ip","2620:52:0:2588:21a:4aff:fed0:403f"],["ovn-encap-type","geneve"],["ovn-remote","ssl:2620:52:0:2588:21a:4aff:fed0:402f:6642"],["system-id","61c1f415-f319-4d5e-93bb-b3bc3c714452"]]]}},"_comment":"ovs-vsctl (invoked by /bin/sh): ovs-vsctl --no-wait set open . external-ids:ovn-encap-ip=2620:52:0:2588:21a:4aff:fed0:403f"}


Version-Release number of selected component (if applicable):
ovirt-host-deploy-1.7.0-0.0.master.20170912090102.git1eeb5a2.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. have 4.2 engine with ipv4 and ipv6 address
2. add a host with has only ipv6 address
3. tail -f /var/log/messages on host

Actual results:
log full of errors about bad ipv6 address

Expected results:
should work nicely with ipv6

Additional info:

Comment 2 Jiri Belka 2017-10-31 12:57:53 UTC
is the issue related to this line which i found during host deployment?

Oct 31 13:46:05 localhost python: ansible-command Invoked with warn=True executable=None _uses_shell=False _raw_params=vdsm-tool ovn-config 2620:52:0:2588:21a:4aff:fed0:402f 2620:52:0:2588:21a:4aff:fed0:4034 removes=None creates=None chdir=None stdin=None

^^ ie. without square brackets.

Comment 3 Dominik Holler 2017-11-01 08:41:34 UTC
Thanks Jiri for finding and the isolation of the issue. This looks like a solvable problem on the integration of ovirt-provider-ovn-driver in vdsm.

Comment 4 Michael Burman 2018-08-28 07:24:19 UTC
Dominik, what is the ovirt-provider-ovn version that has the fix?

Comment 5 Dominik Holler 2018-08-28 07:26:36 UTC
1.2.15 will contain the fix

Comment 6 Dan Kenigsberg 2018-08-30 20:06:59 UTC
Available for testing with ovirt-provider-ovn-0:1.2.15-0.20180829124916.git2cfaeef.el7. Note that you should update ovirt-provider-ovn-driver on the host.

Comment 7 Dominik Holler 2018-09-10 10:30:54 UTC
how to verify:
1. enable IPv6 for engine's FQDN on engine's environment:
   echo "2620:52:0:2588:21a:4aff:fe01:3f4e 10-37-140-135.rhev.lab.eng.brq.redhat.com" >> /etc/hosts
   ping -c 1 -6 10-37-140-135.rhev.lab.eng.brq.redhat.com
2. Add or reinstall IPv6 host, engine.log show show that the variable host_deploy_ovn_central is set to an IPv6 address, e.g.
Executing Ansible command:  [/usr/bin/ansible-playbook, ...
--extra-vars=host_deploy_ovn_tunneling_interface=2620:52:0:2588:21a:4aff:fed0:401c,
--extra-vars=host_deploy_ovn_central=2620:52:0:2588:21a:4aff:fe01:3f4e, ...

3. ensure that ovn-central is listening to IPv6 https://bugzilla.redhat.com/1614345
  ovn-sbctl set-connection pssl:6642:[::]
  netstat -antuop | grep ov[sn]
3. check that ovn-controller is connected
  ssh root@2620:52:0:2588:21a:4aff:fed0:401c tail  /var/log/openvswitch/ovn-controller.log

Comment 8 Roni 2018-10-07 14:52:46 UTC
Verified on downstream: 4.2.7.2-0.1.el7ev
ovirt-provider-ovn-1.2.16-1.el7ev.noarch

Comment 9 Roni 2018-10-08 07:33:21 UTC
Note: to verify, it requires that the ovn-provider FQDN and the Host FQDN will be resolved to IPv6.
To simulate I define both at the /etc/hosts of the Engine machine.

Comment 10 Sandro Bonazzola 2018-11-02 14:30:01 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

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