Fix istio test scenario endpoint API validation

Current query issued at the end of testcase to
istio service API didn't validate the case, when
http server responded with 5XX http code. By
reusing common wrapper for cURL, this is now
handled properly.

Issue-ID: MULTICLOUD-686

Signed-off-by: Konrad Bańka <k.banka@samsung.com>
Change-Id: Ifb73494c9a6d98143edccaad095b2de5d456ef4f

diff --git a/kud/tests/istio.sh b/kud/tests/istio.sh
index c525bb8..e9ef00c 100755 (executable)
--- a/kud/tests/istio.sh
+++ b/kud/tests/istio.sh
@@ -36,5 +36,5 @@ for deployment in details-v1 productpage-v1 ratings-v1 reviews-v1 reviews-v2 rev
 done
 INGRESS_PORT=$(kubectl -n istio-system get service istio-ingressgateway -o jsonpath='{.spec.ports[?(@.name=="http2")].nodePort}')
 INGRESS_HOST=$(kubectl get po -l istio=ingressgateway -n istio-system -o 'jsonpath={.items[0].status.hostIP}')
-curl -o /dev/null -s -w "%{http_code}\n" http://$INGRESS_HOST:$INGRESS_PORT/productpage
+call_api http://$INGRESS_HOST:$INGRESS_PORT/productpage >/dev/null
 popd