Bug 2028693
| Summary: | RHCS 4.x to 5.x upgrade - Cephadm adopt should choose the correct value for autotune_memory_target_ratio | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vikhyat Umrao <vumrao> |
| Component: | Ceph-Ansible | Assignee: | Guillaume Abrioux <gabrioux> |
| Status: | CLOSED ERRATA | QA Contact: | Rajendra Khambadkar <rkhambad> |
| Severity: | high | Docs Contact: | Akash Raj <akraj> |
| Priority: | unspecified | ||
| Version: | 5.0 | CC: | akraj, aschoen, ceph-eng-bugs, gabrioux, gmeno, mgowri, nthomas, tserlin, vereddy, ykaul |
| Target Milestone: | --- | ||
| Target Release: | 5.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-ansible-6.0.27.0-1.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.Correct value is set for `autotune_memory_target_ratio` when migrating to `cephadm`
Previously, when migrating to `cephadm`, nothing would set a proper value for `autotune_memory_target_ratio` depending on the kind of deployment, HCI or non_HCI. Due to this, no ratio was set and there would be no difference between the two deployments.
With this fix, the `cephadm-adopt playbook` sets the right ratio depending on the kind of deployment and the right value is set for `autotune_memory_target_ratio` parameter.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-09 17:36:46 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: | 2102272 | ||
|
Description
Vikhyat Umrao
2021-12-02 23:25:19 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 Security, Bug Fix, and Enhancement 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:5997 |