Bug 1886541

Summary: UI should fallback to minimal deployment only after total CPU < 30 || totalMemory < 72 GiB for initial deployment
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Console Storage PluginAssignee: Bipul Adhikari <badhikar>
Status: CLOSED ERRATA QA Contact: Pratik Surve <prsurve>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs, badhikar, nberry, nthomas, ocs-bugs, scuppett
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-16 14:37:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1885676    
Bug Blocks:    

Description OpenShift BugZilla Robot 2020-10-08 17:16:19 UTC 
+++ This bug was initially created as a clone of Bug #1885676 +++

Created attachment 1719453 [details]
Current Mnimal deployment message

Description of problem:
-----------------------------
OCP 4.6 + OCS 4.6

Minimal deployment should not be triggered unless aggregated CPU is less than 32 or aggregated memory is less than 72 GiB.

Currently it's in case aggregated CPU < 48 or memory less than 102 GiB (below the recommended config), the OCS deployment automatically falls back to minimal deployment phase.

The warning message which is: 
```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.```
needs to be updated as well with respect to the new limits. 

Version-Release number of selected component (if applicable):
----------------------------------------
OCP 4.6 - e.g. 4.6.0-0.nightly-2020-09-28-061045

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

Steps to Reproduce:
1. Select nodes for OCS install (3 nodes preferably) ; totalCPU < 42 || totalMemory < 96; i.e 14 CPU per node(for similar node cluster)

2. UI throws warning and falls back to minimal deployment, but that is not needed.
3.


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

Confirmation from Orit

```
The 42 is for a cluster of 9 osds, for a 3 osds cluster (which is the first installation) 30 cpus is enough. 
Minimal deployment should be triggered on if total CPU < 30 || totalMemory < 72 as it is for a 3 osds only deployment

We can enforce the higher limits when the users increase the cluster capacity

```

--- Additional comment from nberry on 2020-10-06 17:09:16 UTC ---

Chat thread with detailed conversation - https://chat.google.com/room/AAAA76Pbvwc/oMLZ6LMDBMU
Comment 2 Bipul Adhikari 2020-10-14 12:46:21 UTC 
This BZ also fixes a regression introduced by https://bugzilla.redhat.com/show_bug.cgi?id=1860985 where the minimal node deployment check would be activated only when greater than 3 nodes is selected, instead of greater than or equal to 3.
Comment 3 Neha Berry 2020-10-21 09:57:32 UTC 
Requesting for bumping the severity as currently, the trigger for minimal deployment is not what is expected.
Comment 4 Bipul Adhikari 2020-10-21 13:23:18 UTC 
*** Bug 1886823 has been marked as a duplicate of this bug. ***
Comment 13 errata-xmlrpc 2020-11-16 14:37:42 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 (OpenShift Container Platform 4.6.4 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-2020:4987