Back to bug 1962511
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Vasishta | 2021-05-20 09:00:28 UTC | CC | jharriga | |
| Juan Miguel Olmo | 2021-05-25 10:47:53 UTC | Status | NEW | ASSIGNED |
| Sebastian Wagner | 2021-05-25 19:06:53 UTC | Target Release | 5.0 | 5.1 |
| CC | sewagner | |||
| Sebastian Wagner | 2021-05-31 12:50:53 UTC | Priority | unspecified | medium |
| Severity | high | low | ||
| Red Hat One Jira (issues.redhat.com) | 2021-05-31 12:52:19 UTC | Link ID | Red Hat Issue Tracker RHCEPH-104 | |
| Juan Miguel Olmo | 2021-06-02 10:09:19 UTC | Link ID | Ceph Project Bug Tracker 51061 | |
| Juan Miguel Olmo | 2021-06-02 10:09:43 UTC | Status | ASSIGNED | MODIFIED |
| Ken Dreyer (Red Hat) | 2021-10-06 14:13:56 UTC | CC | kdreyer | |
| Status | MODIFIED | ASSIGNED | ||
| Juan Miguel Olmo | 2021-10-06 14:46:07 UTC | Flags | needinfo?(adking) | |
| CC | adking | |||
| Adam King | 2021-10-06 15:33:57 UTC | Flags | needinfo?(adking) | |
| Juan Miguel Olmo | 2021-10-06 16:17:31 UTC | Flags | needinfo?(sewagner) | |
| Sebastian Wagner | 2021-10-13 13:05:06 UTC | Target Release | 5.1 | 5.2 |
| Assignee | jolmomar | sewagner | ||
| Sebastian Wagner | 2021-10-13 13:05:15 UTC | Status | ASSIGNED | NEW |
| Red Hat Bugzilla | 2022-01-31 23:32:05 UTC | CC | sewagner | |
| Assignee | sewagner | adking | ||
| Adam King | 2022-05-25 18:34:06 UTC | Flags | needinfo?(sewagner) | |
| Status | NEW | POST | ||
| errata-xmlrpc | 2022-05-25 23:49:10 UTC | CC | tserlin | |
| Status | POST | MODIFIED | ||
| Fixed In Version | ceph-16.2.8-14.el8cp | |||
| Status | MODIFIED | ON_QA | ||
| Vasishta | 2022-05-26 04:35:05 UTC | QA Contact | vashastr | mgowri |
| Manasa | 2022-06-01 07:33:17 UTC | Status | ON_QA | VERIFIED |
| Akash Raj | 2022-07-06 06:45:41 UTC | Blocks | 2102272 | |
| CC | akraj | |||
| Akash Raj | 2022-07-06 06:49:25 UTC | Flags | needinfo?(adking) | |
| Akash Raj | 2022-07-06 07:10:18 UTC | Docs Contact | knortema | akraj |
| Adam King | 2022-07-06 20:50:17 UTC | Doc Text | Cause: devices with GPT headers were not marked unavailable Consequence: if there were valid devices but also devices with GPT headers, cephadm would attempt to create OSDs on them in a batch and since OSDs cannot be created on devices with GPT headers, the batch OSD creation would fail and no OSDs would be made Fix: no unavailable devices are passed when making OSDs in a batch Result: having devices with GPT headers no longer blocks OSDs being created on valid devices | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Flags | needinfo?(adking) | |||
| Akash Raj | 2022-07-13 06:07:48 UTC | Flags | needinfo?(adking) | |
| Doc Text | Cause: devices with GPT headers were not marked unavailable Consequence: if there were valid devices but also devices with GPT headers, cephadm would attempt to create OSDs on them in a batch and since OSDs cannot be created on devices with GPT headers, the batch OSD creation would fail and no OSDs would be made Fix: no unavailable devices are passed when making OSDs in a batch Result: having devices with GPT headers no longer blocks OSDs being created on valid devices | .Unavailable devices are no longer passed when creating OSDs in a batch Previously, devices with GPT headers were not marked as unavailable. Cephadm would attempt to create OSDs on those devices, along with other valid devices, in a batch leading to failure of the batch OSD creation, since OSDs cannot be created on devices with GPT headers. This would not create OSDs. With this fix, unavailable devices are no longer passed when creating OSDs in a batch and having devices with GPT headers no longer blocks creating OSDs on valid devices. |
||
| Adam King | 2022-07-13 12:37:11 UTC | Flags | needinfo?(adking) | |
| errata-xmlrpc | 2022-08-09 09:53:07 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-08-09 17:35:53 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2022-08-09 17:35:53 UTC | |||
| errata-xmlrpc | 2022-08-09 17:36:30 UTC | Link ID | Red Hat Product Errata RHSA-2022:5997 |
Back to bug 1962511