Bug 1827306
| Summary: | Edit ClusterServiceVersion should not be a first class Action | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Robb Hamilton <rhamilto> |
| Component: | Management Console | Assignee: | Robb Hamilton <rhamilto> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4 | CC: | aos-bugs, bpeterse, dtaylor, hasha, jokerman, yapei |
| Target Milestone: | --- | Keywords: | UpcomingSprint |
| Target Release: | 4.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Edit ClusterServiceVersion is present in a ClusterServiceVersion's Actions menu so that it is parallel with other resources.
Consequence: The presence of the Edit ClusterServiceVersion menu item suggests users should edit the ClusterServiceVersion, when in reality, they more than likely should not.
Fix: Remove the Edit ClusterServiceVersion menu item from the Actions menu.
Result: The Edit ClusterServiceVersion menu item is no longer present in the Actions menu.
|
Story Points: | --- |
| Clone Of: | 1826488 | Environment: | |
| Last Closed: | 2020-06-29 15:33:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1826488 | ||
| Bug Blocks: | |||
|
Comment 1
Robb Hamilton
2020-05-08 17:15:42 UTC
PR opened, awaiting cherry pick approval. PR opened, awaiting cherry pick approval Install an operator from console, then check installed operators, click kebab action, there is no "Edit ClusterServiceVersion" menu now. 4.4.0-0.nightly-2020-06-21-210301 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-2020:2713 |