Description of problem (please be detailed as possible and provide log snippets): - Need Volume Snapshots automation feature to be enabled in OCS with retention period. Version of all relevant components (if applicable): all Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? - This will help CU create a regular snapshot of volumes that's very critical to them without manual effort. Is there any workaround available to the best of your knowledge? N/A Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? N/A Can this issue reproducible? N/A Can this issue reproduce from the UI? N/A If this is a regression, please provide more details to justify this: N/A Steps to Reproduce: - The currently available option is to create a volume snapshot from the UI of any PVC. - CU wants to automate this feature so that they can have a regular backup of volume with a retention period as well. Actual results: - VolumeSnapshot creation is a manual process from UI> Expected results: - Need automation of Volume Snapshot. Additional info:
Moving to volume replicator.
Not sure this can be done at the volume-replication-operator as this is specific to Replication. Maybe we need a new operator to provide this functionality?
What the customer is asking for is available today as an upstream operator: SnapScheduler Docs: https://backube.github.io/snapscheduler/ Repo: https://github.com/backube/snapscheduler It is available as a Community Operator in OpenShift's OperatorHub or as a Helm chart on ArtifactHub.
Moving this to the distribution component for tracking the addition of SnapScheduler to the ODF product. Tasks and progress can be followed through https://issues.redhat.com/browse/RHSTOR-2042 .
It seems the attached customer case is closed. There is no need to keep this BZ open for informing the customer anymore.