You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Anything else you would like to add:
The test must achieve the below functionality
Scenario Outline: Create a clone from a
Given a storage class is created without any fstype as Raw block volume does not have any fstype
And a pvc with volumeMode as Bolck is created referencing this storage class
And a deployment is created using the same pvc
And a snapshot is be created for the corresponding
When the clone create command is run for this snapshot and a deployment is created to use this clone
Then the clone must be created from the snapshot and the created deployment must use the cloned volume
Examples:
| source |
| snapshot |
| volume |
Environment:
LocalPV-ZFS version
Kubernetes version (use kubectl version):
Kubernetes installer & version:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
The text was updated successfully, but these errors were encountered:
Describe the problem/challenge you have
The test to create the clone from snapshot is already present, on the very same line add code to test the clone from volume.
Refer https://github.com/openebs/zfs-localpv/blob/develop/docs/clone.md#create-clone-from-volume
Anything else you would like to add:
The test must achieve the below functionality
Scenario Outline: Create a clone from a
Given a storage class is created without any fstype as Raw block volume does not have any fstype
And a pvc with volumeMode as Bolck is created referencing this storage class
And a deployment is created using the same pvc
And a snapshot is be created for the corresponding
When the clone create command is run for this snapshot and a deployment is created to use this clone
Then the clone must be created from the snapshot and the created deployment must use the cloned volume
Examples:
| source |
| snapshot |
| volume |
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: