Back to bug 2101680
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-06-28 06:28:11 UTC | Link ID | Red Hat Issue Tracker RHCEPH-4628 | |
| Red Hat One Jira (issues.redhat.com) | 2022-06-28 06:29:49 UTC | Link ID | Red Hat Issue Tracker RHCSDASH-783 | |
| Sunil Angadi | 2022-06-28 07:52:51 UTC | Flags | needinfo?(nia) | |
| CC | nia | |||
| Target Release | 6.1 | 5.2 | ||
| Sunil Angadi | 2022-06-28 10:01:19 UTC | QA Contact | sangadi | skanta |
| Ernesto Puerta | 2022-06-28 10:38:40 UTC | Priority | unspecified | high |
| Assignee | epuertat | nia | ||
| QA Contact | skanta | sangadi | ||
| Ernesto Puerta | 2022-06-28 10:39:23 UTC | Status | NEW | ASSIGNED |
| CC | epuertat | |||
| QA Contact | sangadi | skanta | ||
| Nizamudeen | 2022-06-29 08:40:11 UTC | Status | ASSIGNED | POST |
| Link ID | Github ceph/ceph/pull/46889 | |||
| Flags | needinfo?(nia) | |||
| Nizamudeen | 2022-07-06 14:46:51 UTC | Blocks | 2053709 | |
| Status | POST | CLOSED | ||
| Resolution | --- | NEXTRELEASE | ||
| Flags | needinfo?(skanta) needinfo?(sangadi) | |||
| CC | sangadi | |||
| Last Closed | 2022-07-06 14:46:51 UTC | |||
| Sunil Angadi | 2022-07-07 06:21:08 UTC | Status | CLOSED | ASSIGNED |
| Target Release | 5.2 | 6.0 | ||
| Flags | needinfo?(sangadi) | |||
| Resolution | NEXTRELEASE | --- | ||
| Keywords | Reopened | |||
| Sunil Angadi | 2022-07-07 06:21:53 UTC | Flags | needinfo?(skanta) | needinfo+ |
| Nizamudeen | 2022-07-18 05:58:01 UTC | Status | ASSIGNED | POST |
| Akash Raj | 2022-07-20 06:36:28 UTC | Blocks | 2102272 | |
| Flags | needinfo?(nia) | |||
| CC | akraj | |||
| Nizamudeen | 2022-07-20 06:47:27 UTC | Status | POST | MODIFIED |
| Nizamudeen | 2022-07-20 06:54:38 UTC | Doc Text | Cause: If the cluster has only SSD devices or SSDs and NVMe devices, then Throughput option will be recommended even though it shouldn't be Consequence: No impact to the user or the cluster. Workaround (if any): User can still use the Advanced mode for deploying OSDs according to their desired specifications. Result: All the options in the Simple deployment options are still usable apart from this UI issue | |
| Doc Type | If docs needed, set a value | Known Issue | ||
| Flags | needinfo?(nia) | |||
| Anjana Suparna Sriram | 2022-07-20 09:19:25 UTC | Docs Contact | asriram | akraj |
| Akash Raj | 2022-07-25 06:00:40 UTC | Flags | needinfo?(nia) | |
| Doc Text | Cause: If the cluster has only SSD devices or SSDs and NVMe devices, then Throughput option will be recommended even though it shouldn't be Consequence: No impact to the user or the cluster. Workaround (if any): User can still use the Advanced mode for deploying OSDs according to their desired specifications. Result: All the options in the Simple deployment options are still usable apart from this UI issue | .”Throughput-optimized” option is recommended for clusters containing SSD and NVMe devices Previously, whenever the cluster had either only SSD devices or both SSDs and NVMe devices, the “Throughput-optimized” option would be recommended, even though it shouldn’t be and it had no impact either on the user or the cluster. As a workaround, users can use the “Advanced” mode for deploying OSDs according to their desired specifications and all the options in the “Simple” mode are still usable apart from this UI issue. |
||
| Akash Raj | 2022-07-25 06:15:58 UTC | Flags | needinfo?(nia) | |
| errata-xmlrpc | 2022-08-15 18:18:25 UTC | Fixed In Version | ceph-17.2.3-1.el9cp | |
| CC | tserlin | |||
| Status | MODIFIED | ON_QA | ||
| Masauso Lungu | 2022-09-27 08:44:51 UTC | Status | ON_QA | VERIFIED |
| CC | mlungu | |||
| Doc Text | .”Throughput-optimized” option is recommended for clusters containing SSD and NVMe devices Previously, whenever the cluster had either only SSD devices or both SSDs and NVMe devices, the “Throughput-optimized” option would be recommended, even though it shouldn’t be and it had no impact either on the user or the cluster. As a workaround, users can use the “Advanced” mode for deploying OSDs according to their desired specifications and all the options in the “Simple” mode are still usable apart from this UI issue. | .”Throughput-optimized” option is recommended for clusters containing SSD and NVMe devices Previously, whenever the cluster had either only SSD devices or both SSDs and NVMe devices, the “Throughput-optimized” option would be recommended, even though it should not be and it had no impact either on the user or the cluster. As a workaround, users can use the “Advanced” mode for deploying OSDs according to their desired specifications and all the options in the “Simple” mode are still usable apart from this UI issue. | ||
| Flags | needinfo?(nia) | |||
| Masauso Lungu | 2022-09-27 17:57:07 UTC | Blocks | 2126050 | |
| Nizamudeen | 2022-09-28 07:18:40 UTC | Doc Text | .”Throughput-optimized” option is recommended for clusters containing SSD and NVMe devices Previously, whenever the cluster had either only SSD devices or both SSDs and NVMe devices, the “Throughput-optimized” option would be recommended, even though it should not be and it had no impact either on the user or the cluster. As a workaround, users can use the “Advanced” mode for deploying OSDs according to their desired specifications and all the options in the “Simple” mode are still usable apart from this UI issue. | .”Throughput-optimized” option is recommended for clusters containing SSD and NVMe devices Previously, whenever the cluster had either only SSD devices or both SSDs and NVMe devices, the “Throughput-optimized” option would be recommended, even though it should not be and it had no impact either on the user or the cluster. As a workaround, users can use the “Advanced” mode for deploying OSDs according to their desired specifications and all the options in the “Simple” mode are still usable apart from this UI issue. |
| Flags | needinfo?(nia) | |||
| Red Hat Bugzilla | 2022-12-31 19:09:49 UTC | QA Contact | skanta | saraut |
| Red Hat Bugzilla | 2022-12-31 19:54:17 UTC | Assignee | nia | nobody |
| CC | nia | |||
| Red Hat Bugzilla | 2022-12-31 23:52:19 UTC | CC | epuertat | |
| Red Hat Bugzilla | 2023-01-01 05:39:35 UTC | CC | tserlin | |
| Red Hat Bugzilla | 2023-01-01 08:40:53 UTC | CC | sangadi | |
| Red Hat Bugzilla | 2023-01-01 08:41:28 UTC | QA Contact | saraut | |
| Alasdair Kergon | 2023-01-04 04:55:59 UTC | QA Contact | skanta | |
| Alasdair Kergon | 2023-01-04 05:00:47 UTC | Assignee | nobody | nia |
| Alasdair Kergon | 2023-01-04 05:20:55 UTC | CC | nia | |
| Alasdair Kergon | 2023-01-04 05:39:59 UTC | CC | sangadi | |
| Alasdair Kergon | 2023-01-04 06:16:17 UTC | CC | epuertat | |
| Alasdair Kergon | 2023-01-04 06:25:53 UTC | CC | tserlin | |
| Red Hat Bugzilla | 2023-01-09 08:29:44 UTC | CC | ceph-eng-bugs | |
| Alasdair Kergon | 2023-01-09 19:43:36 UTC | CC | ceph-eng-bugs | |
| errata-xmlrpc | 2023-03-20 18:37:56 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-03-20 18:57:08 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2022-07-06 14:46:51 UTC | 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 |
Back to bug 2101680