Exception recovering ports in use without K8S_ANNOTATION_VIF

[Luis Tomas Bolivar]

When the port_debug is disabled and the ports belonging to the pools need to be recovered, we make use of the kubernetes API to discover what ports are being used by the running pods and obtain its IDs based on the K8S_ANNOTATION_VIF information. However, it may happen that some pods do not have the K8S_ANNOTATION_VIF as they are not associated to a neutron port (for instance, the router pod in OpenShift) as they are associated to the host instead.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/509364

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/509364
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=a9cb42897aee292753bb618cfe4344cda9bcd56d
Submitter: Jenkins
Branch: master

commit a9cb42897aee292753bb618cfe4344cda9bcd56d
Author: Luis Tomas Bolivar <email address hidden>
Date: Wed Oct 4 09:26:05 2017 +0200

    Add exception handling to _get_in_use_ports

    This patch skips the pods without kuryr annotations when
    recovering the IDs of the ports that are being used by
    running pods.

    Moreover, as part of the unit test additions, it also moves
    some tests to the BaseVIFPOOL as they are independent of the
    Pool driver

    Closes-Bug: 1721194
    Change-Id: I70828c1459b4100975bf20d6193db69303451cae

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kuryr-kubernetes 0.3.0 release.