Bug 2214023 - [UI] Node details from ODF Topology incorrect
Summary: [UI] Node details from ODF Topology incorrect
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ODF 4.14.0
Assignee: Debjyoti Pandit
QA Contact: Daniel Osypenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-11 07:42 UTC by Daniel Osypenko
Modified: 2023-08-16 14:49 UTC (History)
5 users (show)

Fixed In Version: 4.14.0-110
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-console pull 946 0 None open Bug 2214023: added Rack info for the topology details screen 2023-08-08 07:37:31 UTC
Github red-hat-storage odf-console pull 968 0 None open Bug 2214023: [release-4.14-compatibility] fix: added Rack info for the topology details screen 2023-08-14 08:00:27 UTC
Github red-hat-storage odf-console pull 969 0 None open Bug 2214023: [release-4.14] fix: added Rack info for the topology details screen 2023-08-14 08:01:09 UTC

Description Daniel Osypenko 2023-06-11 07:42:18 UTC
Created attachment 1970278 [details]
node-details-topology-tab

Description of problem (please be detailed as possible and provide log
snippests):

Node details tab shows two problems:
1. When deploying on-premises cluster the node details should show Rack with rack number, but instead it shows Zone, as for cloud based deployments
Important to notice that the Compute / Nodes / Any node - Overview tab has the same problem (adding the screenshot)

2. Provider Id is the spec of the node and full id has format <provider>://UUID
Instead UI shows only provider name (prefix).
* If there is decision to not show the UUID the header is incorrect and should be Provider or Provider name
* If there was no decision to shorten Provider Id we need to reveal the full Provider Id 
 

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-06-03-031200
Kubernetes Version: v1.26.5+7a891f0

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

Cluster version
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.13.0-0.nightly-2023-06-03-031200   True        False         3d      Cluster version is 4.13.0-0.nightly-2023-06-03-031200

Rook version:
rook: v4.13.0-0.e5648f0a2577b9bfd2aa256d4853dc3e8d94862a
go: go1.19.6

Ceph version:
ceph version 17.2.6-50.el9cp (c202ddb5589554af0ce43432ff07cd7ce8f35243) 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?
no

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:
-

Steps to Reproduce:
1. Deploy on-premise cluster, login to management console
2. Navigate to Storage / Data Foundation / Topology / select any node from the cluster and click on Details tab on the right side-bar - check details
3. Navigate to Storage / Data Foundation / Overview 


Actual results:
1. Zone shown without any label under the header, similar problem on Compute / Nodes / Any node - Overview
2. Provider ID is not complete

Expected results:
1. Rack header shown with it's name under the Rack header, same should be on the management console: Compute / Nodes / Any node - Overview 
2. Provider ID header is changed to Provider or value of Provider ID is shown complete

Additional info:


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