Bug 1948427
Summary: | No action is triggered after click 'Continue' button on 'Show community Operator' windows | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Xiyun Zhao <xiyuzhao> |
Component: | Management Console | Assignee: | Jon Jackson <jonjacks> |
Status: | CLOSED ERRATA | QA Contact: | Xiyun Zhao <xiyuzhao> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.8 | CC: | aos-bugs, jiazha, jokerman, jowilson, spadgett, yapei |
Target Milestone: | --- | Flags: | xiyuzhao:
needinfo-
|
Target Release: | 4.8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Community Operator modal "Continue" handler was opening the details sidebar modal, then calling the 'close' callback.
Consequence: Both the community operator modal and the details side bar modal were being unmounted from the DOM right after the user clicked continue. This caused React state in the main app to be out of sync. This new behavior was likely caused by React 17 updates that changed the way parallel instances of React work.
Fix: Call the close callback first, then open the details sidebar so that it doesn't get immediately unmounted.
Result: Community operator modal works as expected and details side bar is displayed after clicking continue.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-07-27 22:58:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Xiyun Zhao
2021-04-12 07:16:45 UTC
Yes, no operator modal can be opened via clicking from web console when `Show community Operator` modal is opened and closed It's possible bug 1948566 is a duplicate of this issue although we need to investigate. *** Bug 1948566 has been marked as a duplicate of this bug. *** (In reply to Samuel Padgett from comment #3) > It's possible bug 1948566 is a duplicate of this issue although we need to > investigate. Confirmed duplicate and closed. This bug has been verified and fixed on payload 4.8.0-0.nightly-2021-04-18-101412 Verify Step: 1. Log into the web UI as admin, navigate to Operator -> OperatorHub page 2. Choose and use '3scale API Management' as a example, click on the name of the operator 3. On the pops up page which called "Show community Operator", click on the 'continue' button 4. Verify if user is able to install the Operator successfully Result: 4. User is able to open the 'operator detail' panel after click the 'Continue' button on 'show community Operator' pops up page. And operator can be installed successfully after installation action is triggered. *** Bug 1950193 has been marked as a duplicate of this bug. *** 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.8.2 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-2021:2438 |