Back to bug 2092089

Who When What Removed Added
Tim Wilkinson 2022-05-31 18:51:06 UTC CC vivk
Red Hat One Jira (issues.redhat.com) 2022-05-31 18:52:05 UTC Link ID Red Hat Issue Tracker RHCEPH-4425
Vikhyat Umrao 2022-05-31 18:52:51 UTC Keywords Regression
Vikhyat Umrao 2022-05-31 18:56:26 UTC Summary setting osd_memory_target with osd/host does not succeed [Workload-DFG] Setting osd_memory_target with osd/host does not succeed
Vikhyat Umrao 2022-05-31 21:01:23 UTC Link ID Red Hat Bugzilla 2088640
Veera Raghava Reddy 2022-05-31 21:21:26 UTC CC vereddy
Vikhyat Umrao 2022-06-02 22:04:23 UTC Status NEW ASSIGNED
Adam King 2022-06-09 00:14:56 UTC Status ASSIGNED POST
errata-xmlrpc 2022-06-09 03:06:39 UTC Status POST MODIFIED
CC tserlin
Fixed In Version ceph-16.2.8-40.el8cp
Status MODIFIED ON_QA
Manasa 2022-06-13 04:51:16 UTC QA Contact mgowri prprakas
Pranav Prakash 2022-06-20 12:18:08 UTC Flags needinfo?(adking)
CC adking
Adam King 2022-06-20 15:56:04 UTC Flags needinfo?(adking)
Pranav Prakash 2022-06-21 11:31:58 UTC Status ON_QA VERIFIED
Akash Raj 2022-07-29 06:09:14 UTC Blocks 2102272
Akash Raj 2022-07-29 06:10:05 UTC Flags needinfo?(adking)
CC akraj
Adam King 2022-07-29 14:37:15 UTC Flags needinfo?(adking)
Doc Text Cause: if osd_memory_target was turned off globally, cephadm would remove the values user set for osd_memory_target at the host level. Additionally, for hosts with FQDN name, even though the crush map uses shortname, cephadm would still set the config option using the FQDN

Consequence: users could not manually set osd_memory_target at the host level and osd_memory_target autotuning would not work with FQDN hosts

Fix: cephadm now does not remove the host level osd_memory_target config settings if osd_memory_target_autotune is set to false. It will also always use shortname for hosts when setting host level osd_memory_target

Result: users should now be able to manually set the osd_memory_target if at the host level osd_memory_target_autotune is set to false and have the options not be removed by cephadm. Additionally, autotuning should now work with hosts added to cephadm with FQDN names
Doc Type If docs needed, set a value Bug Fix
Akash Raj 2022-08-03 14:11:47 UTC Doc Text Cause: if osd_memory_target was turned off globally, cephadm would remove the values user set for osd_memory_target at the host level. Additionally, for hosts with FQDN name, even though the crush map uses shortname, cephadm would still set the config option using the FQDN

Consequence: users could not manually set osd_memory_target at the host level and osd_memory_target autotuning would not work with FQDN hosts

Fix: cephadm now does not remove the host level osd_memory_target config settings if osd_memory_target_autotune is set to false. It will also always use shortname for hosts when setting host level osd_memory_target

Result: users should now be able to manually set the osd_memory_target if at the host level osd_memory_target_autotune is set to false and have the options not be removed by cephadm. Additionally, autotuning should now work with hosts added to cephadm with FQDN names
.`cephadm` no longer removes `osd_memory_target` config settings at host level

Previously, if `osd_memory_target` was turned off globally, `cephadm` would remove the values that the user set for `osd_memory_target` at the host level. Additionally, for hosts with FQDN name, even though the crush map uses a short name, `cephadm` would still set the config option using the FQDN. Due to this, users could not manually set `osd_memory_target` at the host level and `osd_memory_target` auto tuning would not work with FQDN hosts.

With this fix, the `osd_memory_target` config settings is not removed from `cephadm` at the host level if `osd_memory_target_autotune` is set to `false`. It also always uses a short name for hosts when setting host level `osd_memory_target`. If at the host level `osd_memory_target_autotune` is set to `false`, users can manually set the `osd_memory_target` and have the options not be removed by `cephadm`. Additionally, autotuning should now work with hosts added to `cephadm` with FQDN names.
Flags needinfo?(adking)
Docs Contact asriram akraj
Adam King 2022-08-03 17:05:28 UTC Flags needinfo?(adking)
Doc Text .`cephadm` no longer removes `osd_memory_target` config settings at host level

Previously, if `osd_memory_target` was turned off globally, `cephadm` would remove the values that the user set for `osd_memory_target` at the host level. Additionally, for hosts with FQDN name, even though the crush map uses a short name, `cephadm` would still set the config option using the FQDN. Due to this, users could not manually set `osd_memory_target` at the host level and `osd_memory_target` auto tuning would not work with FQDN hosts.

With this fix, the `osd_memory_target` config settings is not removed from `cephadm` at the host level if `osd_memory_target_autotune` is set to `false`. It also always uses a short name for hosts when setting host level `osd_memory_target`. If at the host level `osd_memory_target_autotune` is set to `false`, users can manually set the `osd_memory_target` and have the options not be removed by `cephadm`. Additionally, autotuning should now work with hosts added to `cephadm` with FQDN names.
.`cephadm` no longer removes `osd_memory_target` config settings at host level

Previously, if `osd_memory_target_autotune` was turned off globally, `cephadm` would remove the values that the user set for `osd_memory_target` at the host level. Additionally, for hosts with FQDN name, even though the crush map uses a short name, `cephadm` would still set the config option using the FQDN. Due to this, users could not manually set `osd_memory_target` at the host level and `osd_memory_target` auto tuning would not work with FQDN hosts.

With this fix, the `osd_memory_target` config settings is not removed from `cephadm` at the host level if `osd_memory_target_autotune` is set to `false`. It also always users a short name for hosts when setting host level `osd_memory_target`. If at the host level `osd_memory_target_autotune` is set to `false`, users can manually set the `osd_memory_target` and have the options not be removed by `cephadm`. Additionally, autotuning should now work with hosts added to `cephadm` with FQDN names.
errata-xmlrpc 2022-08-09 10:00:01 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2022-08-09 17:38:27 UTC Resolution --- ERRATA
Status RELEASE_PENDING CLOSED
Last Closed 2022-08-09 17:38:27 UTC
errata-xmlrpc 2022-08-09 17:38:53 UTC Link ID Red Hat Product Errata RHSA-2022:5997

Back to bug 2092089