Back to bug 2155766
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Matan Breizman | 2022-12-22 10:00:13 UTC | Assignee | nojha | mbreizma |
| Matan Breizman | 2022-12-22 10:05:06 UTC | Comment | 0 | updated |
| Red Hat One Jira (issues.redhat.com) | 2022-12-22 10:07:13 UTC | Link ID | Red Hat Issue Tracker RHCEPH-5834 | |
| Red Hat Bugzilla | 2022-12-31 19:13:24 UTC | CC | amathuri | |
| Red Hat Bugzilla | 2022-12-31 19:32:30 UTC | QA Contact | pdhiran | |
| Red Hat Bugzilla | 2022-12-31 19:59:56 UTC | CC | sseshasa | |
| Red Hat Bugzilla | 2022-12-31 22:29:22 UTC | Assignee | mbreizma | nojha |
| Red Hat Bugzilla | 2022-12-31 22:43:28 UTC | CC | rfriedma | |
| Red Hat Bugzilla | 2022-12-31 23:43:30 UTC | CC | rzarzyns | |
| Red Hat Bugzilla | 2022-12-31 23:45:49 UTC | CC | akupczyk | |
| Red Hat Bugzilla | 2023-01-01 05:35:16 UTC | CC | ksirivad | |
| Red Hat Bugzilla | 2023-01-01 06:27:05 UTC | CC | lflores | |
| Red Hat Bugzilla | 2023-01-01 06:28:58 UTC | CC | choffman | |
| Red Hat Bugzilla | 2023-01-01 08:38:50 UTC | CC | nojha | |
| Assignee | nojha | nobody | ||
| Red Hat Bugzilla | 2023-01-01 08:39:25 UTC | CC | pdhange | |
| Red Hat Bugzilla | 2023-01-01 08:50:07 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:46:11 UTC | Assignee | nobody | mbreizma |
| Alasdair Kergon | 2023-01-04 04:56:54 UTC | QA Contact | pdhiran | |
| 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:28:23 UTC | CC | ceph-eng-bugs | |
| Alasdair Kergon | 2023-01-09 19:43:36 UTC | CC | ceph-eng-bugs | |
| Pawan | 2023-07-10 03:04:46 UTC | Flags | needinfo?(mbreizma) | |
| Pawan | 2023-07-10 03:06:11 UTC | Flags | needinfo?(mbreizma) | |
| Matan Breizman | 2023-07-10 08:47:08 UTC | Status | NEW | POST |
| Flags | needinfo?(mbreizma) needinfo?(mbreizma) | |||
| errata-xmlrpc | 2023-07-11 05:43:05 UTC | Status | POST | MODIFIED |
| CC | tserlin | |||
| Fixed In Version | ceph-17.2.6-1.el9cp | |||
| Status | MODIFIED | ON_QA | ||
| Akash Raj | 2023-07-13 17:48:08 UTC | Docs Contact | akraj | |
| Flags | needinfo?(mbreizma) | |||
| CC | akraj | |||
| Blocks | 2221020 | |||
| Matan Breizman | 2023-07-16 13:16:27 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Doc Text | .Users can check for accurate number of pgs with crush rule taken into account Previously, check_pg_num() function did not take into account the root osds used by the crush rule. This resulted in an inaccurate pg num per osd count. With this fix, check_pg_num() will count the projected pg num which are part of the pools affected by the crush rule. Same for number of osds, instead of dividing the projected pg number total by all of the osdmap's osds, divide only by the osds used by the crush rule. | |||
| Flags | needinfo?(mbreizma) | |||
| Akash Raj | 2023-07-24 03:32:26 UTC | Doc Text | .Users can check for accurate number of pgs with crush rule taken into account Previously, check_pg_num() function did not take into account the root osds used by the crush rule. This resulted in an inaccurate pg num per osd count. With this fix, check_pg_num() will count the projected pg num which are part of the pools affected by the crush rule. Same for number of osds, instead of dividing the projected pg number total by all of the osdmap's osds, divide only by the osds used by the crush rule. | .Users can check for accurate number of placement groups with the crush rule Previously, `check_pg_num()` function did not take into account the root OSDs used by the crush rule. This resulted in an inaccurate placement group number per OSD count. With this fix, `check_pg_num()` counts the projected placement group number which are part of the pools affected by the crush rule. The same applies to the number of OSDs as well; instead of dividing the projected placement group number total by all the `osdmap` 's OSDs, it is divided only by the OSDs used by the crush rule. |
| Pawan | 2023-07-24 11:58:25 UTC | Status | ON_QA | VERIFIED |
| Akash Raj | 2023-07-25 04:35:42 UTC | Doc Text | .Users can check for accurate number of placement groups with the crush rule Previously, `check_pg_num()` function did not take into account the root OSDs used by the crush rule. This resulted in an inaccurate placement group number per OSD count. With this fix, `check_pg_num()` counts the projected placement group number which are part of the pools affected by the crush rule. The same applies to the number of OSDs as well; instead of dividing the projected placement group number total by all the `osdmap` 's OSDs, it is divided only by the OSDs used by the crush rule. | .Users can check for accurate number of placement groups with the crush rule Previously, `check_pg_num()` function would not take into account the root OSDs used by the crush rule. This resulted in an inaccurate placement group number per OSD count. With this fix, `check_pg_num()` counts the projected placement group number which are part of the pools affected by the crush rule. The same applies to the number of OSDs as well; instead of dividing the projected placement group number total by all the `osdmap` 's OSDs, it is divided only by the OSDs used by the crush rule. |
| errata-xmlrpc | 2023-08-03 16:32:17 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-03 16:45:09 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-08-03 16:45:09 UTC | |||
| errata-xmlrpc | 2023-08-03 16:46:06 UTC | Link ID | Red Hat Product Errata RHBA-2023:4473 |
Back to bug 2155766