Bug 1829961 - test: time out waiting on Running AfterSuite actions on node 1
Summary: test: time out waiting on Running AfterSuite actions on node 1
Keywords:
Status: CLOSED DUPLICATE of bug 1832332
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-30 16:26 UTC by Brett Tofel
Modified: 2020-05-07 13:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
test: job
Last Closed: 2020-05-07 13:23:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Brett Tofel 2020-04-30 16:26:57 UTC 
Apr 30 14:53:10.198: INFO:  Apr 30 14:53:10.198: INFO: Running AfterSuite actions on all nodes
Apr 30 14:53:10.198: INFO: Running AfterSuite actions on node 1
fail [k8s.io/kubernetes/test/e2e/network/service.go:2039]: Unexpected error:
    <*errors.errorString | 0xc00028a1a0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred 
Apr 30 14:53:10.198: INFO: Running AfterSuite actions on node 1
fail [k8s.io/kubernetes/test/e2e/network/service.go:2039]: Unexpected error:
    <*errors.errorString | 0xc00028a1a0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred 

From: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/promote-release-openshift-machine-os-content-e2e-aws-4.3/11262

for instance, but seems to regularly be happening in job.initialize every job.
Comment 1 Alexander Constantinescu 2020-05-07 13:23:38 UTC 

*** This bug has been marked as a duplicate of bug 1832332 ***
Note You need to log in before you can comment on or make changes to this bug.