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. |
||
|---|---|---|
| .. | ||
| awscloud | ||
| gcp | ||
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. |
||
|---|---|---|
| .. | ||
| awscloud | ||
| gcp | ||