Uploaded image for project: 'genius'
  1. genius
  2. GENIUS-92

TEP info in ITM config datastore can not be deleted

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • None
    • Carbon
    • General
    • None
    • Operating System: All
      Platform: All

    • 9259

      TEP info in ITM config datastore can not be deleted by following the procedure of the ODL document.

      • : where we expect to be deleted
        {
        "transport-zones": {
        "transport-zone": [
        {
        "zone-name": "e383ab7e-a92c-4c7c-84cf-e797270799c2",
        "tunnel-type": "odl-interface:tunnel-type-vxlan",
        "subnets": [
        {
        "vteps": [
      • { "dpn-id": 229274253668002, "portname": "tunnel_port", "option-of-tunnel": false, "ip-address": "10.0.0.20" }

        ,

        { "dpn-id": 118908811792816, "portname": "tunnel_port", "option-of-tunnel": false, "ip-address": "10.0.0.10" }

        ],
        "gateway-ip": "0.0.0.0",
        "vlan-id": 0
        }
        ]
        }
        ]
        }
        }

      Procedure in ODL document::
      ITM Tunnel Auto-Configuration
      http://docs.opendaylight.org/en/stable-carbon/submodules/genius/docs/specs/itm-tunnel-auto-config.html
       TEP Deletion
      When an openvswitch:external_ids:tep-ip parameter gets deleted through ovs-vsctl command, then network topology Operational
      DS gets updated via OVSB update notification. ITM which has registered for the network-topology DTCNs, gets notified and this
      deletes the TEP from Transport zone or tepsNotHostedInTransportZone stored in ITM config DS based on external_ids:tzname
      parameter configured for TEP.

      Environment Details
      OpenStack Version: stable/ocata
      ODL Version: carbon-FR

      Reproduction steps:
      1. Initialize ODL
      2. Connect (Set up) ControllerNode, ComputeNode with ODL
      3. Create NW, router, VM
      4. Confirm data is created in MD-SAL
      restconf/config/itm:transport-zones
      5. Delete NW, router, VM
      6. Execute the following command in compute node

      1. ovs-vsctl remove Open_vSwitch <UUID> external_ids tep-ip="10.0.0.20"

      Attachment List:
      genius-itm-config.xml
      karaf.tar.gz
      itm-transportzone.config
      network-topology.config
      network-topology.operational
      controller.ovsdb-client_dump
      compute.ovsdb-client_dump

      Possible cause:
      Unable to get the TransportZone which contains the TEP should be removed.
      Karaf log:
      2017-09-26 19:26:37,350 | TRACE | nPool-1-worker-3 | OvsdbTepRemoveConfigHelper | 353 - org.opendaylight.genius.itm-impl - 0.2.0.Carbon | Remove TEP: TEP-IP: 10.0.0.20, TZ name: TZA, DPID: 00:00:d0:86:12:72:2e:a2
      2017-09-26 19:26:37,351 | TRACE | nPool-1-worker-3 | OvsdbTepRemoveConfigHelper | 353 - org.opendaylight.genius.itm-impl - 0.2.0.Carbon | Removing TEP from unknown TZ into teps-not-hosted-in-transport-zone.
      2017-09-26 19:26:37,351 | TRACE | nPool-1-worker-3 | OvsdbTepRemoveConfigHelper | 353 - org.opendaylight.genius.itm-impl - 0.2.0.Carbon | Unhosted TransportZone does not exist. Nothing to do for TEP removal.

        1. genius-itm-config.xml
          0.3 kB
        2. itm-transportzone.config
          0.8 kB
        3. karaf.tar.gz
          270 kB
        4. network-topology.config
          5 kB
        5. network-topology.operational
          21 kB
        6. ocata-compute.ovsdb-client_dump
          13 kB
        7. ocata-controller.ovsdb-client_dump
          27 kB

            tarunODLF Tarun Thakur
            ran-xiao@vf.jp.nec.com Ran Xiao
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: