feat(avm): error handling for address resolution #28072
Annotations
3 warnings
|
Setup and Test
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-0ab6454b6feb1a06d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6a.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "We currently do not have sufficient m6a.2xlarge capacity in the Availability Zone you requested (us-east-2b). Our system will be working on provisioning additional capacity. You can currently get m6a.2xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a, us-east-2c."
}
]
|
|
Setup and Test
[
{
"LaunchTemplateAndOverrides": {
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-0ab6454b6feb1a06d",
"Version": "1"
},
"Overrides": {
"InstanceType": "m6a.2xlarge"
}
},
"Lifecycle": "spot",
"ErrorCode": "InsufficientInstanceCapacity",
"ErrorMessage": "There is no Spot capacity available that matches your request."
}
]
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "jm-9131-error-handling-addr-resolution.protocol_circuits_report.json", "jm-9131-error-handling-addr-resolution.public_functions_report.json".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Loading