Back to bug 2099193
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-06-20 09:56:45 UTC | Link ID | Red Hat Issue Tracker RHCEPH-4580 | |
| Prashant Dhange | 2022-06-21 07:17:08 UTC | QA Contact | pdhiran | skanta |
| CC | ngangadh | |||
| Link ID | Github ceph/ceph/pull/46761 Ceph Project Bug Tracker 56136 | |||
| Prashant Dhange | 2022-06-21 07:17:44 UTC | Assignee | nojha | pdhange |
| Status | NEW | ASSIGNED | ||
| Vikhyat Umrao | 2022-09-08 14:05:06 UTC | Target Release | 6.1 | 6.0 |
| Prashant Dhange | 2022-09-08 14:51:40 UTC | Summary | [RADOS]: Getting New PG number when autoscale is off | (RHCS 6.0) [RADOS]: Getting New PG number when autoscale is off |
| Vikhyat Umrao | 2022-09-08 15:06:23 UTC | Link ID | Github ceph/ceph/pull/47925 | |
| Prashant Dhange | 2022-10-20 03:58:32 UTC | Summary | (RHCS 6.0) [RADOS]: Getting New PG number when autoscale is off | (RHCS 6.1) [RADOS]: Getting New PG number when autoscale is off |
| Prashant Dhange | 2022-10-20 03:59:00 UTC | Summary | (RHCS 6.1) [RADOS]: Getting New PG number when autoscale is off | (RHCS 6.0) [RADOS]: Getting New PG number when autoscale is off |
| Neha Ojha | 2022-12-07 18:44:14 UTC | Flags | needinfo?(pdhange) | |
| Prashant Dhange | 2022-12-08 02:59:40 UTC | Flags | needinfo?(pdhange) | |
| Status | ASSIGNED | POST | ||
| errata-xmlrpc | 2022-12-08 07:44:06 UTC | Fixed In Version | ceph-17.2.5-17.el9cp | |
| CC | tserlin | |||
| Status | POST | MODIFIED | ||
| Status | MODIFIED | ON_QA | ||
| Eliska | 2022-12-08 09:18:51 UTC | CC | ekristov | |
| Flags | needinfo?(pdhange) | |||
| Prashant Dhange | 2022-12-09 06:12:44 UTC | Flags | needinfo?(pdhange) | needinfo?(ekristov) |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Doc Text | Cause: The autoscale-status command showing NEW PG_NUM value even though pg-autoscaling is not enabled. Consequence: This is misleading for end user and suggest that pg autoscaler is applying NEW PG_NUM value to pool which is not the case here. Fix: If noautoscale is set, do not show NEW PG_NUM value in the autoscale-status command output. Result: If noautoscale is set, NEW PG_NUM will not be shown in the autoscale-status command output. |
|||
| Eliska | 2022-12-13 10:20:39 UTC | Status | ON_QA | VERIFIED |
| Docs Contact | ekristov | |||
| Doc Text | Cause: The autoscale-status command showing NEW PG_NUM value even though pg-autoscaling is not enabled. Consequence: This is misleading for end user and suggest that pg autoscaler is applying NEW PG_NUM value to pool which is not the case here. Fix: If noautoscale is set, do not show NEW PG_NUM value in the autoscale-status command output. Result: If noautoscale is set, NEW PG_NUM will not be shown in the autoscale-status command output. | .The `autoscale-status` command no longer displays the `NEW PG_NUM` value if PG-autoscaling is disabled Previously, the `autoscale-status` command would show the `NEW PG_NUM` value even though PG-autoscaling was not enabled. This would mislead the end user by suggesting that PG autoscaler applied `NEW PG_NUM` value to the pool, which was not the case. With this fix, if the `noautoscale` flag is set, the `NEW PG_NUM` value is not shown in the `autoscale-status` command output. | ||
| Flags | needinfo?(ekristov) | needinfo?(pdhange) | ||
| Eliska | 2022-12-13 10:21:41 UTC | Blocks | 2126050 | |
| Red Hat Bugzilla | 2022-12-31 19:09:44 UTC | QA Contact | skanta | pdhiran |
| Red Hat Bugzilla | 2022-12-31 19:13:34 UTC | CC | amathuri | |
| Red Hat Bugzilla | 2022-12-31 19:32:42 UTC | QA Contact | pdhiran | |
| Red Hat Bugzilla | 2022-12-31 20:00:06 UTC | CC | sseshasa | |
| Red Hat Bugzilla | 2022-12-31 22:43:36 UTC | CC | rfriedma | |
| Red Hat Bugzilla | 2022-12-31 23:43:40 UTC | CC | rzarzyns | |
| Red Hat Bugzilla | 2022-12-31 23:45:59 UTC | CC | akupczyk | |
| Red Hat Bugzilla | 2023-01-01 05:35:29 UTC | CC | ksirivad | |
| Red Hat Bugzilla | 2023-01-01 05:39:42 UTC | CC | tserlin | |
| Red Hat Bugzilla | 2023-01-01 06:27:15 UTC | CC | lflores | |
| Red Hat Bugzilla | 2023-01-01 06:29:08 UTC | CC | choffman | |
| Red Hat Bugzilla | 2023-01-01 08:38:38 UTC | CC | nojha | |
| Red Hat Bugzilla | 2023-01-01 08:39:48 UTC | Assignee | pdhange | nobody |
| CC | pdhange | |||
| Red Hat Bugzilla | 2023-01-01 08:49:58 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:49:11 UTC | Assignee | nobody | pdhange |
| 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:25:53 UTC | CC | tserlin | |
| Alasdair Kergon | 2023-01-04 06:56:31 UTC | CC | sseshasa | |
| Prashant Dhange | 2023-01-06 20:38:00 UTC | Flags | needinfo?(pdhange) | |
| Red Hat Bugzilla | 2023-01-09 08:29:02 UTC | CC | ceph-eng-bugs | |
| Alasdair Kergon | 2023-01-09 19:43:36 UTC | CC | ceph-eng-bugs | |
| Red Hat Bugzilla | 2023-02-28 18:56:25 UTC | CC | ngangadh | |
| errata-xmlrpc | 2023-03-20 18:37:54 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-03-20 18:56:39 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-03-20 18:56:39 UTC | |||
| errata-xmlrpc | 2023-03-20 18:57:06 UTC | Link ID | Red Hat Product Errata RHBA-2023:1360 |
Back to bug 2099193