@camunda/e2e-test-suite 0.0.1210 → 0.0.1211

package/dist/resources/test-api-v2-complete.sh

@@ -408,6 +408,15 @@ _curl_common() {
   # small for a pod restart; this widens it to ~90s. A sustained outage still
   # returns the real 502/503/504 once the budget is exhausted, so it surfaces
   # as a genuine FAILED (not masked).
+  #
+  # The orchestration REST API itself also answers 503 UNAVAILABLE ("The
+  # search client could not connect to the search server") while its search
+  # client is briefly unable to reach Elasticsearch/OpenSearch — e.g. while
+  # the search backend pod is rolling during an upgrade-minor run, the same
+  # window the nginx case above targets. That response carries a real JSON
+  # body (not nginx's HTML page), so the nginx-only check let it through as
+  # "final" and skipped the widened retry entirely. Treat it the same as the
+  # nginx 503.
   local gw_attempt=0 gw_max=12 gw_response gw_status
   while :; do
     gw_response="$(curl --http1.1 --max-time 30 --connect-timeout 10 \
@@ -417,7 +426,8 @@ _curl_common() {
     if [[ -n "$gw_status" && "$gw_status" != "502" \
           && "$gw_status" != "503" && "$gw_status" != "504" ]] \
        || [[ "$gw_status" == "503" \
-             && "$gw_response" != *'<center>nginx</center>'* ]] \
+             && "$gw_response" != *'<center>nginx</center>'* \
+             && "$gw_response" != *'could not connect to the search server'* ]] \
        || (( gw_attempt >= gw_max )); then
       printf '%s\n' "$gw_response"
       return 0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camunda/e2e-test-suite",
-  "version": "0.0.1210",
+  "version": "0.0.1211",
   "description": "End-to-end test helpers for Camunda 8",
   "repository": {
     "type": "git",

package/resources/test-api-v2-complete.sh

@@ -408,6 +408,15 @@ _curl_common() {
   # small for a pod restart; this widens it to ~90s. A sustained outage still
   # returns the real 502/503/504 once the budget is exhausted, so it surfaces
   # as a genuine FAILED (not masked).
+  #
+  # The orchestration REST API itself also answers 503 UNAVAILABLE ("The
+  # search client could not connect to the search server") while its search
+  # client is briefly unable to reach Elasticsearch/OpenSearch — e.g. while
+  # the search backend pod is rolling during an upgrade-minor run, the same
+  # window the nginx case above targets. That response carries a real JSON
+  # body (not nginx's HTML page), so the nginx-only check let it through as
+  # "final" and skipped the widened retry entirely. Treat it the same as the
+  # nginx 503.
   local gw_attempt=0 gw_max=12 gw_response gw_status
   while :; do
     gw_response="$(curl --http1.1 --max-time 30 --connect-timeout 10 \
@@ -417,7 +426,8 @@ _curl_common() {
     if [[ -n "$gw_status" && "$gw_status" != "502" \
           && "$gw_status" != "503" && "$gw_status" != "504" ]] \
        || [[ "$gw_status" == "503" \
-             && "$gw_response" != *'<center>nginx</center>'* ]] \
+             && "$gw_response" != *'<center>nginx</center>'* \
+             && "$gw_response" != *'could not connect to the search server'* ]] \
        || (( gw_attempt >= gw_max )); then
       printf '%s\n' "$gw_response"
       return 0