Back to bug 2111282
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-07-26 23:49:33 UTC | Link ID | Red Hat Issue Tracker RHCEPH-4937 | |
| Vikhyat Umrao | 2022-07-27 20:52:46 UTC | Flags | needinfo?(sseshasa) | |
| Assignee | nojha | sseshasa | ||
| Sridhar Seshasayee | 2022-07-28 05:58:40 UTC | Status | NEW | ASSIGNED |
| Vikhyat Umrao | 2022-08-01 23:23:52 UTC | Severity | high | medium |
| Sridhar Seshasayee | 2022-11-02 15:57:01 UTC | Link ID | Ceph Project Bug Tracker 57963 | |
| Sridhar Seshasayee | 2022-11-02 15:58:50 UTC | Flags | needinfo?(sseshasa) | |
| Red Hat Bugzilla | 2022-12-31 19:09:37 UTC | QA Contact | pdhiran | skanta |
| QA Contact | skanta | pdhiran | ||
| Red Hat Bugzilla | 2022-12-31 19:13:30 UTC | CC | amathuri | |
| Red Hat Bugzilla | 2022-12-31 19:32:37 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:32 UTC | CC | rfriedma | |
| Red Hat Bugzilla | 2022-12-31 23:43:34 UTC | CC | rzarzyns | |
| Red Hat Bugzilla | 2022-12-31 23:45:54 UTC | CC | akupczyk | |
| Red Hat Bugzilla | 2023-01-01 05:35:23 UTC | CC | ksirivad | |
| Red Hat Bugzilla | 2023-01-01 06:27:10 UTC | CC | lflores | |
| Red Hat Bugzilla | 2023-01-01 06:29:04 UTC | CC | choffman | |
| Red Hat Bugzilla | 2023-01-01 08:38:31 UTC | CC | nojha | |
| Assignee | nojha | nobody | ||
| Red Hat Bugzilla | 2023-01-01 08:39:39 UTC | CC | pdhange | |
| Red Hat Bugzilla | 2023-01-01 08:49:53 UTC | CC | vumrao | |
| 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 04:55:59 UTC | QA Contact | skanta | |
| 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:34:52 UTC | CC | rfriedma | |
| Alasdair Kergon | 2023-01-04 05:37:37 UTC | CC | rzarzyns | |
| 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 | |
| Red Hat Bugzilla | 2023-01-09 08:29:50 UTC | CC | ceph-eng-bugs | |
| Alasdair Kergon | 2023-01-09 19:43:36 UTC | CC | ceph-eng-bugs | |
| Radoslaw Zarzynski | 2023-03-27 18:05:47 UTC | Status | ASSIGNED | POST |
| Ken Dreyer (Red Hat) | 2023-04-03 19:21:06 UTC | Depends On | 2180567 | |
| CC | kdreyer | |||
| Ken Dreyer (Red Hat) | 2023-04-10 20:48:59 UTC | Status | POST | MODIFIED |
| errata-xmlrpc | 2023-04-10 20:51:20 UTC | Status | MODIFIED | ON_QA |
| Akash Raj | 2023-05-03 06:38:01 UTC | Status | ON_QA | VERIFIED |
| CC | akraj | |||
| Flags | needinfo?(sseshasa) | |||
| Docs Contact | akraj | |||
| Sridhar Seshasayee | 2023-05-08 05:05:31 UTC | Doc Text | Cause: The values for osd_mclock_max_capacity_iops_[ssd|hdd] are set depending on the OSD's underlying device type. The config options also have default values that were displayed when queried. For e.g., if the underlying device type for an OSD is SSD, the default value for the HDD option i.e., osd_mclock_max_capacity_iops_hdd was also shown with a non-zero value. Consequence: Displaying values for both HDD and SSD options of an OSD when queried caused confusion regarding the correct option to interpret. Fix: Set the IOPS capacity related config option of the OSD that matches the underlying device type. The alternate or the inactive config option is set to 0. Result: With the fix, when a user queries the IOPS capacity for an OSD, only the config option that matches the underlying device type shows the measured/default value. The alternative/inactive option is set to 0 to clearly indicate that it is disabled. | |
| Flags | needinfo?(sseshasa) | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Akash Raj | 2023-05-16 03:56:42 UTC | Doc Text | Cause: The values for osd_mclock_max_capacity_iops_[ssd|hdd] are set depending on the OSD's underlying device type. The config options also have default values that were displayed when queried. For e.g., if the underlying device type for an OSD is SSD, the default value for the HDD option i.e., osd_mclock_max_capacity_iops_hdd was also shown with a non-zero value. Consequence: Displaying values for both HDD and SSD options of an OSD when queried caused confusion regarding the correct option to interpret. Fix: Set the IOPS capacity related config option of the OSD that matches the underlying device type. The alternate or the inactive config option is set to 0. Result: With the fix, when a user queries the IOPS capacity for an OSD, only the config option that matches the underlying device type shows the measured/default value. The alternative/inactive option is set to 0 to clearly indicate that it is disabled. | .Upon querying the IOPS capacity for an OSD, only the configuration option that matches the underlying device type shows the measured/default value Previously, the `osd_mclock_max_capacity_iops_[ssd|hdd]` values were set depending on the OSD's underlying device type. The configuration options also had default values that were displayed when queried. For example, if the underlying device type for an OSD was SSD, the default value for the HDD option, `osd_mclock_max_capacity_iops_hdd`, was also displayed with a non-zero value. Due to this, displaying values for both HDD and SSD options of an OSD when queried, caused confusion regarding the correct option to interpret. With this fix, the IOPS capacity-related configuration option of the OSD that matches the underlying device type is set and the alternate/inactive configuration option is set to `0`. When a user queries the IOPS capacity for an OSD, only the configuration option that matches the underlying device type shows the measured/default value. The alternative/inactive option is set to 0 to clearly indicate that it is disabled. |
| Akash Raj | 2023-05-19 11:58:25 UTC | Blocks | 2192813 | |
| errata-xmlrpc | 2023-06-15 09:07:53 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-06-15 09:15:33 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-06-15 09:15:33 UTC | |||
| errata-xmlrpc | 2023-06-15 09:16:57 UTC | Link ID | Red Hat Product Errata RHSA-2023:3623 |
Back to bug 2111282