-
Notifications
You must be signed in to change notification settings - Fork 243
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
Hns: POST after DELETE doesn't work without a delay #95
Comments
This is probably because of a delay in applying bindings to the external network adapter when the transparent network is deleted. Will look into this |
I tried this on an RS2 build and it doesn't seem to be a problem. I will try reproducing this on Windows Server 2016.
|
Forgot to mention, I'm using Server 2016. |
@m-kostrzewa Ok it seems that this is happening because our logic dictates binding transparent networks to Network adapters with IPv4 addresses. When the network is deleted it takes some time for the reinitialized adapter to acquire IP which leads to the failure as we can't select the adapter till it has acquired the IP. One of the workaround would be to specify the network adapter by specifying the name using the com.docker.network.windowsshim.interface option |
Hmm.. Can't get it to work... |
I did a similar experiment:
So it seems like you get "element not found" when Ethernet is in Disconnected state, and "unspecified error" when it's in Up state, but has no IP yet? @msabansal, could you describe in a little bit more detail how to perform the workaround you mentioned? This doesn't seem to work:
|
We ran into a similar issue with a similar reproduction. We encountered this on Windows Server 1709 and 1803, but it looks to be resolved in 2019. |
Changing base layer order
Deleting a HNS network and then creating another one immediately after doesn't work. Here's the error message:
Here's a test case:
Note that sleeping for 20 seconds after deleting a network seems to "fix" the issue. 10 second timeout is not enough.
update: I repeated this in Powershell, so this may be problem with HNS. I posted an issue here: MicrosoftDocs/Virtualization-Documentation#516
The text was updated successfully, but these errors were encountered: