Understand "No route to host" as an expected error message from stunnel, and turn that into API error WLB_UNKNOWN_HOST if we see it when contacting WLB.
This is two patches, one for xen-api-libs.hg, and one for xen-api.hg.
Signed-off-by: Ewan Mellor <ewan.mellor@eu.citrix.com>
check_verify_error line;
check_error "Connection refused" line;
check_error "No host resolved" line;
+ check_error "No route to host" line;
check_error "Invalid argument" line in
Unixext.readfile_line check_line st_proc.logfile
(* If we reach here the whole stunnel log should have been gone through