Skip to content
This repository was archived by the owner on Dec 7, 2023. It is now read-only.
This repository was archived by the owner on Dec 7, 2023. It is now read-only.

flaky volume e2e test when using docker + CNI #679

@darkowlzz

Description

@darkowlzz

The volume e2e test is observed to fail frequently with Docker + CNI :

=== RUN   TestVolumeWithDockerAndCNI

    TestVolumeWithDockerAndCNI: run_volume_test.go:120: assertion failed: error is not nil: exit status 1: vm stop: 

        ["/home/travis/build/weaveworks/ignite/bin/ignite" "--runtime=docker" "--network-plugin=cni" "stop" "e2e_test_volume_docker_and_cni"]

        time="2020-08-31T04:45:29Z" level=info msg="Removing the container with ID \"ignite-d54e77eeaa408deb\" from the \"cni\" network"

        time="2020-08-31T04:45:31Z" level=fatal msg="failed to stop container for VM \"d54e77eeaa408deb\": Error response from daemon: No such container: ignite-d54e77eeaa408deb"

It passes on restarting the test, mostly.

Docker + CNI never worked on my development machine (ubuntu 18.04) but it works on TravisCI for all of the other e2e tests.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/testingIssues related to improving testing

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions