Open ljelinkova opened 5 years ago
@ljelinkova Is this issue still persist? For me, it is the app creation flow working as expected.
I haven't seen this issue for couple of days. However, I'd expect launcher to display some error message if it is not able to get the boosters from server.
[22:08:17.804] SEVERE https://openshift.io/osio-ci-e2e-005/e2e-1016-2307-1415/applauncher/createapp/e2e-1016-2307-1415 - Failed to load https://forge.api.openshift.io/api/booster-catalog/: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://openshift.io' is therefore not allowed access. The response had HTTP status code 500.
@ljelinkova if this is a bug, please label it and assign a severity
Maybe this is more of a UX issue - what should be displayed to user, if no boosters are loaded (e.g. due to backend failure).
cc @openshiftio/uxd-team
Haven't seen this issue lately.
How come?
https://github.com/openshiftio/openshift.io/issues/4670
This could happen anytime and the user should be given some clue as why there are no boosters.
It would be great if UX team could comment @serenamarie125
The server side issues have been resolved. The title of the issue was a bit misleading. Probably we should have a general way of displaying an error note to communicate that boosters couldn't be loaded for some reason.
Issue Overview
The e2e tests failed when creating new application because there were no available boosters listed.
Expected Behaviour
The wizard should list available boosters
Current Behaviour
The wizard is empty
Steps To Reproduce
This happens intermittently
Additional Information
This was looged in from browser log:
You can see more logs here: http://artifacts.ci.centos.org/devtools/e2e/devtools-test-e2e-openshift.io-smoketest-us-east-1b-released/877/03-01-afterEach.log