> and look for status code 418

so if you look at the "doc" (cough) in INFRAUTILS-33, what you might want to do instead is just look for any "non-200" (=sth, NOK) status code, instead?

yeah, and/or if I could read java code better too... LOL

here's a patch to do this in robot
https://git.opendaylight.org/gerrit/#/c/71527/

but, we will still want a patch to do this with curl/wget in our releng/builder deploy scripts.

This is jut 2 files in releng/builder:

jjb/integration/distribution/distribution-check-bootup.sh
jjb/integration/integration-deploy-controller-run-test.sh
jjb/integration/integration-start-cluster-run-test.sh

we just need to replace this section by the new REST call:

echo "Waiting up to 6 minutes for controller to come up, checking every 5 seconds..."
COUNT="0"
while true; do
    COUNT=$(( ${COUNT} + 5 ))
    sleep 5
    echo "already waited ${COUNT} seconds..."
    if grep --quiet 'org.opendaylight.infrautils.ready-impl.*System ready' "${WORKSPACE}/${BUNDLEFOLDER}/data/log/karaf.log"; then
        echo "Controller is UP"
        break
    elif (( "${COUNT}" > "360" )); then
        echo "Timeout Controller DOWN"
        dump_log_and_exit
    fi
done