Bug 1857477
| Summary: | Bad helptext for storagecluster creation | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Kyle Bader <kbader> |
| Component: | Console Storage Plugin | Assignee: | Ankush Behl <anbehl> |
| Status: | CLOSED ERRATA | QA Contact: | Elena Bondarenko <ebondare> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4 | CC: | afrahman, aos-bugs, etamir, kbader, nberry, nmukherj, nthomas, olakra, rperiyas, ygalanti |
| Target Milestone: | --- | ||
| Target Release: | 4.8.0 | ||
| 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: | 2021-07-27 22:32:27 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
Kyle Bader
2020-07-15 23:32:48 UTC
@kbader UI labels the selected nodes with ocs label and hence the pods created during StorageCluster initialization can be scheduled on it, if this is what you are asking. I didn't quite understand the issue. Can you please explain a bit more? The issue is the wording of the help text "3 selected nodes are used for initial deployment." It's a *minimum* of 3 nodes, but > 3 can be selected, and *all* selected nodes will be valid scheduling targets (versus only 3). "The remaining selected nodes will be used by OpenShift as scheduling targets for OCS scaling." All nodes that are selected are potentially valid scheduling targets for components, so they wouldn't be used *only* for scaling. @smordech @ygalanti Please update the text. this text has been updated as part of the work we did around the storage cluster creation wizard. https://marvelapp.com/prototype/12i47i8j/screen/73122992 (In reply to Yuval from comment #4) > this text has been updated as part of the work we did around the storage > cluster creation wizard. > https://marvelapp.com/prototype/12i47i8j/screen/73122992 Moving to ON_QA based on this. "Selected nodes will have labels added to them that make them targets for OCS components" Select at least 3 nodes preferably in 3 different zones. It is recommended to start with at least 14 CPUs and 34 GiB per node. The selected nodes will be labeled with cluster.ocs.openshift.io/openshift-storage="" (unless they are already labeled). Selected nodes will have labels added to them that make them targets for OCS components @kbader @ygalanti is this statement what we're looking for ? Please confirm Setting target release to the active development branch (4.8.0). For any fixes, where required , cloned BZs will be created for those release maintenance streams. @kbader , do you agree with https://bugzilla.redhat.com/show_bug.cgi?id=1857477#c14 ? This text works for me: “The selected nodes will be labeled with cluster.ocs.openshift.io/openshift-storage="" (unless they are already labeled). Selected nodes will have labels added to them that make them targets for OCS components” That said, if we wanted to make it shorter / more concise: “Selected nodes will be labeled in a way that makes them viable hosts for OCS components.” 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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-2021:2438 |