"Element not found" error when hot attaching endpoint to container about hcsshim HOT 9 CLOSED

We ran the above reproduction for about 10 times with 17079 image, and haven't seen the Eelement not found error yet. I wonder if this is something that has been resolved, can someone confirm this?

from hcsshim.

What is the full container host version? (Either from docker info, or powershell '$psversiontable.BuildVersion')

I'm not aware of any changes in this area.

@msabansal @JMesser81 Do you know of any recent fixes here?

from hcsshim.

@darrenstahlmsft This is the docker info output for 17079. We have certainly seen this with 1709, but it could be that we haven't had enough mileage on 17079 yet.

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 2
Server Version: master-dockerproject-2018-01-23
Storage Driver: windowsfilter
 Windows:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: ics l2bridge l2tunnel nat null overlay transparent
 Log: awslogs etwlogs fluentd gelf json-file logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 17079 (17079.1001.amd64fre.rs_prerelease.180113-2149)
Operating System: Windows Server Standard
OSType: windows
Architecture: x86_64
CPUs: 4
Total Memory: 8GiB
Name: VAGRANT-ALOR7AV
ID: OGZ3:DALU:HSVN:ZUOF:4VAR:L3NP:YLLN:Q5JJ:MKZ7:WESN:COXJ:5VKB
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

from hcsshim.

Oh, I see, this is comparing the latest insider preview build to 1709. I know there's been a lot of reliability work going into this release, but I don't know specifics on the networking side. Hopefully one of the networking folks I pinged has some more info

from hcsshim.

@darrenstahlmsft The element not found actually does show up in 17079, so I don't think this issue has been fixed in the latest insider preview. We are looking forward to the final release of 1803 and hoping to close this issue.

from hcsshim.

@darrenstahlmsft We are testing the 1803 and still seeing the element not found show up in our pipelines. Please let us know if you need more information.

from hcsshim.

@aminjam It wasn't reproing for me when I tried it. I will check this out. If you have a repro getting these traces will help identify the issue.

netsh trace start globallevel=5 provider=Microsoft-Windows-Host-Network-Service level=5 provider={80CE50DE-D264-4581-950D-ABADEEE0D340} level=6 provider=microsoft-windows-winnat level=5 provider=Microsoft-Windows-TCPIP level=5 report=di

from hcsshim.

It turns out our CI failures were not during hot attach of endpoints (they were actually showing up while creating several HNS networks in parallel). Our reproduction from the issue description no longer produces failures either. We think we can close this out @darstahl @mdelillo

from hcsshim.

@sesmith177 Thanks for confirming

from hcsshim.