Back to bug 2126559
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-09-13 20:58:40 UTC | Link ID | Red Hat Issue Tracker RHCEPH-5257 | |
| Vikhyat Umrao | 2022-09-13 21:21:51 UTC | Link ID | Ceph Project Bug Tracker 57529 | |
| Vikhyat Umrao | 2022-09-13 21:23:00 UTC | Assignee | nojha | sseshasa |
| Vikhyat Umrao | 2022-09-14 20:14:36 UTC | QA Contact | pdhiran | skanta |
| CC | skanta | |||
| Target Release | 6.1 | 6.0 | ||
| Status | NEW | ASSIGNED | ||
| Sridhar Seshasayee | 2022-09-15 12:37:38 UTC | Flags | needinfo?(skanta) | |
| Vikhyat Umrao | 2022-09-15 21:48:02 UTC | Flags | needinfo?(skanta) | |
| Sridhar Seshasayee | 2022-09-27 19:13:53 UTC | Flags | needinfo?(vumrao) | |
| Mike Hackett | 2022-09-28 18:36:06 UTC | CC | mhackett | |
| Vikhyat Umrao | 2022-10-10 16:57:09 UTC | Flags | needinfo?(vumrao) | |
| Shreyansh Sancheti | 2022-10-21 12:44:17 UTC | CC | ssanchet | |
| Sridhar Seshasayee | 2022-12-15 06:53:31 UTC | Status | ASSIGNED | POST |
| errata-xmlrpc | 2022-12-15 17:36:14 UTC | Status | POST | MODIFIED |
| CC | tserlin | |||
| Fixed In Version | ceph-17.2.5-26.el9cp | |||
| Status | MODIFIED | ON_QA | ||
| Eliska | 2022-12-19 13:06:03 UTC | Flags | needinfo?(sseshasa) | |
| CC | ekristov | |||
| Sridhar Seshasayee | 2022-12-19 13:38:26 UTC | Flags | needinfo?(sseshasa) | |
| Eliska | 2022-12-20 13:35:27 UTC | Flags | needinfo?(sseshasa) | |
| Sridhar Seshasayee | 2022-12-20 14:36:44 UTC | Flags | needinfo?(sseshasa) | |
| Eliska | 2022-12-21 08:16:06 UTC | Doc Type | If docs needed, set a value | No Doc Update |
| Red Hat Bugzilla | 2022-12-21 08:16:06 UTC | Doc Type | No Doc Update | No Doc Update |
| Red Hat Bugzilla | 2022-12-31 19:03:03 UTC | CC | ssanchet | |
| Red Hat Bugzilla | 2022-12-31 19:09:54 UTC | QA Contact | skanta | pdhiran |
| CC | skanta | |||
| Red Hat Bugzilla | 2022-12-31 19:13:29 UTC | CC | amathuri | |
| Red Hat Bugzilla | 2022-12-31 19:32:36 UTC | QA Contact | pdhiran | |
| Red Hat Bugzilla | 2022-12-31 20:00:01 UTC | Assignee | sseshasa | nojha |
| CC | sseshasa | |||
| Red Hat Bugzilla | 2022-12-31 22:43:31 UTC | CC | rfriedma | |
| Red Hat Bugzilla | 2022-12-31 23:43:33 UTC | CC | rzarzyns | |
| Red Hat Bugzilla | 2022-12-31 23:45:53 UTC | CC | akupczyk | |
| Red Hat Bugzilla | 2023-01-01 05:35:21 UTC | CC | ksirivad | |
| Red Hat Bugzilla | 2023-01-01 05:39:53 UTC | CC | tserlin | |
| Red Hat Bugzilla | 2023-01-01 05:52:46 UTC | CC | mhackett | |
| Red Hat Bugzilla | 2023-01-01 06:27:08 UTC | CC | lflores | |
| Red Hat Bugzilla | 2023-01-01 06:29:02 UTC | CC | choffman | |
| Red Hat Bugzilla | 2023-01-01 08:38:54 UTC | Assignee | nojha | nobody |
| CC | nojha | |||
| Red Hat Bugzilla | 2023-01-01 08:39:37 UTC | CC | pdhange | |
| Red Hat Bugzilla | 2023-01-01 08:50:12 UTC | CC | vumrao | |
| Red Hat Bugzilla | 2023-01-01 09:11:52 UTC | CC | racpatel | |
| Sunil Kumar Nagaraju | 2023-01-02 14:12:16 UTC | QA Contact | skanta | |
| CC | sunnagar | |||
| Alasdair Kergon | 2023-01-04 04:40:45 UTC | CC | akupczyk | |
| Alasdair Kergon | 2023-01-04 04:43:34 UTC | CC | amathuri | |
| Alasdair Kergon | 2023-01-04 04:53:27 UTC | Assignee | nobody | sseshasa |
| Alasdair Kergon | 2023-01-04 05:08:58 UTC | CC | ksirivad | |
| Alasdair Kergon | 2023-01-04 05:10:58 UTC | CC | lflores | |
| Alasdair Kergon | 2023-01-04 05:21:38 UTC | CC | nojha | |
| Alasdair Kergon | 2023-01-04 05:28:18 UTC | CC | pdhange | |
| Alasdair Kergon | 2023-01-04 05:33:51 UTC | CC | racpatel | |
| Alasdair Kergon | 2023-01-04 05:34:52 UTC | CC | rfriedma | |
| Alasdair Kergon | 2023-01-04 05:37:37 UTC | CC | rzarzyns | |
| Alasdair Kergon | 2023-01-04 05:41:45 UTC | CC | skanta | |
| Alasdair Kergon | 2023-01-04 05:47:37 UTC | CC | ssanchet | |
| Alasdair Kergon | 2023-01-04 05:59:30 UTC | CC | vumrao | |
| Alasdair Kergon | 2023-01-04 06:13:47 UTC | CC | choffman | |
| Alasdair Kergon | 2023-01-04 06:56:31 UTC | CC | sseshasa | |
| Alasdair Kergon | 2023-01-04 11:29:24 UTC | CC | mhackett | |
| Red Hat Bugzilla | 2023-01-09 08:31:12 UTC | Status | ON_QA | ASSIGNED |
| CC | ceph-eng-bugs | |||
| Alasdair Kergon | 2023-01-09 19:43:36 UTC | CC | ceph-eng-bugs | |
| Sridhar Seshasayee | 2023-01-10 12:40:56 UTC | Status | ASSIGNED | ON_QA |
| Sridhar Seshasayee | 2023-01-11 10:11:13 UTC | Status | ON_QA | VERIFIED |
| Flags | needinfo?(sseshasa) | |||
| Flags | needinfo?(sseshasa) | |||
| Eliska | 2023-01-12 13:11:58 UTC | Doc Text | Issue: The OSD benchmark test on OSD boot-up may sometimes not run even with osd_mclock_force_run_benchmark_on_init set to 'true'. Consequence: osd_mclock_max_capacity_iops_[hdd | |
| Doc Text | ,ssd] parameter value not overridden with the default values Workaround (if any): 1. set the osd_mclock_force_run_benchmark_on_init to true command : ceph config set osd osd_mclock_force_run_benchmark_on_init true 2. Remove the | |||
| Doc Text | value on the respective osd command: ceph config rm <osd.id> osd_mclock_max_capacity_iops_hdd 3. Restart the OSD Result: The osd "osd_mclock_max_capacity_iops_[ssd | |||
| Doc Text | ,hdd]" parameter will either be set with the default value or the new value if it's within the threshold setting. | |||
| Doc Type | No Doc Update | Known Issue | ||
| Docs Contact | ekristov | |||
| Eliska | 2023-01-13 07:16:42 UTC | Doc Text | Issue: The OSD benchmark test on OSD boot-up may sometimes not run even with osd_mclock_force_run_benchmark_on_init set to 'true'. Consequence: osd_mclock_max_capacity_iops_[hdd,ssd] parameter value not overridden with the default values Workaround (if any): 1. set the osd_mclock_force_run_benchmark_on_init to true command : ceph config set osd osd_mclock_force_run_benchmark_on_init true 2. Remove the value on the respective osd command: ceph config rm <osd.id> osd_mclock_max_capacity_iops_hdd 3. Restart the OSD Result: The osd "osd_mclock_max_capacity_iops_[ssd,hdd]" parameter will either be set with the default value or the new value if it's within the threshold setting. | .The Ceph OSD benchmark test might get skipped Currently, the Ceph OSD benchmark test boot-up might sometimes not run even with `osd_mclock_force_run_benchmark_on_init` parameter set to `true`. As a consequence, the `osd_mclock_max_capacity_iops_[hdd,ssd]` parameter value is not overridden with the default values. As a workaround, perform the following steps: . Set `osd_mclock_force_run_benchmark_on_init` to `true`: + .Example ---- [ceph: root@host01 /]# ceph config set osd osd_mclock_force_run_benchmark_on_init true ---- . Remove the value on the respective OSD: + .Syntax [source, subs=”verbatim,quotes”] ---- ceph config rm OSD._OSD_ID_ osd_mclock_max_capacity_iops_[hdd,ssd] ---- + .Example ---- [ceph: root@host01 /]# ceph config rm osd.0 osd_mclock_max_capacity_iops_hdd . Restart the OSD This results in the `osd_mclock_max_capacity_iops_[ssd,hdd]` parameter being either set with the default value or the new value if it is within the threshold setting. |
| Eliska | 2023-01-13 07:18:16 UTC | Blocks | 2126050 | |
| Eliska | 2023-01-13 07:25:06 UTC | Doc Text | .The Ceph OSD benchmark test might get skipped Currently, the Ceph OSD benchmark test boot-up might sometimes not run even with `osd_mclock_force_run_benchmark_on_init` parameter set to `true`. As a consequence, the `osd_mclock_max_capacity_iops_[hdd,ssd]` parameter value is not overridden with the default values. As a workaround, perform the following steps: . Set `osd_mclock_force_run_benchmark_on_init` to `true`: + .Example ---- [ceph: root@host01 /]# ceph config set osd osd_mclock_force_run_benchmark_on_init true ---- . Remove the value on the respective OSD: + .Syntax [source, subs=”verbatim,quotes”] ---- ceph config rm OSD._OSD_ID_ osd_mclock_max_capacity_iops_[hdd,ssd] ---- + .Example ---- [ceph: root@host01 /]# ceph config rm osd.0 osd_mclock_max_capacity_iops_hdd . Restart the OSD This results in the `osd_mclock_max_capacity_iops_[ssd,hdd]` parameter being either set with the default value or the new value if it is within the threshold setting. | .The Ceph OSD benchmark test might get skipped Currently, the Ceph OSD benchmark test boot-up might sometimes not run even with `osd_mclock_force_run_benchmark_on_init` parameter set to `true`. As a consequence, the `osd_mclock_max_capacity_iops_[hdd,ssd]` parameter value is not overridden with the default values. As a workaround, perform the following steps: . Set `osd_mclock_force_run_benchmark_on_init` to `true`: + .Example ---- [ceph: root@host01 /]# ceph config set osd osd_mclock_force_run_benchmark_on_init true ---- . Remove the value on the respective OSD: + .Syntax [source, subs=”verbatim,quotes”] ---- ceph config rm OSD._OSD_ID_ osd_mclock_max_capacity_iops_[hdd,ssd] ---- + .Example ---- [ceph: root@host01 /]# ceph config rm osd.0 osd_mclock_max_capacity_iops_hdd ---- . Restart the OSD This results in the `osd_mclock_max_capacity_iops_[ssd,hdd]` parameter being either set with the default value or the new value if it is within the threshold setting. |
| Eliska | 2023-01-13 07:29:22 UTC | Doc Text | .The Ceph OSD benchmark test might get skipped Currently, the Ceph OSD benchmark test boot-up might sometimes not run even with `osd_mclock_force_run_benchmark_on_init` parameter set to `true`. As a consequence, the `osd_mclock_max_capacity_iops_[hdd,ssd]` parameter value is not overridden with the default values. As a workaround, perform the following steps: . Set `osd_mclock_force_run_benchmark_on_init` to `true`: + .Example ---- [ceph: root@host01 /]# ceph config set osd osd_mclock_force_run_benchmark_on_init true ---- . Remove the value on the respective OSD: + .Syntax [source, subs=”verbatim,quotes”] ---- ceph config rm OSD._OSD_ID_ osd_mclock_max_capacity_iops_[hdd,ssd] ---- + .Example ---- [ceph: root@host01 /]# ceph config rm osd.0 osd_mclock_max_capacity_iops_hdd ---- . Restart the OSD This results in the `osd_mclock_max_capacity_iops_[ssd,hdd]` parameter being either set with the default value or the new value if it is within the threshold setting. | .The Ceph OSD benchmark test might get skipped Currently, the Ceph OSD benchmark test boot-up might sometimes not run even with `osd_mclock_force_run_benchmark_on_init` parameter set to `true`. As a consequence, the `osd_mclock_max_capacity_iops_[hdd,ssd]` parameter value is not overridden with the default values. As a workaround, perform the following steps: . Set `osd_mclock_force_run_benchmark_on_init` to `true`: + .Example ---- [ceph: root@host01 /]# ceph config set osd osd_mclock_force_run_benchmark_on_init true ---- . Remove the value on the respective OSD: + .Syntax [source,subs="verbatim,quotes"] ---- ceph config rm OSD._OSD_ID_ osd_mclock_max_capacity_iops_[hdd,ssd] ---- + .Example ---- [ceph: root@host01 /]# ceph config rm osd.0 osd_mclock_max_capacity_iops_hdd ---- . Restart the OSD This results in the `osd_mclock_max_capacity_iops_[ssd,hdd]` parameter being either set with the default value or the new value if it is within the threshold setting. |
| errata-xmlrpc | 2023-03-20 18:38:36 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-03-20 18:58:05 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-03-20 18:58:05 UTC | |||
| errata-xmlrpc | 2023-03-20 18:58:40 UTC | Link ID | Red Hat Product Errata RHBA-2023:1360 |
Back to bug 2126559