Bug 2179981

Summary: ODF Topology search bar mistakes to find searched node/pod
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Daniel Osypenko <dosypenk>
Component: management-consoleAssignee: Bipul Adhikari <badhikar>
Status: CLOSED ERRATA QA Contact: Daniel Osypenko <dosypenk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.13CC: badhikar, kramdoss, nberry, ocs-bugs, odf-bz-bot
Target Milestone: ---   
Target Release: ODF 4.13.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-21 15:24:39 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 Daniel Osypenko 2023-03-20 13:36:56 UTC
Description of problem (please be detailed as possible and provide log
snippests):

During the execution of the test on search bar found 2 problems:

Major issue here:
1. Using Topology Search bar it finds wrong nodes/pods when any text put into the search input

It's been observed too during the test case:
2. Topology fails to render. Bug may be a duplicate of https://github.com/red-hat-storage/odf-console/pull/683 but is not a focus of current BZ

see attached screen recording https://drive.google.com/file/d/1kDLDFYJFJXU0cNOHxg9DZ_KwAiYFF_Tv/view?usp=share_link

These two problems were seen separately on from another and not dependent, but may be observed on one video (attached to the bug) 


Version of all relevant components (if applicable):
OC version:
Client Version: 4.12.0-202208031327
Kustomize Version: v4.5.4
Server Version: 4.13.0-0.nightly-2023-03-17-161027
Kubernetes Version: v1.26.2+06e8c46

OCS verison:
ocs-operator.v4.13.0-107.stable              OpenShift Container Storage   4.13.0-107.stable              Succeeded

Cluster version
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.13.0-0.nightly-2023-03-17-161027   True        False         3h19m   Error while reconciling 4.13.0-0.nightly-2023-03-17-161027: an unknown error has occurred: MultipleErrors

Rook version:
rook: v4.13.0-0.5e1e599ef7616feeaf4babcde46a96714890e96d
go: go1.19.6

Ceph version:
ceph version 17.2.5-75.el9cp (52c8ab07f1bc5423199eeb6ab5714bc30a930955) quincy (stable)


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

no

Is there any workaround available to the best of your knowledge?

workaround to find nodes/pods on topology visually or to use  
compute/nodes or workloads/pods console pages 


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

1

Can this issue reproducible?

yes

Can this issue reproduce from the UI?

yes

If this is a regression, please provide more details to justify this:
not a regression. found within feature Happy Path validation

Steps to Reproduce:
1. Deploy cluster with latest ODF 4.13
2. Login and navigate to Storage / Data Foundation / Topology page 
3. enter any valuable 


Actual results:
When using Topology search bar:
- any random text will find any random node/pod (number of nodes/pods) 
- any matched text to existed node/pod names will find wrong node/pod

Expected results:
- any text partially matched to existed node/pod will be found
- text not matching any existed node/pod name will not find any node/pod

Additional info:
issue is not dependent on deployment configuration and reproducible 5/5

must-gather logs:
https://drive.google.com/drive/folders/1Kh_fRBBwyJK8WR1yPoik31o60xYppMmv?usp=share_link

Comment 6 Daniel Osypenko 2023-04-16 17:53:55 UTC
Verified: https://url.corp.redhat.com/screen-recording-2179981

OC version:
Client Version: 4.12.0-202208031327
Kustomize Version: v4.5.4
Server Version: 4.13.0-0.nightly-2023-04-15-102029
Kubernetes Version: v1.26.3+19816ee

OCS verison:
ocs-operator.v4.13.0-164.stable              OpenShift Container Storage   4.13.0-164.stable              Succeeded

Cluster version
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.13.0-0.nightly-2023-04-15-102029   True        False         109m    Error while reconciling 4.13.0-0.nightly-2023-04-15-102029: the cluster operator storage is not available

Rook version:
rook: v4.13.0-0.29c073c4f2fcc059b628779cb763c385a0a8f23c
go: go1.19.6

Ceph version:
ceph version 17.2.6-10.el9cp (19b8858bfb3d0d1b84ec6f0d3fd7c6148831f7c8) quincy (stable)

Comment 9 errata-xmlrpc 2023-06-21 15:24:39 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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix 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/RHBA-2023:3742