[VTN-63] OpenStack integration does not work in Helium SR3 Created: 26/Mar/15  Updated: 19/Oct/17  Resolved: 07/Jul/15

Status: Resolved
Project: vtn
Component/s: VTN Manager
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: dhandayadhapani bhoopalan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 2898

 Description   

Issue Scenario :

Network creation is getting failed in OpenStack integration with VTN as Network Provider

Reproduce the Bug:

First get a set-up for VTN Manager with controller using the example:
Install VTNManager to use VTN API(VTN Coordinator is not required):

https://wiki.opendaylight.org/view/Release/Helium/VTN/Installation_Guide.

After Controller is up then start stacking Openstack(Control Node) as in the below page:

https://wiki.opendaylight.org/view/Release/Helium/VTN/User_Guide/OpenStack_Support.

When Openstack is getting stacked, the network(OVS) creation is getting failed in the control node.

The Error message in the OpenStack log is:

2015-03-20 01:51:33.051 | [ERROR] /opt/stack/devstack/functions-common:534 Failure creating SUBNET_ID for eba3edb79f984e7392ff9551fcf0b487

The Error message in the ODL Controller is :

2015-03-20 01:51:25,997 | ERROR | -bio-8080-exec-7 | ContainerResponse | 165 - com.sun.jersey.jersey-server - 1.17.0 | Mapped exception to response: 503 (Service Unavailable)
org.opendaylight.controller.northbound.commons.exception.ServiceUnavailableException

Occurrence of the issue :

Occurs every time of integrating OpenStack with VTN



 Comments   
Comment by Ananthi Palaniswamy [ 07/Apr/15 ]

The OpenStack integration does not support only in Helium SR3

Comment by Hideyuki Tai [ 03/Jul/15 ]

The patches for the bug have been already merged.
https://git.opendaylight.org/gerrit/#/c/17330/ (master)
https://git.opendaylight.org/gerrit/#/c/18185/ (stable/helium)

Generated at Wed Feb 07 20:47:55 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.