Under normal circumstances,the tunnel interface will not be reported to the <InterfaceParentEntry> database of odl.However,there will be some abnormal conditions that cause the tunnel interface to be reported to the <InterfaceParentEntry> datebase of odl.Moreover,the names of the parent interface and the sub-interface of the tunnel interface are the same, which leads to an infinite loop of recursive calls.
The following is LOG.info print,this print will continue in an infinite loop:

Binding Service default.tuna328e99cfbf for tuna328e99cfbf
Adding Interface stat Oper Ds for interface: tun10445754965
Binding service default.tun07a8566aeb0 for tun07a8566aeb0
Binding Service default.tun1044575496s for tun10445754965
Adding Interface State to Oper Ds for interface: tun6919c7309be
Binding service default.tun6919c7309be for tun6919c7309be
Adding Interface State to oper Ds for interface: tun 3dceob008e7
Adding Interface State Oper Ds for interface: tuna7465ofc96c
Binding service default.tun3de60b008e7 for tun3dc60b008e7
Adding Interface State Oper Ds for interface: tunb7flb369bbe
Binding service default tuna74650fc98c for: tuna74650fc96c
Adding Interface State Oper Ds for interface: tun26c586b1026
Binding service default.tun566ab2ea275 for tun566ab2ea27
Anding Service default.tun26c586b1c26 for tun26c586b1c26
Adding Interface State Oper Ds for interface: tune4aled953a4
Adding Interface State Oper Ds for interface: tuno68acdd3215
Binding service default.tune4aled953a4 for: tune4aled9s384
Adding Interface State Oper Ds for interface: tun632775b49ca
Binding Service default.tun068acdd3215 for : tun068acdd3215
Binding Service default.tun632775b4gca for : tune32775b49ca