Bug 2008490 - Backing store details page does not contain all the kebab actions.
Summary: Backing store details page does not contain all the kebab actions.
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Sanjal Katiyar
QA Contact: Elena Bondarenko
Depends On:
TreeView+ depends on / blocked
Reported: 2021-09-28 11:30 UTC by Mugdha Soni
Modified: 2022-03-10 16:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:13:54 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10266 0 None open Bug 2008490: Fix edit-bucket-class action 2021-10-19 13:08:26 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:14:14 UTC

Description Mugdha Soni 2021-09-28 11:30:11 UTC
Description of problem:
Backing store detail page did not have kebab action "Edit BucketClass Resources" .The screenshot for the same will be attached.

Version-Release number of selected component :
OCP 4.9
OCS 4.9

How reproducible:

Steps to Reproduce:
1.Install ODF cluster
2.Click on storage->odf->BucketClass->BucketClass details page .
3.Click on kebab Actions drop down at right corner . 

Actual results:
All other actions are present in the actions drop down except "Edit BucketClass Resources".

Expected results:
"Edit BucketClass Resources" action should be present in details page as well.

Comment 5 Elena Bondarenko 2021-10-29 14:13:17 UTC
I re-tested with OCP 4.10.0-0.nightly-2021-10-28-211203, bucket class kebab menu contains option "Edit Bucket Class Resources".

Comment 8 errata-xmlrpc 2022-03-10 16:13:54 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 (Moderate: OpenShift Container Platform 4.10.3 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.