Bug 1973149 - Add setting autotune_memory_target_ratio for hci envs to the ceph-ansible cephadm-adopt playbook [NEEDINFO]
Summary: Add setting autotune_memory_target_ratio for hci envs to the ceph-ansible cep...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 5.0z1
Assignee: Dimitri Savineau
QA Contact: Sunil Kumar Nagaraju
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-17 10:38 UTC by Vikhyat Umrao
Modified: 2021-11-02 16:39 UTC (History)
12 users (show)

Fixed In Version: ceph-ansible-6.0.13-1.el8cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-02 16:38:26 UTC
Embargoed:
mhull: needinfo?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 6706 0 None open cephadm-adopt: enable osd memory autotune for HCI 2021-07-12 16:02:11 UTC
Red Hat Issue Tracker RHCEPH-370 0 None None None 2021-08-19 05:13:27 UTC
Red Hat Product Errata RHBA-2021:4105 0 None None None 2021-11-02 16:39:08 UTC

Description Vikhyat Umrao 2021-06-17 10:38:35 UTC 
Description of problem:
add setting autotune_memory_target_ratio for hci envs to the
ceph-ansible cephadm-adopt playbook - this is required so that we use
the right amount of memory when autotuning is turned on later, when we
no longer have ansible configs around


Version-Release number of selected component (if applicable):
RHCS 5
Comment 12 errata-xmlrpc 2021-11-02 16:38:26 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 (Red Hat Ceph Storage 5.0 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/RHBA-2021:4105
Note You need to log in before you can comment on or make changes to this bug.