Add None label statement for proper toremove

[v-kamerdinerov]

Looks like there was already a similar problem as long as 2 years ago.

#1107

I checked, indeed If you add processing of a missing Label, the address deletion is successful

exabgp.conf

name = rhel01
interval = 5
command = curl -sf http://10.30.3.13:9005/healthcheck
ip = 10.30.4.3
ip = 10.30.4.4
start-ip = 2
ip = 10.30.4.5
next-hop = 10.30.3.13
withdraw-on-down
dynamic-ip-setup

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet 10.30.4.5/32 scope global lo
       valid_lft forever preferred_lft forever
    inet 10.30.4.4/32 scope global lo
       valid_lft forever preferred_lft forever
    inet 10.30.4.3/32 scope global lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

Add some debug and shutoff monitored service

DEBUG[healthcheck] Loopback addresses: [Pv4Network('10.30.4.5/32'), IPv4Network('10.30.4.4/32'), IPv4Network('10.30.4.3/32')]
INFO[healthcheck] ips= [IPv4Network('10.30.4.5/32'), IPv4Network('10.30.4.3/32'), IPv4Network('10.30.4.4/32')]
INFO[healthcheck] existing= {IPv4Network('10.30.4.4/32'), IPv4Network('10.30.4.3/32'), IPv4Network('10.30.4.5/32')}
INFO[healthcheck] toremove= {IPv4Network('10.30.4.5/32'), IPv4Network('10.30.4.4/32'), IPv4Network('10.30.4.3/32')}
DEBUG[healthcheck] Remove loopback IP address 10.30.4.5/32
DEBUG[healthcheck] Remove loopback IP address 10.30.4.4/32
DEBUG[healthcheck] Remove loopback IP address 10.30.4.3/32

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

voila