From 7a166cd356a9ada2067de9099bd394b7be9cf8c4 Mon Sep 17 00:00:00 2001 From: Sanne Raymaekers Date: Fri, 22 Nov 2024 15:27:00 +0100 Subject: [PATCH] awscloud/secure-instance: log error code comparisons We're seeing some behaviour where create fleet is not retried and subsequently the SI cleanup fails due to the security group already being tied to an existing instance. There is no error that an instance was launched anyway. --- internal/cloud/awscloud/secure-instance.go | 1 + 1 file changed, 1 insertion(+) diff --git a/internal/cloud/awscloud/secure-instance.go b/internal/cloud/awscloud/secure-instance.go index 19c6dc84b..18fd5129d 100644 --- a/internal/cloud/awscloud/secure-instance.go +++ b/internal/cloud/awscloud/secure-instance.go @@ -639,6 +639,7 @@ func doCreateFleetRetry(cfOutput *ec2.CreateFleetOutput) (bool, []string) { msg := []string{} retry := false for _, err := range cfOutput.Errors { + logrus.Infof("Checking to retry fleet create on error %s (msg: %s)", *err.ErrorCode, *err.ErrorMessage) if slices.Contains(retryCodes, *err.ErrorCode) { retry = true }