Bug 1801584 - Inconsistency in kebab and actions menu for storage cluster instance
Summary: Inconsistency in kebab and actions menu for storage cluster instance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Neha Gupta
QA Contact: Oded
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-11 09:39 UTC by Yuval
Modified: 2023-09-14 05:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:14:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Storage Cluster UI (391.42 KB, image/png)
2020-06-21 11:07 UTC, Oded
no flags Details
Actions (153.06 KB, image/png)
2020-06-23 09:08 UTC, Neha Gupta
no flags Details
kebab menu (1.50 MB, video/webm)
2020-06-29 18:22 UTC, Oded
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4352 0 None closed Bug 1801584: Fixed Inconsistency in kebab and actions menu for storage cluster 2020-07-03 02:52:07 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:15:25 UTC

Description Yuval 2020-02-11 09:39:41 UTC
All the actions that appear in the kebab menu for the storage cluster instance, should appear in the actions menu when drilling down to the storage cluster.

Comment 3 Oded 2020-06-21 11:05:37 UTC
Bug Reconstructed.

SetUp:
Provider:AWS
OCP Version: 4.5.0-0.nightly-2020-06-20-194346
OCS Version: ocs-operator.v4.5.0-452.ci

Test Process:
1.Go to "Operators"->"Insatalled Operators" -> "Storage Cluster"
2.Not all the actions that appear in the kebab menu appear in the actions menu.
*Attached screenshot

Comment 4 Oded 2020-06-21 11:07:01 UTC
Created attachment 1698224 [details]
Storage Cluster UI

Comment 6 Neha Gupta 2020-06-23 09:08:02 UTC
@oviner The actions should be visible inside the storage cluster details page and not on Operator Details > Storage cluster tab. It contains the operator level actions. 
Actions are properly visible on the storage cluster details page and is consistent with the kebab actions. Attaching the screenshot.

Steps to see -

1) Install OCS operator and storage cluster.
2) Go to OCS operator's details page
3) Go to storage cluster tab
4) Click on Storage cluster's name which will take you to the details page
5) Click on Actions dropdown.

Comment 7 Neha Gupta 2020-06-23 09:08:26 UTC
Created attachment 1698413 [details]
Actions

Comment 8 Oded 2020-06-29 18:20:51 UTC
Bug Not Reconstructed.

SetUp:
Provider:AWS
OCP Version: 4.5.0-0.nightly-2020-06-26-215024
OCS Version: ocs-operator.v4.4.1-465.ci

Test Process:
1.Go to "Operators"->"Insatalled Operators" -> "OCS"->"Storage Cluster" tab -> "ocs-storagecluster"
2.Actions dropdown:
*Add Capacity
*Download Cluster Metadata
*Edit OCS Cluster Service
*Delete OCS Cluster Service
3.Go to "Operators"->"Insatalled Operators" -> "OCS"->"Storage Cluster" tab
4.kebab menu:
*Add Capacity
*Download Cluster Metadata
*Edit OCS Cluster Service
*Delete OCS Cluster Service

Conclusion: 
All the actions that appear in the "kebab menu" appear in the "Actions dropdown"

*Can verify this bug on OCP 4.5 and OCS 4.4? 
*There are issues with "kebab menu" (attached screen record)

Comment 9 Oded 2020-06-29 18:22:58 UTC
Created attachment 1699199 [details]
kebab menu

Comment 12 errata-xmlrpc 2020-07-13 17:14:44 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, 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:2409

Comment 13 Red Hat Bugzilla 2023-09-14 05:52:18 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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