Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
unspecified
-
None
-
None
-
Operating System: All
Platform: All
-
2844
Description
I observed that the REST API of VTN Manager did not work at all when I installed the feature "odl-vtn-manager-all" with the feature "odl-integration-compatible-with-all".
I observed this issue on the Karaf distribution for integration tests which I built from the source code of the integration.git on 03/13 2015 (PDT).
How to reproduce the issue
==========================
1. Build a Karaf distribution for integration tests.
$ cd
{integration.git} $ cd distributions/test
$ mvn clean install -DskipTests
2. Run the Karaf.
$ cd target/assembly
$ ./bin/karaf
3. Install features on the Karaf console.
opendaylight-user@root> feature:install odl-integration-compatible-with-all odl-openflowplugin-flow-services-ui odl-openflowplugin-adsal-compatibility odl-vtn-manager-all
4. Wait until VTN Manager bundles become "Active".
You can check the state of VTN Manager bundles by executing the following command.
bundle:list | grep vtn
5. Call the REST API of VTN Manager.
$ curl -v --user "admin":"admin" -H "Accept: application/json" -H \
"Content-type: application/json" -X GET \
http://localhost:8282/controller/nb/v2/vtn/default/vtns
The response message from the controller should contain the empty VTN list, and the response code should be 200.
However, the response code was 503 (Service Unavailable), and response message was "VTN Manager: Service is not available. Could be down for maintanence".
Error log message
=================
When I called the REST API, the controller output the following ERROR message into the karaf.log.
2015-03-13 20:07:53,582 | ERROR | -bio-8282-exec-1 | ContainerResponse | 108 - com.sun.jersey.jersey-server - 1.17.0 | Mapped exception to response: 503 (Service Unavailable)
org.opendaylight.controller.northbound.commons.exception.ServiceUnavailableException
at org.opendaylight.vtn.manager.northbound.VTNNorthBoundBase.serviceUnavailable(VTNNorthBoundBase.java:133)[491:org.opendaylight.vtn.manager.northbound:0.3.0.SNAPSHOT]
at org.opendaylight.vtn.manager.northbound.VTNNorthBoundBase.getVTNManager(VTNNorthBoundBase.java:180)[491:org.opendaylight.vtn.manager.northbound:0.3.0.SNAPSHOT]
at org.opendaylight.vtn.manager.northbound.VTenantNorthbound.getTenants(VTenantNorthbound.java:89)[491:org.opendaylight.vtn.manager.northbound:0.3.0.SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.7.0_65]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_65]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_65]
at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_65]
For your investigation, I attached the karaf.log on the issue into this bug report.
Complementary Information
=========================
When I just installed the feature odl-vtn-manager-all, the REST API of VTN Manager worked fine.