Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1549229 - IPv6 not disabled with OOO ODL container deployment
IPv6 not disabled with OOO ODL container deployment
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-opendaylight (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
urgent Severity high
: beta
: 13.0 (Queens)
Assigned To: Tim Rozet
Itzik Brown
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-26 13:48 EST by Tim Rozet
Modified: 2018-10-18 03:20 EDT (History)
7 users (show)

See Also:
Fixed In Version: puppet-opendaylight-7.0.0-0.20180216174117
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
N/A
Last Closed: 2018-06-27 09:45:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenDaylight Bug INTPAK-117 None None None 2018-02-26 13:59 EST
OpenDaylight gerrit 68783 None None None 2018-02-26 14:48 EST
Red Hat Product Errata RHEA-2018:2086 None None None 2018-06-27 09:46 EDT

  None (edit)
Description Tim Rozet 2018-02-26 13:48:55 EST
Description of problem:
In puppet-odl we allow for the passing of java options to the systemd service.  The default options include disabling the IPv6 stack in JVM.  However, in container deployment we do not use systemd.  Therefore when ODL starts it is listening on a IPv6.  We need to modify how we configure java options in puppet-opendaylight.
Comment 7 Itzik Brown 2018-04-03 03:45:34 EDT
Checked that the java process has:
-Djava.net.preferIPv4Stack=true

ODL isn't listening on IPv6
Comment 10 errata-xmlrpc 2018-06-27 09:45:51 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2086

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