Fix bug in ip -> hypervisor retrieval

Fix bug in ip -> hypervisor retrieval

the bug was being hit when the ip address of the compute node
in question matched the substring of the ip address of another
compute node in the hypervisor list output.

example:
10.30.170.5 was matching on 10.30.170.5 -and- 10.30.170.56.

This was probably not happening often, but it did happen here:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-openstack-ocata-upstream-stateful-carbon/245/log_full.html.gz#s1-s8-t7-k3-k3-k4

Change-Id: I89a8ae514db7b089ce337dcf6819a271f2b61562
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>