Bug 1905621 - Protractor login test fails against a 4.7 (nightly) Power cluster
Summary: Protractor login test fails against a 4.7 (nightly) Power cluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.7
Hardware: ppc64le
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.7.0
Assignee: David Taylor
QA Contact: Hiro Miyamoto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-08 17:04 UTC by Hiro Miyamoto
Modified: 2021-02-24 15:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:41:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Remove Power Cluster initial i18n 'en-US' 404 not found errors (238.60 KB, image/png)
2020-12-09 21:28 UTC, David Taylor
no flags Details
Power Cluster Knative Unauthorized errors (127.02 KB, image/png)
2020-12-09 21:29 UTC, David Taylor
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7502 0 None closed Bug 1905621: Protractor login test fails against a 4.7 (nightly) Power cluster 2021-02-19 13:50:07 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:41:37 UTC

Description Hiro Miyamoto 2020-12-08 17:04:06 UTC
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!

Comment 1 Dan Li 2020-12-08 19:01:55 UTC
Setting the blocker flag to "Blocker+" after spoken with Hiro

Comment 5 David Taylor 2020-12-09 21:28:34 UTC
Created attachment 1738055 [details]
Remove Power Cluster initial i18n 'en-US' 404 not found errors

Comment 6 David Taylor 2020-12-09 21:29:44 UTC
Created attachment 1738056 [details]
Power Cluster Knative Unauthorized errors

Comment 10 Yadan Pei 2020-12-21 08:22:03 UTC
@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

Comment 11 Hiro Miyamoto 2021-01-12 23:42:25 UTC
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!

Comment 13 errata-xmlrpc 2021-02-24 15:41:14 UTC
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


Note You need to log in before you can comment on or make changes to this bug.