Bug 1886823 - OCS : Refine the Warning message which is displayed when minimal deployment is triggered in UI
Summary: OCS : Refine the Warning message which is displayed when minimal deployment i...
Keywords:
Status: CLOSED DUPLICATE of bug 1885676
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.7.0
Assignee: Bipul Adhikari
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-09 13:21 UTC by Neha Berry
Modified: 2020-10-28 10:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-21 13:23:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screencast when the message gets triggered (156.56 KB, video/webm)
2020-10-09 13:21 UTC, Neha Berry
no flags Details
OCP4.6 minimal cluster warning (56.42 KB, image/png)
2020-10-14 20:20 UTC, Annette Clewett
no flags Details
OCP4.6 minimal cluster warning (83.05 KB, image/png)
2020-10-14 22:52 UTC, Annette Clewett
no flags Details

Description Neha Berry 2020-10-09 13:21:12 UTC
Created attachment 1720266 [details]
Screencast when the message gets triggered

Description of problem:
-----------------------------

Related to Bug 1885676

Currently, for selected nodes, if the aggregate CPU <30 and aggregate memory <72 GiB, the UI falls back to minimal deployment, wherein limits are reduced for the following pods

a) RGW 
b) OSD 
c) MDS 

Even though the Warning message appears only if CPU<30 and memory<72, but the statement on the screen says

```The selected nodes do not match the OCS storage cluster recommended requirements of an aggregated 42 CPUs and 102 GiB of RAM. If the selection cannot be modified, a minimal cluster will be deployed.```


IMO, this statement is confusing, as looking at the text, it implies that minimal deployment would be triggered in all the cases when CPU<42 and memory<102. Hence, the actual trigger point and the message are a little contradictory.

It would be good to refine the message to clearly state as to when the deployment :

a) really falls back to minimal deployment
b) minimal deployment would mean 1 OSD per node, no support for more OSD



Version-Release number of selected component (if applicable):
-----------------------------------------------
OCS 4.6  and OCP 4.6 and above

How reproducible:
-----------------
Always

Steps to Reproduce:
1. Create an OCP cluster with multiple worker nodes, say 4 CPU and 16 GB memory. 

2. In create storage cluster page, select minimum 3 worker nodes (more can be selected), making sure that total CPU is still less than 30

.
3. Check the warning message


Actual results:
---------------------
The warning message conveys minimal deployment will be used if below recommended config, but trigger is different

Expected results:
---------------------
Refine the statement to clearly match the actual trigger when this message surfaces.

Additional info:
---------------------

from KNIP

>> Detect that it’s a small cluster
CPU is < 30 or if aggregate memory < 72. 


>> highlight in the UI that this is a minimal cluster deployment that can  support only 1 drives 

_____________________________________________]

In the screenscast
------------------------

9 nodes(matser made schedulable too), 4 CPU each = 36 CPU

if all 9 nodes selected = no warning
If 8 nodes selected = 8 * 4 = 32 CPu, no warning
If 7 nodes selected, 7*4 = 28 CPU <required aggregate of 30 CPU - the warning message is triggered

But the warning message still reads

""""""
The selected nodes do not match the OCS storage cluster recommended requirements of an aggregated 42 CPUs and 102 GiB of RAM. If the selection cannot be modified, a minimal cluster will be deployed
"""""

Comment 1 Stephen Cuppett 2020-10-09 16:55:17 UTC
Setting target release to the active development branch (4.7.0). For any fixes, where required and requested, cloned BZs will be created for those release maintenance streams where appropriate once they are identified.

Comment 3 Annette Clewett 2020-10-14 20:20:58 UTC
Created attachment 1721584 [details]
OCP4.6 minimal cluster warning

Comment 4 Annette Clewett 2020-10-14 22:52:27 UTC
Created attachment 1721635 [details]
OCP4.6 minimal cluster warning

Comment 5 Bipul Adhikari 2020-10-21 13:23:18 UTC
This should be part of the fixes done in https://bugzilla.redhat.com/show_bug.cgi?id=1886541. As since the limit is lowered hence the message should also change based on this reasoning I have updated its a description and am closing this.

*** This bug has been marked as a duplicate of bug 1886541 ***

Comment 6 Bipul Adhikari 2020-10-28 10:27:33 UTC

*** This bug has been marked as a duplicate of bug 1885676 ***


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