CNI returns wrong interface name

[Michal Dulko]

As "name" field on CNI result we write down this from the VIF ovo: "vif_name":"tap39e238b5-cb". According to CNI spec we should return whatever is in CNI_IFNAME:

"interfaces describes specific network interfaces the plugin created. If the CNI_IFNAME variable exists the plugin must use that name for the sandbox/hypervisor interface or return an error if it cannot."

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/670141
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=ca222d4f5b9ed38122ceec32d2e98cf9abc3911f
Submitter: Zuul
Branch: master

commit ca222d4f5b9ed38122ceec32d2e98cf9abc3911f
Author: Alexey Perevalov <email address hidden>
Date: Wed Jul 10 18:05:44 2019 +0300

    Use CNI_IFNAME environment variable

    According to CNI spec kubelet expects CNI_IFNAME (the name
    inside container) if sandbox is not empty.

    Both python and golang implementation was done unconditionally,
    IOW we can add both empty sandbox and interface name on the
    host and nonempty sandbox and container's iface name.

    Closes-Bug: #1835038
    Change-Id: I3f21bc0c0790bb79ee81db361cd072609a0a3169
    Signed-off-by: Alexey Perevalov <email address hidden>

[OpenStack Infra (hudson-openstack)]

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