Bug 2263148
| Summary: | ODF installation fails if "Performance Mode" is picked up during install ( "Performance Mode" requests on CPU exceed available cpu on OCP node ) | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Elvir Kuric <ekuric> |
| Component: | management-console | Assignee: | Alfonso MartÃnez <almartin> |
| Status: | CLOSED ERRATA | QA Contact: | Joy John Pinto <jopinto> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.15 | CC: | almartin, mparida, muagarwa, nberry, nigoyal, odf-bz-bot, skatiyar |
| Target Milestone: | --- | ||
| Target Release: | ODF 4.16.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 4.16.0-94 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-07-17 13:13:47 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
Elvir Kuric
2024-02-07 08:18:24 UTC
We had a lot of discussion about this situation during the design phase of the feature itself. We did think of adding some validation on the UI before choosing a profile. The validation was intended to calculate & see if a selected profile can be applied successfully on a cluster by its available resources. But after a long discussion & digging, we found it's impossible to predict whether a pod can schedule before actually doing it. K8s scheduling is a hard computational problem that we can't solve. We decided we would do 2 things. 1. Basic validation on UI by just checking the basic total resources available on the cluster and if that meets a certain basic number we have decided. 2. Clear messaging in the doc mentioning that if you don't have sufficient resources choosing a higher resource profile will result in failure, so please choose accordingly. This warning if implemented would be on the console/UI. Moving there and assigning to Alfonso as he has the context. Verified with OCP 4.16.0-0.nightly-2024-05-23-173505 and ODF 4.16.0-113.stable provided by Red Hat Steps performed upon verification: 1. Installed ODF on ibm cloud machine with instance type bx2-16x64, Thus having total resources of 48 CPUs and 188.7 GiB on 3 zone 2. Increased number of OSD by add capacity option from existing 3 to 12 3. Upon adding 12 osds, the total requested resources by performance profile was greater than available resources hence proper error message was displayed and mode selection option was greyed out, Refer 12osd_resource_req_not met.png 4. Also the CPUs and Memory required values for each performance profile kept on incraesing as #of osds were increased post 6 osds, refer 6_osd.png and 9_osd.png 5. Tried applying 'balanced Mode" performance profile, which was successful. 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 (Important: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & 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/RHSA-2024:4591 |