Bug 2228104
| Summary: | [RDR] Greenfield deployment does not pick value set in storagecluster for osdtype | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Pratik Surve <prsurve> |
| Component: | ocs-operator | Assignee: | Santosh Pillai <sapillai> |
| Status: | POST --- | QA Contact: | Elad <ebenahar> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.14 | CC: | kramdoss, muagarwa, odf-bz-bot, sapillai |
| Target Milestone: | --- | ||
| Target Release: | ODF 4.14.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | |||
Something is not correct with the way the storagecluster was applied via yaml. Still trying to figure what's wrong there. But manually editing the storageCluster yaml with new field works. Pratik, is this still a test blocker? Santosh, where are we with this issue? Haven't looked at it yet since we are still exploring non CLI options to configure OSD store. I'll take a look soon. Since we have decided to use UI for Greenfield, I've opened a PR - https://github.com/red-hat-storage/ocs-operator/pull/2132 to support using annotations for OSD store optmization in OCS operator. The annotation will be added by the UI. |
Description of problem (please be detailed as possible and provide log snippets): [RDR] Greenfield deployment does not pick value set in storagecluster for osdtype Version of all relevant components (if applicable): OCP version:- 4.14.0-0.nightly-2023-07-31-181848 ODF version:- 4.14.0-93 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? 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? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1.Deploy RDR cluster 2. Create storagecluster via cli and set osdStore: type: bluestore-rdr Actual results: Values passed from the yaml are not picked by ocs-operator Expected results: Additional info: storagecluster yaml:- https://privatebin.corp.redhat.com/?1b8acc50b1bc63a8#EMZFv9UeTjnMCsS9rRpcdtpCsxdoocqcfrjCS97boDQS