Bug 2105909 - OLM create-namespace.spec.ts e2e test fails always
Summary: OLM create-namespace.spec.ts e2e test fails always
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.12.0
Assignee: Christoph Jerolimov
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 2105910
TreeView+ depends on / blocked
 
Reported: 2022-07-11 07:31 UTC by Christoph Jerolimov
Modified: 2023-01-17 19:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-17 19:51:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11809 0 None open Bug 2105909: Fix create-namespace e2e test with updated 3scale operator 2022-07-11 07:34:11 UTC
Red Hat Product Errata RHSA-2022:7399 0 None None None 2023-01-17 19:52:28 UTC

Description Christoph Jerolimov 2022-07-11 07:31:55 UTC
Description of problem:
The openshift/console tests e2e-gcp-console CI jobs fails currently always with an error in create-namespace.spec.ts.

For example:
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_console/11798/pull-ci-openshift-console-release-4.10-e2e-gcp-console/1545505724312850432
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_console/11798/pull-ci-openshift-console-release-4.10-e2e-gcp-console/1545549888563974144
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_console/11798/pull-ci-openshift-console-release-4.10-e2e-gcp-console/1545684305693380608

See also:
https://search.ci.openshift.org/?search=before+all%60+hook+we+are+skipping+the+remaining+tests+in+the+current+suite%3A+%60Using+OLM+descriptor+compon&maxAge=336h&context=1&type=bug%2Bissue%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

Version-Release number of selected component (if applicable):
At least 4.8+

How reproducible:
Always

Steps to Reproduce:
1. Run a CI job

Actual results:
  1) Create namespace from install operators
       creates namespace from operator install page:
     CypressError: Timed out retrying after 30050ms: `cy.click()` failed because this element is `disabled`:

`<button aria-haspopup="true" aria-expanded="false" class="pf-c-dropdown__toggle" data-test-id="dropdown-button" type="button" id="dropdown-selectbox" data-test="dropdown-selectbox" disabled="">...</button>`


Expected results:
Test should pass

Additional info:
3scale 2.11 supports only installation mode 'A specific namespace', so it was automatically selected. But starting with 2.12 it also supports 'All namespaces'.

So it is now required to select this radio option to specify the namespace.

Comment 1 Robb Hamilton 2022-08-18 12:58:10 UTC
Need verification, please.

Comment 2 Robb Hamilton 2022-08-22 15:01:37 UTC
Ya Dan, can you help see that this fix gets verified?  This fix needs to be back ported to 4.9 in order to unblock other fixes from merging to release-4.9.  the back ports have all been created, but they cannot start merging until this one is verified.

Comment 3 Yadan Pei 2022-08-23 03:10:55 UTC
PR was merged on July 13, searched `creates namespace from operator install page` test results latest 7 days
https://search.ci.openshift.org/?search=creates+namespace+from+operator+install+page&maxAge=168h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job 

there are only some errors in OCP 4.8 and OCP 4.9, `creates namespace from operator install page` tests has been always passing in 4.12

the issue has been fixed in OCP 4.12

Comment 6 errata-xmlrpc 2023-01-17 19:51:57 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.12.0 bug fix and security 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-2022:7399


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