Build fail: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-console-aws-4.4/1214 Possibly because the object is being deleted considered as `running`
This is a top flake for this job, it should get high priority from the team to investigate/resolve.
https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-console-aws-4.4/1214/build-log.txt ``` 68) ConsoleExternalLogLink CRD ✔ displays YAML editor for creating a new ConsoleExternalLogLink instance ✔ creates a new ConsoleExternalLogLink instance ✔ displays detail view for ConsoleExternalLogLink instance ✔ creates a new test pod to display the ConsoleExternalLogLink instance ✔ displays the ConsoleExternalLogLink instance on the test pod ✔ displays YAML editor for adding namespaceFilter to the ConsoleExternalLogLink instance ✔ does not display the ConsoleExternalLogLink instance on the test pod ✔ deletes the test pod ✔ deletes the ConsoleExternalLogLink instance Error from server (AlreadyExists): error when creating "STDIN": object is being deleted: pods "test-kkyve-pod" already exists 69) Events 70) Events [20:48:08] W/element - more than one element found for locator By(css selector, [data-test-id=test-kkyve-pod]) - the first result will be used ✖ event view displays created pod (1 failure) >> Done! Failed Specs: 1) Events Events : event view displays created pod Error: Command failed: echo '{"apiVersion":"v1","kind":"Pod","metadata":{"name":"test-kkyve-pod","namespace":"test-kkyve"},"spec":{"containers":[{"name":"hello-openshift","image":"openshift/hello-openshift"}]}}' | kubectl create -n test-kkyve -f - Error from server (AlreadyExists): error when creating "STDIN": object is being deleted: pods "test-kkyve-pod" already exists at checkExecSyncError child_process.js:629:11 at Object.execSync child_process.js:666:13 at UserContext.<anonymous> /go/src/github.com/openshift/console/frontend/integration-tests/tests/event.scenario.ts:24:5 at /go/src/github.com/openshift/console/frontend/node_modules/jasminewd2/index.js:112:25 at new ManagedPromise /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:1077:7 at ControlFlow.promise /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:2505:12 at schedulerExecute /go/src/github.com/openshift/console/frontend/node_modules/jasminewd2/index.js:95:18 at TaskQueue.execute_ /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:3084:14 at TaskQueue.executeNext_ /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:3067:27 at asyncRun /go/src/github.com/openshift/console/frontend/node_modules/selenium-webdriver/lib/promise.js:2974:25 From: Task: Run beforeAll in control flow at UserContext.<anonymous> /go/src/github.com/openshift/console/frontend/node_modules/jasminewd2/index.js:94:19 From asynchronous test: Error at Suite.<anonymous> /go/src/github.com/openshift/console/frontend/integration-tests/tests/event.scenario.ts:23:3 at Env.<anonymous> /go/src/github.com/openshift/console/frontend/node_modules/jasmine-fail-fast/dist/jasmine-fail-fast.js:57:26 at Env.wrapper [as describe] /go/src/github.com/openshift/console/frontend/node_modules/jasmine-fail-fast/node_modules/lodash/index.js:3592:19 at Object.<anonymous> /go/src/github.com/openshift/console/frontend/integration-tests/tests/event.scenario.ts:5:1 at Module._compile internal/modules/cjs/loader.js:778:30 at Module.m._compile /go/src/github.com/openshift/console/frontend/node_modules/ts-node/src/index.ts:400:23 ```
This flake not reproduced in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-console-aws-4.5/262 4.5.0-0.nightly-2020-03-18-060748
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409