Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: add bdd for automated upgrade #636

Merged
merged 1 commit into from
Feb 18, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions tests/bdd/zfs.feature
Original file line number Diff line number Diff line change
Expand Up @@ -253,3 +253,26 @@ Feature: Validate volume provisioning for fsType zfs, ext4, xfs, btrfs
| ext4 |
| xfs |
| btrfs |

Scenario Outline: Main features should work after upgrade
Given The latest stable version of OpenEBS Local PV ZFS is installed in the cluster
And a storage class is created with fsType as <fsType> and thinprovision as <thinprovision> and allowExpansion as true
And pvc is created referencing this storage class
And a deployment is created using the same pvc
And a volume snapshot is created referencing this storage class
When the OpenEBS Local PV ZFS installed in the cluster is upgraded to target prerelease or develop version
And the pvc capacity is updated to a greater size
Then the pvc resize should work correctly and the filesystem should be updated eventually
When a restore is created from the snapshot
Then the restore should be created successfully and should be consumable by a workload
When a clone is created from the pvc
Then the clone should be created successfully and should be consumable by a workload
And the workloads should keep running until completion
Examples:
| fsType | thinprovision |
| zfs | no |
| xfs | no |
| zfs | yes |
| xfs | yes |
| zfs | |
| xfs | |
Loading