Skip to content

Quarantine flaky k8s integ spec

Dan Davison requested to merge qa-quarantine-kubernetes_integration_spec into master

What does this MR do?

Quarantining an unfortunately flaky smoke test.

Test has been failing intermittently:

Error from: #225315 (closed)

Stacktrace

Expand stack trace 
Executing `docker pull registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1`
Using default tag: latest
latest: Pulling from gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1
745d0f80490d: Pulling fs layer
a7c4df765a7a: Pulling fs layer
a7c4df765a7a: Verifying Checksum
a7c4df765a7a: Download complete
745d0f80490d: Download complete
745d0f80490d: Pull complete
a7c4df765a7a: Pull complete
Digest: sha256:f11984a81ce28740bd016e2c7b45dbdb592d24a22763a5fb9056eb5c748588ab
Status: Downloaded newer image for registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1:latest
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `docker run -d --rm --network bridge --hostname k3s.bridge --name k3s --publish 6443:6443 --privileged registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1 server --cluster-secret some-secret `
82665da51abf6c511c6b457aa2d15637d7f05741ce21bd8dea266f6e04e0cd14
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `kubectl config set-cluster k3s --server https://k3s.bridge:6443 --insecure-skip-tls-verify`
Cluster "k3s" set.
Executing `kubectl config set-credentials default --username=node --password=some-secret`
User "default" set.
Executing `kubectl config set-context k3s --cluster=k3s --user=default`
Context "k3s" created.
Executing `kubectl config use-context k3s`
Switched to context "k3s".
Executing `docker network inspect test`
[]
Error: No such network: test
Waiting for K3s server at `https://k3s.bridge:6443` to become available ............................................................checking for kubectl... yes
I, [2020-07-07T15:49:25.582409 #22]  INFO -- : Setting application settings: {:allow_local_requests_from_web_hooks_and_services=>true}
Executing `docker pull registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1`
Using default tag: latest
latest: Pulling from gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1
Digest: sha256:f11984a81ce28740bd016e2c7b45dbdb592d24a22763a5fb9056eb5c748588ab
Status: Image is up to date for registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1:latest
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `docker run -d --rm --network bridge --hostname k3s.bridge --name k3s --publish 6443:6443 --privileged registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1 server --cluster-secret some-secret `
docker: Error response from daemon: Conflict. The container name "/k3s" is already in use by container "82665da51abf6c511c6b457aa2d15637d7f05741ce21bd8dea266f6e04e0cd14". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
D, [2020-07-07T15:49:26.866561 #22] DEBUG -- : 
Starting test: Configure Kubernetes Cluster Integration Project Clusters can create and associate a project cluster
checking for kubectl... yes
I, [2020-07-07T15:49:26.868466 #22]  INFO -- : Setting application settings: {:allow_local_requests_from_web_hooks_and_services=>true}
Executing `docker pull registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1`
Using default tag: latest
latest: Pulling from gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1
Digest: sha256:f11984a81ce28740bd016e2c7b45dbdb592d24a22763a5fb9056eb5c748588ab
Status: Image is up to date for registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1:latest
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `docker run -d --rm --network bridge --hostname k3s.bridge --name k3s --publish 6443:6443 --privileged registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1 server --cluster-secret some-secret `
docker: Error response from daemon: Conflict. The container name "/k3s" is already in use by container "82665da51abf6c511c6b457aa2d15637d7f05741ce21bd8dea266f6e04e0cd14". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
checking for kubectl... yes
I, [2020-07-07T15:49:27.626641 #22]  INFO -- : Setting application settings: {:allow_local_requests_from_web_hooks_and_services=>true}
Executing `docker pull registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1`
Using default tag: latest
latest: Pulling from gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1
Digest: sha256:f11984a81ce28740bd016e2c7b45dbdb592d24a22763a5fb9056eb5c748588ab
Status: Image is up to date for registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1:latest
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `docker network inspect test`
[]
Error: No such network: test
Executing `docker run -d --rm --network bridge --hostname k3s.bridge --name k3s --publish 6443:6443 --privileged registry.gitlab.com/gitlab-org/cluster-integration/test-utils/k3s-gitlab-ci/releases/v0.6.1 server --cluster-secret some-secret `
docker: Error response from daemon: Conflict. The container name "/k3s" is already in use by container "82665da51abf6c511c6b457aa2d15637d7f05741ce21bd8dea266f6e04e0cd14". You have to remove (or rename) that container to be able to reuse that name.

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

This would cause a temporary outage in testing of adding Kubernetes clusters to the GitLab application. We have lower-level tests, but not in an end-to-end manner such as this.

Edited by Dan Davison

Merge request reports