Bug 1995612 - Block pool details page breadcrumb link is not pointing storage system details page
Summary: Block pool details page breadcrumb link is not pointing storage system detail...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.9.0
Assignee: gowtham
QA Contact: Mugdha Soni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-19 13:39 UTC by gowtham
Modified: 2021-10-18 17:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:47:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 9772 0 None None None 2021-08-19 14:00:26 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:47:42 UTC

Comment 5 Mugdha Soni 2021-09-22 07:57:48 UTC 
Validated the fix with cluster ODF version 4.9.0-139.ci and following steps were performed :-

1.In navigation menu clicked on  Storage -> ODF Data Foundation -> Storage Systems -> click storage-system-name -> BlockPools 

When clicked StorageSystem or block pool , link are redirect to correct page i.e storage system details page. The screenshot for the same is attached in comment#4 .

Since the expected results are met ,moving the bug to verified state .


Thankyou
Mugdha soni
Comment 7 errata-xmlrpc 2021-10-18 17:47:27 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.9.0 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:3759
Note You need to log in before you can comment on or make changes to this bug.