While checking that the controller is up, we don't care about

certificate validity, the user could be deploying with self-signed
certs.

refs #18791

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <ward@curii.com>

diff --git a/arvados/controller/service/running.sls b/arvados/controller/service/running.sls
index 7f6af5136609ae3b63ed0f4df78927496df63fce..edd0476e839e59241b393390357a451b137a08b8 100644 (file)
--- a/arvados/controller/service/running.sls
+++ b/arvados/controller/service/running.sls
@@ -25,7 +25,7 @@ arvados-controller-service-running-service-running:
 arvados-controller-service-running-service-ready-cmd-run:
   cmd.run:
     - name: |
 arvados-controller-service-running-service-ready-cmd-run:
   cmd.run:
     - name: |

-        while ! (curl -s {{  arvados.cluster.Services.Controller.ExternalURL }} | \
+        while ! (curl -k -s {{  arvados.cluster.Services.Controller.ExternalURL }} | \

                  grep -qE "req-[a-z0-9]{20}.{5}error_token") do
           echo 'waiting for API to be ready...'
           sleep 1
                  grep -qE "req-[a-z0-9]{20}.{5}error_token") do
           echo 'waiting for API to be ready...'
           sleep 1