Operating System: All
Platform: All

Updating the admin status in the Vbr interface.

First create the vbr interfaces if1 and if2 and do the portmapping.
Then in th emininet give ping:

Now update one of the interfaces as shown below:

curl --user admin:adminpass -H 'content-type: application/json' -X PUT -d '{"interface": {"if_name": "if1", "adminstatus" : "disable"}}' http://127.0.0.1:8083/vtn webapi/vtns/vtn1/vbridges/vBridge1/interfaces/if1

After running this command the interface should be disabled and its operstatus should go down, but it doesnot happen so:

Manish Kumar detected and reported this bug.
https://lists.opendaylight.org/pipermail/vtn-dev/2015-February/000851.html

First get a set-up for vtn manager and coordinator using the example,
L2 Network with single controller as shown on the below page :

https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):VTN_Coordinator:RestApi:L2_Network_Example_Using_VTN_Virtualization

After this one of the interfaces is disabled by updating the admin status. This should get the operation state of that interface down. The below command is used for this :

curl -v --user admin:adminpass -H 'content-type: application/json' -H 'ipaddr:127.0.0.1' -X PUT -d '{"interface": {"if_name": "if1","description": "if_desc1", "adminstatus": "disable"}}' http://127.0.0.1:8083/vtn-webapi/vtns/vtn_one/vbridges/vbr_one/interfaces/if1.json

From the VTN Manager GET command is checked :

curl -v --user "admin":"admin" -H "Accept: application/json" -H "Content-type: application/json" -X GET http://localhost:8080/controller/nb/v2/vtn/default/vtns/vtn_one/vbridges/vbr_one/interfaces/if1

This is a wrong behavior. The status should get updated in the vtn manager and the interface should do DOWN. When the adminstatus is disabled the Ping should also fail

Issue Scenario :

When the admin_status attribute of the Vbridge Itnerface is modified, the same change is not reflected in the VTN Manager of the corresponding ODL controller.

Reproduce the Bug :

First get a set-up for vtn manager and coordinator using the example:
L2 Network with single controller as shown on the below page :
https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):VTN_Coordinator:RestApi:L2_Network_Example_Using_VTN_Virtualization

Then update the vBr interface admin status using the below command :

curl -v --user admin:adminpass -H 'content-type: application/json' -H 'ipaddr:127.0.0.1' -X PUT -d '{"interface": {"if_name": "if1","description": "if_desc1", "adminstatus": "disable"}}' http://127.0.0.1:8083/vtn-webapi/vtns/vtn_one/vbridges/vbr_one/interfaces/if1.json

When the GET command is used in the Vtn manager to get the status of the interface:

curl -v --user "admin":"admin" -H "Accept: application/json" -H "Content-type: application/json" -X GET http://localhost:8080/controller/nb/v2/vtn/default/vtns/vtn_one/vbridges/vbr_one/interfaces/if1

This is the result :

Occurrence of the issue :

Update of the admin_status attribute in VTN Coordiantor.

The patch for this bug was merged into the master branch of the vtn.git.
https://git.opendaylight.org/gerrit/#/c/15715/

The patch for this bug was also merged into the stable/helium branch of the vtn.git.
https://git.opendaylight.org/gerrit/#/c/16385/