You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When describing an InstanceType like "t3a.large" or "t3a.xlarge" in returned 'InstanceTypeInfo' information about vCPUs is empty - VCpuInfo is nil.
In comparison MemoryInfo is fine and has all the details.
aws-sdk-go v1 does not have this issue and works as expected.
Thanks for reporting this issue @r0kas, I can confirm this behavior and have narrowed it down to a deserialization bug. We will have this fixed in our next release.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Fixes b4b2263. The sdk had a bug where
it was not deserializing responses correctly
(aws/aws-sdk-go-v2#910).
Other changes are:
- `LoadDefaultConfig` accepts now a context object
- `github.com/aws/aws-sdk-go-v2/ec2imds` moved to
`github.com/aws/aws-sdk-go-v2/feature/ec2/imds`
- `github.com/awslabs/smithy-go` moved to `github.com/aws/smithy-go`
Signed-off-by: Vlad Ungureanu <vladu@palantir.com>
Fixes b4b2263. The sdk had a bug where
it was not deserializing responses correctly
(aws/aws-sdk-go-v2#910).
Other changes are:
- `LoadDefaultConfig` accepts now a context object
- `github.com/aws/aws-sdk-go-v2/ec2imds` moved to
`github.com/aws/aws-sdk-go-v2/feature/ec2/imds`
- `github.com/awslabs/smithy-go` moved to `github.com/aws/smithy-go`
Signed-off-by: Vlad Ungureanu <vladu@palantir.com>
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug
When describing an InstanceType like "t3a.large" or "t3a.xlarge" in returned 'InstanceTypeInfo' information about vCPUs is empty -
VCpuInfo
is nil.In comparison
MemoryInfo
is fine and has all the details.aws-sdk-go v1 does not have this issue and works as expected.
Version of AWS SDK for Go?
v0.29.0
Version of Go (
go version
)?v1.15.2
To Reproduce (observed behavior)
Output: nil
Expected behavior
Expected output:
{
DefaultCores: 1,
DefaultThreadsPerCore: 2,
DefaultVCpus: 2,
ValidCores: [1],
ValidThreadsPerCore: [1,2]
}
Additional context
Tried this out on "t3a.large" and "t3a.xlarge" instance types. Same behavior on both.
aws-sdk-go v1 works as expected.
The text was updated successfully, but these errors were encountered: