Back to bug 1956418

Who When What Removed Added
RHEL Program Management 2021-05-03 16:14:26 UTC Keywords FutureFeature
Gaurav Sitlani 2021-05-03 16:54:42 UTC CC gsitlani
Shriya Mulay 2021-05-03 17:01:17 UTC CC hchiramm
Flags needinfo?(hchiramm)
Humble Chirammal 2021-05-04 07:02:26 UTC CC anbehl
Flags needinfo?(hchiramm) needinfo?(anbehl)
Humble Chirammal 2021-05-04 07:02:54 UTC CC asachan
Flags needinfo?(asachan)
Anmol Sachan 2021-05-06 07:35:43 UTC CC nthomas
Flags needinfo?(asachan)
Shriya Mulay 2021-05-06 12:22:34 UTC Flags needinfo?(hchiramm)
Humble Chirammal 2021-05-06 14:58:27 UTC CC shan
Flags needinfo?(hchiramm) needinfo?(shan)
Sébastien Han 2021-05-06 15:09:28 UTC Flags needinfo?(shan)
Niels de Vos 2021-05-06 17:58:48 UTC CC ndevos
Mudit Agarwal 2021-05-27 03:12:17 UTC CC etamir, muagarwa
Flags needinfo?(anbehl) needinfo?(etamir)
Sonal 2021-05-28 11:39:34 UTC CC sarora
Eran Tamir 2021-05-31 13:05:58 UTC Flags needinfo?(etamir)
Sonal 2021-06-01 10:23:35 UTC CC bkunal
Flags needinfo?(bkunal)
Mudit Agarwal 2021-06-01 10:25:55 UTC Summary [GSS}[RFE] Automatic space reclaimation for RBD [GSS][RFE] Automatic space reclaimation for RBD
Bipin Kunal 2021-06-01 11:59:27 UTC CC mhackett
Flags needinfo?(bkunal) needinfo?(mhackett)
Sonal 2021-06-07 09:51:19 UTC Flags needinfo?(mhackett)
Sonal 2021-07-28 08:17:33 UTC Flags needinfo?(mhackett)
Niels de Vos 2021-08-16 08:11:24 UTC Status NEW ASSIGNED
Link ID Github csi-addons/spec/issues/15
Assignee hchiramm ndevos
Red Hat Bugzilla 2021-09-21 18:46:22 UTC CC asachan
Rejy M Cyriac 2021-09-26 22:42:39 UTC Product Red Hat OpenShift Container Storage Red Hat OpenShift Data Foundation
Component csi-driver csi-driver
Niels de Vos 2021-10-07 10:11:04 UTC CC nravinas
Link ID Red Hat Issue Tracker RHSTOR-1941
Jilju Joy 2021-10-27 13:23:22 UTC CC jijoy
Chris Blum 2021-11-01 08:57:40 UTC CC cblum
James Biao 2021-11-10 23:14:02 UTC CC jbiao
Priya Pandey 2021-11-11 11:12:21 UTC CC prpandey
Eric Beaudoin 2021-11-17 19:48:16 UTC CC ebeaudoi
Shriya Mulay 2021-12-13 09:44:18 UTC Comment 0 is private 1 0
Group private
Mudit Agarwal 2022-01-10 15:44:28 UTC Doc Type If docs needed, set a value Enhancement
Elad 2022-01-26 11:41:42 UTC QA Contact ebenahar jijoy
Mudit Agarwal 2022-01-26 11:45:29 UTC Status ASSIGNED MODIFIED
RHEL Program Management 2022-01-26 11:47:11 UTC Target Release --- ODF 4.10.0
Mudit Agarwal 2022-01-26 11:50:16 UTC Status MODIFIED ON_QA
Jilju Joy 2022-02-03 07:16:57 UTC QA Contact jijoy kmanohar
Mudit Agarwal 2022-03-04 12:13:30 UTC Blocks 2056571
Mudit Agarwal 2022-03-31 14:57:01 UTC Status ON_QA VERIFIED
CC rar
Flags needinfo?(rar)
Niels de Vos 2022-04-01 08:08:21 UTC Flags needinfo?(rar)
Doc Text Feature: Provide a way to reclaim space from RBD type PersistentVolumes.

Reason: RBD PersistentVolumes are thin-provisioned when created, meaning little space from the Ceph cluster is consumed. When data is stored on the PersistentVolume, the consumed storage increases automatically. After data is deleted, the consumed storage does not reduce, as the RBD PersistentVolume does not return the free'd space back to the Ceph cluster. For certain scenarios, it is wished that the free'd space is returned to the Ceph cluster, so that other workloads can benefit from it.

Result: The ReclaimSpace feature allows users to enable automatic reclaiming of free'd space from RBD PersistentVolumes. Users can add an annotation to their PersistentVolumeClaim or create a ReclaimSpaceCronJob for recurring space reclaiming, or run a ReclaimSpaceJob for a one-time operation.
Shilpi Sharma 2022-04-04 19:24:04 UTC CC shilpsha
Flags needinfo?(ndevos)
Niels de Vos 2022-04-05 10:29:43 UTC Flags needinfo?(ndevos)
Shilpi Sharma 2022-04-05 11:30:07 UTC Doc Text Feature: Provide a way to reclaim space from RBD type PersistentVolumes.

Reason: RBD PersistentVolumes are thin-provisioned when created, meaning little space from the Ceph cluster is consumed. When data is stored on the PersistentVolume, the consumed storage increases automatically. After data is deleted, the consumed storage does not reduce, as the RBD PersistentVolume does not return the free'd space back to the Ceph cluster. For certain scenarios, it is wished that the free'd space is returned to the Ceph cluster, so that other workloads can benefit from it.

