+++ This bug was initially created as a clone of Bug #1507587 +++ Description of problem: related to BZ1507543, ie. trying to have ipv6 only host up. ovsdb-server listens by default only on ipv4, not very helpful to conquer networks which must use ipv6. see http://openvswitch.org/support/dist-docs/ovsdb-server.1.html # netstat -antuop | grep ov[sn] tcp 0 0 0.0.0.0:6641 0.0.0.0:* LISTEN 5065/ovsdb-server off (0.00/0/0) tcp 0 0 0.0.0.0:6642 0.0.0.0:* LISTEN 5073/ovsdb-server off (0.00/0/0) tcp 0 0 10.37.138.234:6642 10.37.138.244:49144 ESTABLISHED 5073/ovsdb-server off (0.00/0/0) # grep -IR 664[12] /var/lib/openvswitch/ /var/lib/openvswitch/ovnnb_db.db:{"_date":1507900220199,"NB_Global":{"d9ada689-f11a-4820-927c-f0c6ba42b019":{"connections":["uuid","643f6975-9f69-4196-a19e-d1d54b9d58d1"]}},"_comment":"ovs-nbctl: ovn-nbctl set-connection pssl:6641","Connection":{"643f6975-9f69-4196-a19e-d1d54b9d58d1":{"target":"pssl:6641"}}} /var/lib/openvswitch/ovnsb_db.db:{"_date":1507900220253,"SB_Global":{"1610f49e-f448-4532-bdef-201123681f9b":{"connections":["uuid","e80b7f7c-643b-4ace-8321-1071d5e5a63a"]}},"_comment":"ovs-sbctl: ovn-sbctl set-connection pssl:6642","Connection":{"e80b7f7c-643b-4ace-8321-1071d5e5a63a":{"target":"pssl:6642"}}} Version-Release number of selected component (if applicable): ovirt-engine-setup-4.2.0-0.0.master.20171029154613.git19686f3.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. have os with ipv6 address too 2. engine-setup 3. see if ovs stuff listens on ipv6 addresses as well Actual results: ovs stuff does not listen on ipv6 Expected results: should listen Additional info: --- Additional comment from Dan Kenigsberg on 2018-07-12 18:12:45 IDT --- Hopefully this can be solved on OVS side. If RHV needs to intervene, we'd clone the bug. --- Additional comment from Jakub Sitnicki on 2018-07-31 16:52:03 IDT --- Dan, Jiri, ovsdb-server supports listening on both IPv4 and IPv6. It can be enabled by setting the listening address to '::' (IPv6 wildcard address, all zeros). In terms of configuration commands this translates to: $ ovn-nbctl set-connection 'pssl:6641:[::]' $ ovn-sbctl set-connection 'pssl:6642:[::]' By default, that is if you don't specify the address, ovsdb-server listens only on IPv4. This behavior is also documented in ovsdb-server(1) man-page under the '--remote' option. Works with OVS/OVN v2.7+. I'm guessing you are already using 'set-connection' to enable SSL and so it would seem like a viable solution to adjust the commands to also specify the listening address. If that does not work for you, please let me know and we'll reopen the issue. Thanks, Jakub
Available for testing with nightly build ovirt-engine-0:4.2.6.5-0.0.master.20180829082211.git3013edd.el7
verified on nightly build: 4.2.6.5_SNAPSHOT openvswitch-2.9.0-56.el7fdp.x86_64 openvswitch-ovn-central-2.9.0-56.el7fdp.x86_64 openvswitch-ovn-common-2.9.0-56.el7fdp.x86_64 openvswitch-selinux-extra-policy-1.0-7.el7fdp.noarch python-openvswitch-2.9.0-56.el7fdp.noarch ovirt-engine-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-api-explorer-0.0.1-1.el7ev.noarch ovirt-engine-backend-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-cli-3.6.8.1-1.el7ev.noarch ovirt-engine-dashboard-1.2.4-1.el7ev.noarch ovirt-engine-dbscripts-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-dwh-4.2.4.3-1.el7ev.noarch ovirt-engine-dwh-setup-4.2.4.3-1.el7ev.noarch ovirt-engine-extension-aaa-jdbc-1.1.7-1.el7ev.noarch ovirt-engine-extensions-api-impl-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-lib-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-metrics-1.1.7-1.el7ev.noarch ovirt-engine-restapi-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch ovirt-engine-setup-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-setup-base-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-setup-plugin-ovirt-engine-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-setup-plugin-websocket-proxy-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-tools-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-tools-backup-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-vmconsole-proxy-helper-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-webadmin-portal-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch ovirt-engine-websocket-proxy-4.2.6.5_SNAPSHOT-104.g25610802.0.scratch.master.el7ev.noarch python-ovirt-engine-sdk4-4.2.8-1.el7ev.x86_64
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.