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
Flaky test: DockerSwarmSuite.TestPruneNetwork #27866
Comments
hmm looks like a network isn't being cleaned up correctly, from failing docker.log here https://gist.github.com/tophj-ibm/bd415b07affffd124eee5e45ac82e408 time="2016-10-28T19:02:59.242218000Z" level=debug msg=""Calling POST /v1.25/networks/create"
time="2016-10-28T19:02:59.242366000Z" level=debug msg="form data: {\"Attachable\":false,\"CheckDuplicate\":true,\"Driver\":\"overlay\",\"EnableIPv6\":false,\"IPAM\":{\"Config\":[],\"Driver\":\"default\",\"Options\":{}},\"Internal\":false,\"Labels\":{},\"Name\":\"n4\",\"Options\":{}}"
time="2016-10-28T19:02:59.243590000Z" level=error msg="Handler for POST /v1.25/networks/create returned error: network with name n4 already exists" |
This test was added in #27525 ping @AkihiroSuda ptal |
https://jenkins.dockerproject.org/job/Docker%20Master%20(arm)/3558/console seems hitting this. But AFAIK no test other than (bundle: https://jenkins.dockerproject.org/job/Docker%20Master%20(arm)/3571/)
Maybe the error string |
Reproduced during So the test failure is
Looking at the log (mine and @tophj-ibm 's #27866 (comment)) , the failure is caused when the ID of the e.g.
The ID is generated from here; it occasionally creates a network named |
I'll try to open PR that allows to create a network of which name is the prefix of the ID of the |
…f a swarm network Previously, it doesn't allow creating such a network: e.g. $ docker network inspect -f '{{.Id}}' ingress 84xh9knigj6zyt00u31e26nj3 $ docker network create 84 Error response from daemon: network with name 84 already exists Fix moby#27866 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
opened #27938 |
…f a swarm network Previously, it doesn't allow creating such a network: e.g. $ docker network inspect -f '{{.Id}}' ingress 84xh9knigj6zyt00u31e26nj3 $ docker network create 84 Error response from daemon: network with name 84 already exists Fix moby#27866 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
…f a swarm network Previously, it doesn't allow creating such a network: e.g. $ docker network inspect -f '{{.Id}}' ingress 84xh9knigj6zyt00u31e26nj3 $ docker network create 84 Error response from daemon: network with name 84 already exists Fix moby#27866 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
…f a swarm network Previously, it doesn't allow creating such a network: e.g. $ docker network inspect -f '{{.Id}}' ingress 84xh9knigj6zyt00u31e26nj3 $ docker network create 84 Error response from daemon: network with name 84 already exists Fix #27866 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp> (cherry picked from commit edfbc3b) Signed-off-by: Victor Vieux <vieux@docker.com>
…f a swarm network Previously, it doesn't allow creating such a network: e.g. $ docker network inspect -f '{{.Id}}' ingress 84xh9knigj6zyt00u31e26nj3 $ docker network create 84 Error response from daemon: network with name 84 already exists Fix moby#27866 Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
Seen flakily failing on arm and ppc64le.
unfortunately the Jenkins logs were deleted as I was making this, but I'm seeing it on my local power machine on master as well.
The text was updated successfully, but these errors were encountered: