conf: avoid looking up network port that doesn't exist
conf: avoid looking up network port that doesn't exist

If the hypervisor driver has not yet created the network port, the
portid field will be "00000000-0000-0000-0000-000000000000".

If a failure occurs during early VM startup, the hypervisor driver may
none the less try to release the network port, resulting in an
undesirable warning:

2019-09-12 13:17:42.349+0000: 16544: error :
virNetworkObjLookupPort:1679 : network port not found: Network port with
UUID 00000000-0000-0000-0000-000000000000 does not exist

By checking if the portid UUID is valid, we can avoid polluting the logs
in this way.

Reviewed-by: Michal Privoznik <83d82aaba2eed257f4814b0c239c260c4caaadf0@redhat.com>
Signed-off-by: Daniel P. Berrangé <bb938cf255e055ff3507f2627d214e8e62118fcf@redhat.com>

nertpinx/libvirt,libvirt/libvirt,nertpinx/libvirt,zippy2/libvirt,fabianfreyer/libvirt,jfehlig/libvirt,olafhering/libvirt,libvirt/libvirt,andreabolognani/libvirt,zippy2/libvirt,andreabolognani/libvirt,jardasgit/libvirt,fabianfreyer/libvirt,jfehlig/libvirt,nertpinx/libvirt,crobinso/libvirt,zippy2/libvirt,crobinso/libvirt,olafhering/libvirt,zippy2/libvirt,crobinso/libvirt,nertpinx/libvirt,olafhering/libvirt,fabianfreyer/libvirt,olafhering/libvirt,andreabolognani/libvirt,jfehlig/libvirt,andreabolognani/libvirt,jardasgit/libvirt,fabianfreyer/libvirt,nertpinx/libvirt,libvirt/libvirt,fabianfreyer/libvirt,jfehlig/libvirt,libvirt/libvirt,jardasgit/libvirt,andreabolognani/libvirt,jardasgit/libvirt,jardasgit/libvirt,crobinso/libvirt