-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WaitUntilNetworkInterfaceAvailableWithContext does not block with InvalidNetworkInterfaceID.NotFound error #4282
Comments
Hi, is this still persisting with the latest version of SDK? |
Hi @vudh1 , the issue is still persisting with the latest version of the SDK. |
Hi @mzampetakis , This is quite an old issue. I apologize for not getting to this sooner. If this is still an issue with the Go SDK v2, please open a new issue there and I will take a look. Thanks again, |
Comments on closed issues are hard for our team to see. |
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug
Invoking
WaitUntilNetworkInterfaceAvailableWithContext
with a non existing Network IDreturns immediately with an error. The same happens in cases that Network is not available (e.g. right after the
CreateNetworkInterface
invocation). I would expect thatWaitUntilNetworkInterfaceAvailableWithContext
blocks for a period of time (10 attempts * 20" by default) until it fails with aResourceNotReady
error.Currently the error returned is
InvalidNetworkInterfaceID.NotFound
.Version of AWS SDK for Go?
1.42.9
Version of Go (
go version
)?go version go1.17.3 darwin/amd64
To Reproduce (observed behavior)
Expected behavior
In the code presented above, I would expect having the
WaitUntilNetworkInterfaceAvailableWithContext
to block the execution for the whole period of the polling time (10 attempts * 20") as the Network is not found (as it has not even created). But instead of this, it immediately returns an error with typeInvalidNetworkInterfaceID.NotFound
.Additional context
The same issue affects the
WaitUntilNetworkInterfaceAvailable
which directly invokes theWaitUntilNetworkInterfaceAvailableWithContext
.The possible solution to this is to remove the acceptor
from the
WaitUntilNetworkInterfaceAvailableWithContext
acceptors.I have prepared a branch with the required change
but it requires changes to the
models/apis/ec2/2016-11-15/waiters-2.json
which, based on the guidelines requires to open an issue first instead of a PR.The text was updated successfully, but these errors were encountered: