Back to bug 2107849

Who When What Removed Added
Adam King 2022-07-16 19:39:27 UTC Target Release 6.1 6.0
Red Hat One Jira (issues.redhat.com) 2022-07-16 19:42:20 UTC Link ID Red Hat Issue Tracker RHCEPH-4779
Veera Raghava Reddy 2022-07-17 10:18:56 UTC CC vereddy
Severity unspecified high
QA Contact mgowri prprakas
Ken Dreyer (Red Hat) 2022-07-29 18:31:24 UTC CC kdreyer
Adam King 2022-08-22 13:20:10 UTC Status NEW POST
errata-xmlrpc 2022-08-22 20:58:02 UTC Status POST MODIFIED
Fixed In Version ceph-17.2.3-12.el9cp
CC tserlin
Status MODIFIED ON_QA
Manisha Saini 2022-08-24 07:33:33 UTC CC msaini
QA Contact prprakas msaini
Manisha Saini 2022-08-29 10:05:22 UTC Status ON_QA VERIFIED
Eliska 2022-09-08 07:10:10 UTC CC ekristov
Flags needinfo?(adking)
Adam King 2022-09-08 18:45:33 UTC Doc Type If docs needed, set a value Bug Fix
Flags needinfo?(adking)
Doc Text .`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.
Eliska 2022-09-13 08:53:03 UTC Blocks 2126050
Eliska 2022-09-20 14:33:52 UTC Doc Text .`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.
.`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 configuration 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.
Eliska 2022-09-27 11:59:50 UTC Docs Contact asriram ekristov
Red Hat Bugzilla 2023-01-01 05:37:28 UTC Assignee adking nobody
Red Hat Bugzilla 2023-01-01 05:39:52 UTC CC tserlin
Red Hat Bugzilla 2023-01-01 06:03:27 UTC CC kdreyer
Red Hat Bugzilla 2023-01-01 08:37:28 UTC QA Contact msaini
CC msaini
Red Hat Bugzilla 2023-01-01 08:47:44 UTC CC vereddy
Alasdair Kergon 2023-01-04 04:33:20 UTC Assignee nobody adking
Alasdair Kergon 2023-01-04 04:42:26 UTC QA Contact msaini
Alasdair Kergon 2023-01-04 05:03:42 UTC CC kdreyer
Alasdair Kergon 2023-01-04 05:18:08 UTC CC msaini
Alasdair Kergon 2023-01-04 06:59:12 UTC CC vereddy
errata-xmlrpc 2023-03-20 18:38:05 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2023-03-20 18:57:08 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2023-03-20 18:57:08 UTC
errata-xmlrpc 2023-03-20 18:57:49 UTC Link ID Red Hat Product Errata RHBA-2023:1360
Manisha Saini 2023-06-12 09:25:21 UTC Locked 0 1

Back to bug 2107849