Bug 2079062 - Test for console demo plugin toast notification needs to be increased for ci testing
Summary: Test for console demo plugin toast notification needs to be increased for ci ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Joe Caiani
QA Contact: Xiyun Zhao
Depends On:
TreeView+ depends on / blocked
Reported: 2022-04-26 19:49 UTC by Joe Caiani
Modified: 2022-08-10 11:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:08:39 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11402 0 None open Bug 2079062: increase timeout to render toast notification for demo plugin test 2022-04-26 19:52:52 UTC
Github openshift console pull 11414 0 None open Bug 2079062: Update the wait time for demo plugin to 60s 2022-04-27 20:19:43 UTC
Github openshift console pull 11416 0 None open Bug 2079062: use xl timeout to verify the demo pull spec is accurate 2022-04-28 14:57:21 UTC
Github openshift console pull 11473 0 None open Bug 2079062: Update user from node to 1001 similar to console docker file user id 2022-05-10 21:19:27 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:08:50 UTC

Description Joe Caiani 2022-04-26 19:49:25 UTC
Description of problem:
ci tests are failing on waiting for the toast notification that is rendered when the check-updates poll is updated with new plugin data.

Version-Release number of selected component (if applicable):

How reproducible:
reproducable in ci

Steps to Reproduce:
1. see https://github.com/openshift/release/pull/27920

Actual results:

Expected results:

Additional info:

Comment 5 Joe Caiani 2022-05-10 21:11:02 UTC
toast notification now showing, try and update the user from node to 1001

Comment 8 Xiyun Zhao 2022-05-23 09:44:15 UTC
This bug has been verified

Verification Step:
1. Search "Demo dynamic plugin test" on search.ci.openshift.org with filter "bug+junit"
2. Check if there is any failed log in the search result

2. No fails found on the recent ci log anymore, all cases are passed

Demo dynamic plugin test
  Logging in as kubeadmin
      create project
      Running plugin test on ci using PLUGIN_PULL_SPEC: 
    ✓ test Dynamic Nav items (337834ms)
    ✓ test Test Consumer nav item (574ms)
    ✓ test Test Utilities nav item (333ms)
    ✓ test List Page nav item (2339ms)
      Running plugin test on ci using PLUGIN_PULL_SPEC: 
      delete project
  Logging out
    ✓ test K8s API nav item (2085ms)
  5 passing (11m)
[mochawesome] Report JSON saved to cypress_report_002.json
  │ Tests:        5                                                                                │
  │ Passing:      5                                                                                │
  │ Failing:      0                                                                                │
  │ Pending:      0                                                                                │
  │ Skipped:      0                                                                                │
  │ Screenshots:  0                                                                                │
  │ Video:        true                                                                             │
  │ Duration:     11 minutes, 7 seconds                                                            │
  │ Spec Ran:     app/demo-dynamic-plugin.spec.ts

Comment 10 errata-xmlrpc 2022-08-10 11:08:39 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 (Important: OpenShift Container Platform 4.11.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.


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