Bug 1962744
| Summary: | [GSS][ceph-volume]'ceph-volume' ignores the 'bluestore_block_db_size' paramenter provided in ceph.conf | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Janmejay Singh <jansingh> |
| Component: | Ceph-Volume | Assignee: | Andrew Schoen <aschoen> |
| Status: | CLOSED ERRATA | QA Contact: | Rahul Lepakshi <rlepaksh> |
| Severity: | medium | Docs Contact: | Ranjini M N <rmandyam> |
| Priority: | unspecified | ||
| Version: | 4.2 | CC: | agunn, aschoen, ceph-eng-bugs, ceph-qe-bugs, kdreyer, mhackett, mmuench, rlepaksh, rmandyam, sunnagar, vereddy |
| Target Milestone: | --- | ||
| Target Release: | 5.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.6-1.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.`ceph-volume` uses `bluestore_block_db_size` parameter for deploying Ceph OSDs
Previously, `ceph-volume` would create an incorrectly sized block.db logical volume when deploying Ceph OSDs as it would ignore the value of `bluestore_block_db_size` parameter in the `ceph.conf` file.
With this release, `ceph-volume` uses the value of `bluestore_block_db_size` parameter from the `ceph.conf` file when creating the block.db logical volumes and Ceph OSDs are deployed as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-04-04 10:20:39 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2031073 | ||
|
Comment 4
Ken Dreyer (Red Hat)
2021-10-06 13:55:01 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 (Moderate: Red Hat Ceph Storage 5.1 Security, Enhancement, and 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-2022:1174 |