Bug 2178588 - No rack names on ODF Topology
Summary: No rack names on ODF Topology
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.13.0
Assignee: Bipul Adhikari
QA Contact: Daniel Osypenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-15 10:34 UTC by Daniel Osypenko
Modified: 2023-08-09 16:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-21 15:24:28 UTC
Embargoed:


Attachments (Terms of Use)
expected rack name presented (from the sketch - to implement) (28.26 KB, image/jpeg)
2023-03-15 10:34 UTC, Daniel Osypenko
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-console pull 691 0 None Merged Topology: Fixes Issues pointed by UX 2023-03-23 05:56:17 UTC
Github red-hat-storage odf-console pull 713 0 None open Bug 2178588: [release-4.13] Topology: Fixes Issues pointed by UX 2023-03-23 05:56:18 UTC
Github red-hat-storage odf-console pull 714 0 None open Bug 2178588: [release-4.13-compatibility] Topology: Fixes Issues pointed by UX 2023-03-23 05:56:19 UTC
Red Hat Product Errata RHBA-2023:3742 0 None None None 2023-06-21 15:24:50 UTC

Description Daniel Osypenko 2023-03-15 10:34:25 UTC
Created attachment 1950944 [details]
expected rack name presented (from the sketch - to implement)

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

The rack names are not displayed when the ODF CEPH Topology opened on cluster level. Similarly the zone should be presented for cloud deployments, which works well.

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-11-033820
Kubernetes Version: v1.26.2+bc894ae

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

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

Rook version:
rook: v4.13.0-0.78a2f4d47d1565993575ab9d2130d543eb1f27a4
go: go1.19.2

Ceph version:
ceph version 17.2.5-69.el9cp (b7b25cbd1fb79976b1ec7eda3fa2e6fcc48246d6) quincy (stable)

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


Is there any workaround available to the best of your knowledge?
oc describe node compute-1 | grep rack shows the rack label

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 regression

Steps to Reproduce:
1. deploy cluster on vSphere via upi_1az_rhcos_vsan_3m_3w.yaml
2. enter web console
3. open Data Foundation/Topology page


Actual results:
topology presented but no rack names are visible

Expected results:
rack names are visible under each worker node

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

Comment 9 Bipul Adhikari 2023-05-18 08:08:04 UTC
No doc text required.

Comment 12 errata-xmlrpc 2023-06-21 15:24:28 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


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