Result: The ReclaimSpace feature allows users to enable automatic reclaiming of free'd space from RBD PersistentVolumes. Users can add an annotation to their PersistentVolumeClaim or create a ReclaimSpaceCronJob for recurring space reclaiming, or run a ReclaimSpaceJob for a one-time operation.
Automatic reclaim space for RADOS Block Devices

Previously, RADOS Block Devices (RBD) PersistentVolumes were thin-provisioned, that is, less space from the Ceph cluster was consumed. When data was stored on the PersistentVolume, the consumed storage increased automatically. However, after data was deleted, the consumed storage did not reduce, as the RBD PersistentVolume does not return the free space back to the Ceph cluster. In certain scenarios, it is required that the freed up space is returned to the Ceph cluster so that the other workloads can benefit from it.

With this update, the ReclaimSpace feature allows you to enable automatic reclaiming of freed up space from RBD PersistentVolumes with thin-provisioning. You can add an annotation to your PersistentVolume Claim, create a ReclaimSpaceCronJob for recurring space reclaiming, or run a ReclaimSpaceJob for a one-time operation.
Shilpi Sharma 2022-04-05 16:12:22 UTC Doc Text Automatic reclaim space for RADOS Block Devices

Previously, RADOS Block Devices (RBD) PersistentVolumes were thin-provisioned, that is, less space from the Ceph cluster was consumed. When data was stored on the PersistentVolume, the consumed storage increased automatically. However, after data was deleted, the consumed storage did not reduce, as the RBD PersistentVolume does not return the free space back to the Ceph cluster. In certain scenarios, it is required that the freed up space is returned to the Ceph cluster so that the other workloads can benefit from it.

With this update, the ReclaimSpace feature allows you to enable automatic reclaiming of freed up space from RBD PersistentVolumes with thin-provisioning. You can add an annotation to your PersistentVolume Claim, create a ReclaimSpaceCronJob for recurring space reclaiming, or run a ReclaimSpaceJob for a one-time operation.
.Automatic reclaim space for RADOS Block Devices

Previously, RADOS Block Devices (RBD) PersistentVolumes were thin-provisioned, that is, less space from the Ceph cluster was consumed. When data was stored on the PersistentVolume, the consumed storage increased automatically. However, after data was deleted, the consumed storage did not reduce, as the RBD PersistentVolume does not return the free space back to the Ceph cluster. In certain scenarios, it is required that the freed up space is returned to the Ceph cluster so that the other workloads can benefit from it.

With this update, the ReclaimSpace feature allows you to enable automatic reclaiming of freed up space from RBD PersistentVolumes with thin-provisioning. You can add an annotation to your PersistentVolume Claim, create a ReclaimSpaceCronJob for recurring space reclaiming, or run a ReclaimSpaceJob for a one-time operation.
Jilju Joy 2022-04-06 07:52:23 UTC Flags needinfo?(shilpsha)
Shilpi Sharma 2022-04-06 08:36:04 UTC Flags needinfo?(shilpsha) needinfo?(jijoy)
Shilpi Sharma 2022-04-06 10:37:27 UTC Doc Text .Automatic reclaim space for RADOS Block Devices

Previously, RADOS Block Devices (RBD) PersistentVolumes were thin-provisioned, that is, less space from the Ceph cluster was consumed. When data was stored on the PersistentVolume, the consumed storage increased automatically. However, after data was deleted, the consumed storage did not reduce, as the RBD PersistentVolume does not return the free space back to the Ceph cluster. In certain scenarios, it is required that the freed up space is returned to the Ceph cluster so that the other workloads can benefit from it.

With this update, the ReclaimSpace feature allows you to enable automatic reclaiming of freed up space from RBD PersistentVolumes with thin-provisioning. You can add an annotation to your PersistentVolume Claim, create a ReclaimSpaceCronJob for recurring space reclaiming, or run a ReclaimSpaceJob for a one-time operation.
.Automatic reclaim space for RADOS Block Devices

RADOS Block Devices(RBD) PersistentVolumes are thin-provisioned when created, meaning little space from the Ceph cluster is consumed. When data is stored on the PersistentVolume, the consumed storage increases automatically. However, after data is deleted, the consumed storage does not reduce, as the RBD PersistentVolume does not return the free space back to the Ceph cluster. In certain scenarios, it is required that the freed up space is returned to the Ceph cluster so that the other workloads can benefit from it.

With this update, the ReclaimSpace feature allows you to enable automatic reclaiming of freed up space from RBD PersistentVolumes with thin-provisioning. You can add an annotation to your PersistentVolume Claim, create a ReclaimSpaceCronJob for recurring space reclaiming, or run a ReclaimSpaceJob for a one-time operation.
errata-xmlrpc 2022-04-13 15:05:59 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2022-04-13 18:49:40 UTC Resolution --- ERRATA
Status RELEASE_PENDING CLOSED
Last Closed 2022-04-13 18:49:40 UTC
errata-xmlrpc 2022-04-13 18:50:11 UTC Link ID Red Hat Product Errata RHSA-2022:1372
Jilju Joy 2022-06-15 05:08:38 UTC Flags needinfo?(jijoy)
Prasad Desala 2022-06-17 06:58:08 UTC CC tdesala
Link ID Github red-hat-storage/ocs-ci/pull/5677
Elad 2023-08-09 16:37:41 UTC CC odf-bz-bot

Back to bug 1956418