Description of problem: sometimes the case is failed https://prow.k8s.io/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-console-aws-4.2/95 Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-09-11-012246 How reproducible: e2e flake Steps to Reproduce: 1. 2. 3. Actual results: Failed Specs: 1) Kubernetes resource CRUD operations PersistentVolumeClaim : displays a YAML editor for creating a new resource instance Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. at ontimeout timers.js:427:11 at tryOnTimeout timers.js:289:5 at listOnTimeout timers.js:252:5 at Timer.processTimers timers.js:212:10 Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. at ontimeout timers.js:427:11 at tryOnTimeout timers.js:289:5 at listOnTimeout timers.js:252:5 at Timer.processTimers timers.js:212:10 Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. at ontimeout timers.js:427:11 at tryOnTimeout timers.js:289:5 at listOnTimeout timers.js:252:5 at Timer.processTimers timers.js:212:10 Expected results: Additional info:
It's fixed. I can't find this error in the tests.
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-2019:2922