https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/24857/pull-ci-openshift-origin-master-e2e-cmd/5010 SUCCESS after 0.000s: test/cmd/secrets.sh:100: executing 'oc secrets link deployer basicauth' expecting success Running test/cmd/secrets.sh:102: executing 'oc secrets link deployer basicauth sshauth' expecting success... SUCCESS after 0.000s: test/cmd/secrets.sh:102: executing 'oc secrets link deployer basicauth sshauth' expecting success Running test/cmd/secrets.sh:104: executing 'oc secrets link deployer basicauth sshauth --for=pull' expecting success... SUCCESS after 0.000s: test/cmd/secrets.sh:104: executing 'oc secrets link deployer basicauth sshauth --for=pull' expecting success Running test/cmd/secrets.sh:106: executing 'oc secrets link deployer basicauth sshauth --for=pull,mount' expecting success... FAILURE after 30.000s: test/cmd/secrets.sh:106: executing 'oc secrets link deployer basicauth sshauth --for=pull,mount' expecting success: the command returned the wrong error code There was no output from the command. Standard error from the command: Unable to connect to the server: dial tcp 10.0.0.2:6443: i/o timeout [ERROR] hack/lib/cmd.sh:241: `return "${return_code}"` exited with status 1. Apr 9 18:55:52.356: INFO: skipping dumping cluster info - cluster too large Apr 9 18:55:52.370: INFO: Deleted {user.openshift.io/v1, Resource=users e2e-test-test-cmd-d7d9g-user}, err: <nil> Apr 9 18:55:52.384: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthclients e2e-client-e2e-test-test-cmd-d7d9g}, err: <nil> Apr 9 18:55:52.397: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthaccesstokens 66W6Z8JIRNq_VkZywWI27gAAAAAAAAAA}, err: <nil> Apr 9 18:55:52.404: INFO: Deleted {/v1, Resource=namespaces cmd-secrets}, err: <nil> [AfterEach] [sig-cli][Feature:LegacyCommandTests][Disruptive][Serial] test-cmd: /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/util/client.go:111 Apr 9 18:55:52.404: INFO: Waiting up to 7m0s for all (but 100) nodes to be ready STEP: Destroying namespace "e2e-test-cmd-9099" for this suite. STEP: Destroying namespace "e2e-test-test-cmd-d7d9g" for this suite. Apr 9 18:55:52.438: INFO: Running AfterSuite actions on all nodes Apr 9 18:55:52.438: INFO: Running AfterSuite actions on node 1 fail [github.com/openshift/origin/test/extended/cmd/cmd.go:118]: Expected <[]error | len:1, cap:1>: [ { s: "error waiting for the pod 'test-cmd' to complete: the pod errored trying to run the command", }, ] to have length 0
Our test-cmd are not much resilient to any problems thus fail immediately. This one filed due to: Unable to connect to the server: dial tcp 10.0.0.2:6443: i/o timeout which looks like a temporary network glitch. We are working towards transitioning our test-cmd into proper e2e so I'll set this priority for low for now. Feel free to bump if this becomes more pressing issue.
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale". If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity 7 days after it was marked as LifecycleStale, so we are closing this bug as WONTFIX. If you consider this bug still valuable, please reopen it or create new bug.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days