Description of problem: When running Protractor tests against a 4.7 (nightly) cluster running on Power/ppc64le, the very first login step fails, showing a blank screen with 3 dots in the center as screencapture. The cluster does allow login, if you point your browser and manually login. Version-Release number of selected component (if applicable): 4.7.0-0.nightly-ppc64le-2020-11-18-124940 How reproducible: Always Steps to Reproduce: 1. set up Protractor runs, per https://github.com/openshift/console/tree/master#integration-tests 2. set up extra env vars to point to a remote cluster, instead of local bridge, pointing to a cluster on POWER 3. run `test-protractor.sh` Actual results: Fails at the very first test that would log into the cluster. Expected results: Passes the login step and continues for the rest of the test suite. Additional info: The cluster in question is still active at https://console-openshift-console.apps.satwsin1-44.149.81.133.59.nip.io/dashboards Contact me for kubeadmin login for debug/investigation. Thanks!
Setting the blocker flag to "Blocker+" after spoken with Hiro
Created attachment 1738055 [details] Remove Power Cluster initial i18n 'en-US' 404 not found errors
Created attachment 1738056 [details] Power Cluster Knative Unauthorized errors
@Hiro Miyamoto, Could you help verify this bug? It looks like a Power cluster is needed but I didn't get response requesting kubeadmin password for it
Verified with Protractor tests code on `release-4.7` branch as of 1/7 against a Power cluster running 4.7.0-fc.1, and the login part works like below and proceeds to the rest of the tests in both Chrome and Firefox! >> Executing 8 defined specs... Test Suites & Specs: 1) Auth test 2) Login test ✔ logs in as kubeadmin user 3) Create a test namespace ✔ creates test namespace if necessary 4) Interacting with the environment variable editor 5) When a variable is added ✔ shows the correct variables 6) When a variable is deleted ✔ does not show any variables 7) When a variable is added from a config map ✔ shows the correct variables 8) When a variable is deleted from a config map ✔ shows the correct variables 9) When a variable is added from a secret ✔ shows the correct variables 10) When a variable is deleted from a secret ✔ shows the correct variables >> Done!
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633