From 15e1cf8573de08a8454f957f3c47e94e4584c58a Mon Sep 17 00:00:00 2001 From: Jacek Kaniuk Date: Wed, 27 Nov 2019 20:44:52 +0100 Subject: [PATCH] Decrease verbosity of Prometheus firewall rule checking Prow log viewer extracts its output as an error --- run-e2e-with-prometheus-fw-rule.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/run-e2e-with-prometheus-fw-rule.sh b/run-e2e-with-prometheus-fw-rule.sh index d7597809b0..ec40282172 100755 --- a/run-e2e-with-prometheus-fw-rule.sh +++ b/run-e2e-with-prometheus-fw-rule.sh @@ -20,7 +20,7 @@ set -o pipefail # Add firewall rule for Prometheus port (9090) if [[ -n "${KUBE_GKE_NETWORK:-}" ]]; then - if ! gcloud compute firewall-rules describe "${KUBE_GKE_NETWORK}-9090" > /dev/null; then + if ! gcloud compute firewall-rules describe "${KUBE_GKE_NETWORK}-9090" > /dev/null 2>&1; then PROMETHEUS_RULE_NAME="${KUBE_GKE_NETWORK}-9090" echo "Prometheus firewall rule not found, creating..." echo COMMAND: gcloud compute firewall-rules create --network "${KUBE_GKE_NETWORK}" --source-ranges 0.0.0.0/0 --allow tcp:9090 "${PROMETHEUS_RULE_NAME}"