vxlan-gpe: lisp/one l2 arp entry fails to delete

[Onong Tayeng]

When the gpe listener receives a gpe port delete event from etcd, it deletes the remote mapping entry for the port as well the one l2 arp entry. Before deleting the one l2 arp entry, it checks for the existence of the entry in VPP. This check fails because the IP address returned by PAPI is the Python IPv4Address object whereas the gpe listener expects the binary address.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/749239

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/749239
Committed: https://git.openstack.org/cgit/x/networking-vpp/commit/?id=009afc36f68a791a0e7ed3cccd79aed39576bdc6
Submitter: Zuul
Branch: master

commit 009afc36f68a791a0e7ed3cccd79aed39576bdc6
Author: Onong Tayeng <email address hidden>
Date: Tue Sep 1 16:14:19 2020 +0530

    vxlan-gpe: lisp l2 arp entry fails to delete

    When the gpe listener receives a gpe port delete event from etcd, it
    deletes the remote mapping entry for the port as well the lisp l2
    arp entry. Before deleting the l2 arp entry, it checks for the
    existence of the entry in VPP. This check fails because the IP address
    returned by PAPI is the Python IPv4Address object whereas the gpe
    listener expects the binary address.

    Change-Id: I3935daf12c5b96fad56c46c970580582ad47f8a4
    Closes-Bug: #1893766