sig-network e2e test failure: timed out waiting for the condition

Bug #1828256 reported by Ashley Lai
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Kubernetes E2E Test Charm
Triaged
Undecided
Unassigned

Bug Description

kubernetes-e2e version: 1.14.1

While running e2e test we got the failure below.

/workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:692 Unexpected error: <*errors.errorString | 0xc000299400>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred /workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:557 [BeforeEach] [sig-network] DNS /workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:149

Revision history for this message
David Coronel (davecore) wrote :

I see a similar error in another run:

^[[91m^[[1m• Failure [307.515 seconds]^[[0m
[sig-network] DNS
^[[90m/workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/framework.go:22^[[0m
  ^[[91m^[[1mshould provide DNS for services [Conformance] [It]^[[0m
  ^[[90m/workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:692^[[0m

  ^[[91mUnexpected error:
      <*errors.errorString | 0xc0002e6470>: {
          s: "timed out waiting for the condition",
      }
      timed out waiting for the condition
  occurred^[[0m

  /workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:557

Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

sub'd to field high

tags: added: cdo-qa foundations-engine
Revision history for this message
Tim Van Steenburgh (tvansteenburgh) wrote :

We'll take a look. In the meantime, please explain why this is Field High. AFAICT, a conformance test failure does not meet the criteria.

Also, please list the steps taken to achieve this failure (how CDK was deployed, and how e2e was run).

Changed in charm-kubernetes-e2e:
status: New → Triaged
Revision history for this message
Jason Hobbs (jason-hobbs) wrote : Re: [Bug 1828256] Re: sig-network e2e test failure

Here's a link to a test run this failed on.

https://solutions.qa.canonical.com/#/qa/testRun/ccdb6e43-d9da-47cf-a698-09a7ce30ae7f

You can get to the artifacts from a link at the bottom of the page.

Here's the bundles we used:
http://paste.ubuntu.com/p/bzkPSbHSwX/

This was kubernetes deployed on top of openstack.

It doesn't happen everytime - it is a race condition.

We use E2E to validate our kubernetes deployments, and this is one of the
E2E tests.

One of the Field Critical SLA criteria is "Stable release Solutions QA
Foundation Cloud build blocked". We applied Field High because it doesn't
happen every time, but still causes a significant number of test failures.

On Wed, May 22, 2019 at 6:55 AM Tim Van Steenburgh <email address hidden>
wrote:

> We'll take a look. In the meantime, please explain why this is Field
> High. AFAICT, a conformance test failure does not meet the criteria.
>
> Also, please list the steps taken to achieve this failure (how CDK was
> deployed, and how e2e was run).
>
> ** Changed in: charm-kubernetes-e2e
> Status: New => Triaged
>
> --
> You received this bug notification because you are a member of Canonical
> Field High, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/1828256
>
> Title:
> sig-network e2e test failure
>
> Status in Kubernetes E2E Test Charm:
> Triaged
>
> Bug description:
> kubernetes-e2e version: 1.14.1
>
> While running e2e test we got the failure below.
>
> /workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/
> k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:692
> Unexpected error: <*errors.errorString | 0xc000299400>: { s: "timed
> out waiting for the condition", } timed out waiting for the condition
> occurred
> /workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/
> k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/dns_common.go:557
> [BeforeEach] [sig-network] DNS
> /workspace/anago-v1.14.1-beta.0.44+b7394102d6ef77/src/
> k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:149
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charm-kubernetes-e2e/+bug/1828256/+subscriptions
>

Revision history for this message
Ashley Lai (alai) wrote : Re: sig-network e2e test failure

Failure in kubernetes-e2e: junit_19.xml

Revision history for this message
Ashley Lai (alai) wrote :

Attaching more logs. Hope this helps.

summary: - sig-network e2e test failure
+ sig-network e2e test failure: timed out waiting for the condition
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.