Merge pull request #24330 from vespa-engine/hmusum/handle-internal-server-error-from-config-server

Handle internal server error in response from config server as transi… [run-systemtest]

1 files changed, 4 insertions, 0 deletions

diff --git a/controller-server/src/main/java/com/yahoo/vespa/hosted/controller/deployment/InternalStepRunner.java b/controller-server/src/main/java/com/yahoo/vespa/hosted/controller/deployment/InternalStepRunner.java
index 4d7b84be65e..46c93c019ee 100644
--- a/controller-server/src/main/java/com/yahoo/vespa/hosted/controller/deployment/InternalStepRunner.java
+++ b/controller-server/src/main/java/com/yahoo/vespa/hosted/controller/deployment/InternalStepRunner.java
@@ -242,6 +242,10 @@ public class InternalStepRunner implements StepRunner {
                     logger.log("Deployment failed with possibly transient error " + e.code() +
                                ", will retry: " + e.getMessage());
                     return result;
+                case INTERNAL_SERVER_ERROR:
+                    // Log only error code, to avoid exposing internal data in error message
+                    logger.log("Deployment failed with possibly transient error " + e.code() + ", will retry");
+                    return result;
                 case LOAD_BALANCER_NOT_READY:
                 case PARENT_HOST_NOT_READY:
                     logger.log(e.message()); // Consider splitting these messages in summary and details, on config server.