Bug 1684678
Summary: | operator hub page doesn't show installed community operator without clicking "show community" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Erik M Jacobs <ejacobs> |
Component: | Management Console | Assignee: | Jeff Phillips <jephilli> |
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas, xiaocwan |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
UX design was to show community operators only when the user confirmed showing them.
Consequence:
Users had to clicl 'Show Community Operators' before the community operators would display.
Fix:
Show community operators by default and add an indicator to the community operators' tiles.
Result:
Community operators are shown by default and have a community 'badge'
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:44:51 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
Erik M Jacobs
2019-03-01 20:46:27 UTC
This should be fixed by https://github.com/openshift/console/pull/1178 Now it does not seen on 4.0.0-0.nightly-2019-03-06-074438. The community operators are displayed well after browsed to some other pages such as Pod page then go back. It also works when the whole page close and reopen. If this is the same thing as the step2 "leave the operator hub page", I think it could be moved to Verified. 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, 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/RHBA-2019:0758 |