Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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