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

Bug 1607362

Summary: [Deployment] ODL doesnot boot on IPv6 network
Product: Red Hat OpenStack Reporter: Janki <jchhatba>
Component: puppet-opendaylightAssignee: Janki <jchhatba>
Status: CLOSED ERRATA QA Contact: Noam Manos <nmanos>
Severity: high Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: aadam, jjoyce, jschluet, mariel, mkolesni, nyechiel, slinaber, tvignaud
Target Milestone: z4Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Deployment
Fixed In Version: puppet-opendaylight-8.2.2-4.9126c8dgit.el7ost Doc Type: Enhancement
Doc Text:
This feature adds support for deploying OpenDaylight (ODL) on IPv6 addresses.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-16 17:55:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1488821    
Attachments:
Description Flags
karaf logs for all 3 ODL containers none

Description Janki 2018-07-23 11:14:45 UTC 
Created attachment 1469922 [details]
karaf logs for all 3 ODL containers

Description of problem:
ODL doesnot boot when deployed on IPv6 network with TripleO.

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


How reproducible:
Always

Steps to Reproduce:
1. Deploy OSP13 + ODL on IPv6 internal network

Actual results:
ODL doesnot boot

Expected results:
ODL should boot

Additional info:
All ODL related ports are listening on IPv6 address.
$ sudo netstat -ntlp | grep java
tcp6       0      0 :::44444                :::*                    LISTEN      37342/java          
tcp6       0      0 :::42271                :::*                    LISTEN      37342/java          
tcp6       0      0 ::1:35747               :::*                    LISTEN      37342/java          
tcp6       0      0 fd00:fd00:fd00:2000::1e:8101 :::*                    LISTEN      37342/java          
tcp6       0      0 127.0.0.1:1099          :::*                    LISTEN      37342/java          
tcp6       0      0 fd00:fd00:fd00:2000::1e:8081 :::*                    LISTEN      37342/java

curl -g -v -u admin:admin http://[fd00:fd00:fd00:2000::1e]:8081/restconf/operational/network-topology:network-topology/topology/netvirt:1 gives 404.

Few error snippets:
2018-07-21T06:47:26,855 | ERROR | paxweb-extender-2-thread-1 | EnvironmentLoader                | 144 - org.apache.shiro.web - 1.3.2 | Shiro environment initialization failed
java.lang.RuntimeException: Error obtaining AAAShiroProvider

2018-07-21T06:47:26,731 | ERROR | Blueprint Extender: 3 | BlueprintContainerImpl           | 81 - org.apache.aries.blueprint.core - 1.8.3 | Unable to start blueprint container for bundle org.opendaylight.genius.idmanager-shell/0.4.3.redhat-1 due to unresolved dependencies [(objectClass=org.opendaylight.genius.idmanager.api.IdManagerMonitor)]
java.util.concurrent.TimeoutException: null

and many more blueprints error.

DiagStatus service is started
2018-07-21T06:42:28,003 | INFO  | features-1-thread-1 | DiagStatusServiceImpl            | 272 - org.opendaylight.infrautils.diagstatus-impl - 1.3.3.redhat-1 | DiagStatusServiceImpl started

but it registers other services as inactive due to missing dependencies.

Features installed are:
"odl-jolokia", "odl-netvirt-openstack"

I tried reversing the feature sequence and got the same results.

EXTRA_JAVA_OPTS: '-Djava.net.preferIPv6Addresses=true'
Comment 1 Janki 2018-07-23 16:23:24 UTC 
Akka cluster URL ip needs to be inside [ ] for IPv6 addresses.
Comment 2 Janki 2018-08-01 10:41:23 UTC 
The issue was missing [ ] around IPv6 address in akka.conf file. See port 2550 missing in above netstat command.

Relevant changes are being made in puppet (patch linked in External trackers).
Comment 3 Janki 2018-11-26 11:28:33 UTC 
*** Bug 1653247 has been marked as a duplicate of this bug. ***
Comment 19 errata-xmlrpc 2019-01-16 17:55:03 UTC 
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/RHBA-2019:0068