Back to bug 2042320
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-01-19 09:11:42 UTC | Link ID | Red Hat Issue Tracker RHCEPH-2997 | |
| Kotresh HR | 2022-01-20 11:34:08 UTC | Link ID | Ceph Project Bug Tracker 53949 | |
| CC | khiremat | |||
| Greg Farnum | 2022-01-20 14:45:12 UTC | Status | NEW | ASSIGNED |
| Assignee | pdonnell | khiremat | ||
| CC | gfarnum | |||
| Matthias Muench | 2022-01-28 08:11:55 UTC | CC | mmuench | |
| Veera Raghava Reddy | 2022-01-28 19:00:29 UTC | CC | vereddy | |
| Hemanth Kumar | 2022-03-07 08:04:10 UTC | QA Contact | hyelloji | amk |
| Greg Farnum | 2022-03-09 15:37:07 UTC | Flags | needinfo?(mrajanna) needinfo?(khiremat) | |
| Madhu Rajanna | 2022-03-14 05:44:01 UTC | Flags | needinfo?(mrajanna) | |
| Kotresh HR | 2022-03-17 14:06:12 UTC | Flags | needinfo?(khiremat) | needinfo?(mrajanna) |
| Madhu Rajanna | 2022-03-22 02:40:23 UTC | Flags | needinfo?(mrajanna) | |
| Kotresh HR | 2022-04-06 05:53:57 UTC | Flags | needinfo?(mrajanna) | |
| Madhu Rajanna | 2022-04-06 05:55:47 UTC | Flags | needinfo?(mrajanna) | |
| Madhu Rajanna | 2022-04-06 05:56:19 UTC | Summary | CephFS: Log subvolume clone progress and the Failure details if subvolume clone fails. | CephFS: Log Failure messafe if subvolume clone fails. |
| Madhu Rajanna | 2022-04-06 05:57:06 UTC | Summary | CephFS: Log Failure messafe if subvolume clone fails. | CephFS: Log Failure details if subvolume clone fails. |
| Greg Farnum | 2022-04-14 13:34:31 UTC | Link ID | Ceph Project Bug Tracker 53949 | |
| Greg Farnum | 2022-04-14 13:35:04 UTC | Link ID | Ceph Project Bug Tracker 55190 | |
| Kotresh HR | 2022-04-18 09:30:20 UTC | Flags | needinfo?(vshankar) | |
| CC | vshankar | |||
| Venky Shankar | 2022-04-20 13:55:50 UTC | Flags | needinfo?(vshankar) | |
| Venky Shankar | 2022-05-23 07:55:24 UTC | Status | ASSIGNED | POST |
| Ken Dreyer (Red Hat) | 2022-05-24 20:29:40 UTC | CC | kdreyer | |
| Status | POST | MODIFIED | ||
| Fixed In Version | ceph-16.2.8-6.el8cp | |||
| errata-xmlrpc | 2022-05-24 23:37:46 UTC | Status | MODIFIED | ON_QA |
| Red Hat Bugzilla | 2022-05-26 08:30:36 UTC | CC | ceph-qe-bugs | |
| Mudit Agarwal | 2022-05-30 15:41:29 UTC | CC | assingh | |
| Amarnath | 2022-05-31 10:20:59 UTC | Flags | needinfo?(khiremat) | |
| Kotresh HR | 2022-06-01 09:21:22 UTC | Flags | needinfo?(khiremat) | needinfo?(amk) |
| CC | amk | |||
| Amarnath | 2022-06-02 07:01:03 UTC | Flags | needinfo?(amk) | |
| Status | ON_QA | VERIFIED | ||
| Akash Raj | 2022-07-06 07:32:12 UTC | Flags | needinfo?(khiremat) | |
| CC | akraj | |||
| Blocks | 2102272 | |||
| Docs Contact | akraj | |||
| Kotresh HR | 2022-07-06 12:52:42 UTC | Flags | needinfo?(khiremat) | |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Doc Text | Feature: Display clone failure reason in the existing clone status command. Reason: If the clone fails, there was no way to find out the actual reason for the failure apart from looking into logs. This feature adds the clone failure reason to the output of clone status command as below. $ ceph fs clone status cephfs clone1 { "status": { "state": "failed", "source": { "volume": "cephfs", "subvolume": "subvol1", "snapshot": "snap1" "size": "104857600" }, "failure": { "errno": "122", "errstr": "Disk quota exceeded" } } } The reason for a clone failure is shown with two fields as below: #. `errno` : error number #. `error_msg` : failure error string Result: With this feature in place, if the clone is failed, the reason for the failure can be checked using clone status command. |
|||
| Niels de Vos | 2022-07-08 08:50:47 UTC | Blocks | 2042318 | |
| Depends On | 2042318 | |||
| Akash Raj | 2022-07-13 07:13:29 UTC | Flags | needinfo?(khiremat) | |
| Doc Text | Feature: Display clone failure reason in the existing clone status command. Reason: If the clone fails, there was no way to find out the actual reason for the failure apart from looking into logs. This feature adds the clone failure reason to the output of clone status command as below. $ ceph fs clone status cephfs clone1 { "status": { "state": "failed", "source": { "volume": "cephfs", "subvolume": "subvol1", "snapshot": "snap1" "size": "104857600" }, "failure": { "errno": "122", "errstr": "Disk quota exceeded" } } } The reason for a clone failure is shown with two fields as below: #. `errno` : error number #. `error_msg` : failure error string Result: With this feature in place, if the clone is failed, the reason for the failure can be checked using clone status command. | .Reason for clone failure shows up when using `clone status` command Previously, whenever a clone failed, the only way to check the reason for failure was by looking into the logs. T With this release, the reason for clone failure is shown in the output of the `clone status` command: .Example ---- [ceph: root@host01 /]# ceph fs clone status cephfs clone1 { "status": { "state": "failed", "source": { "volume": "cephfs", "subvolume": "subvol1", "snapshot": "snap1" "size": "104857600" }, "failure": { "errno": "122", "errstr": "Disk quota exceeded" } } } ---- The reason for a clone failure is shown in two fields: `errno` : error number `error_msg` : failure error string |
||
| Kotresh HR | 2022-07-14 12:26:26 UTC | Flags | needinfo?(khiremat) | |
| Akash Raj | 2022-07-19 09:31:56 UTC | Doc Text | .Reason for clone failure shows up when using `clone status` command Previously, whenever a clone failed, the only way to check the reason for failure was by looking into the logs. T With this release, the reason for clone failure is shown in the output of the `clone status` command: .Example ---- [ceph: root@host01 /]# ceph fs clone status cephfs clone1 { "status": { "state": "failed", "source": { "volume": "cephfs", "subvolume": "subvol1", "snapshot": "snap1" "size": "104857600" }, "failure": { "errno": "122", "errstr": "Disk quota exceeded" } } } ---- The reason for a clone failure is shown in two fields: `errno` : error number `error_msg` : failure error string | .Reason for clone failure shows up when using `clone status` command Previously, whenever a clone failed, the only way to check the reason for failure was by looking into the logs. With this release, the reason for clone failure is shown in the output of the `clone status` command: .Example ---- [ceph: root@host01 /]# ceph fs clone status cephfs clone1 { "status": { "state": "failed", "source": { "volume": "cephfs", "subvolume": "subvol1", "snapshot": "snap1" "size": "104857600" }, "failure": { "errno": "122", "errstr": "Disk quota exceeded" } } } ---- The reason for a clone failure is shown in two fields: `errno` : error number `error_msg` : failure error string |
| Akash Raj | 2022-07-20 05:43:08 UTC | Doc Text | .Reason for clone failure shows up when using `clone status` command Previously, whenever a clone failed, the only way to check the reason for failure was by looking into the logs. With this release, the reason for clone failure is shown in the output of the `clone status` command: .Example ---- [ceph: root@host01 /]# ceph fs clone status cephfs clone1 { "status": { "state": "failed", "source": { "volume": "cephfs", "subvolume": "subvol1", "snapshot": "snap1" "size": "104857600" }, "failure": { "errno": "122", "errstr": "Disk quota exceeded" } } } ---- The reason for a clone failure is shown in two fields: `errno` : error number `error_msg` : failure error string | .Reason for clone failure shows up when using `clone status` command Previously, whenever a clone failed, the only way to check the reason for failure was by looking into the logs. With this release, the reason for clone failure is shown in the output of the `clone status` command: .Example ---- [ceph: root@host01 /]# ceph fs clone status cephfs clone1 { "status": { "state": "failed", "source": { "volume": "cephfs", "subvolume": "subvol1", "snapshot": "snap1" "size": "104857600" }, "failure": { "errno": "122", "errstr": "Disk quota exceeded" } } } ---- The reason for a clone failure is shown in two fields: - `errno` : error number - `error_msg` : failure error string |
| errata-xmlrpc | 2022-08-09 09:56:21 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-08-09 17:37:27 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-08-09 17:37:27 UTC | |||
| errata-xmlrpc | 2022-08-09 17:38:03 UTC | Link ID | Red Hat Product Errata RHSA-2022:5997 |
Back to bug 2042320