@@ -165,7 +165,8 @@ Test Encrypted Volume Snapshot Clone
165165 And Wait for volume 1 detached
166166
167167 # Attach cloned volume to new deployment with crypto SC (to trigger luksOpen)
168- And Create deployment 1 with volume 1 sc_name=longhorn-crypto node_stage_secret_name=longhorn-crypto
168+ And Create deployment 1 with volume 1 sc_name=longhorn-crypto node_stage_secret_name=longhorn-crypto node_publish_secret_name=longhorn-crypto
169+
169170 And Wait for volume of deployment 1 healthy
170171
171172 # Verify cloned volume size and data integrity
@@ -309,9 +310,6 @@ Test Encrypted Volume Backup Restore To Encrypted Volume
309310 ... - Restored volumes' replica backend file is exactly 100 Mi + 16 Mi.
310311 ... - The 10 Mi payload checksum matches the original.
311312 ... - Issue: https://github.com/longhorn/longhorn/issues/9205
312- IF '${DATA_ENGINE } ' == 'v2'
313- Skip v2 data engine does not support encrypted volume restore with encrypted=True (https://github.com/longhorn/longhorn/issues/13163)
314- END
315313 Given Create crypto secret
316314 And Create storageclass longhorn-crypto with encrypted=true dataEngine=${DATA_ENGINE }
317315 When Create persistentvolumeclaim 0 volume_type=RWO sc_name=longhorn-crypto storage_size=100Mi
@@ -339,8 +337,10 @@ Test Encrypted Volume Backup Restore To Encrypted Volume
339337 And Wait for volume 3 detached
340338 # Mount the restored volumes via deployments so that CSI opens the LUKS container.
341339 # Must use longhorn-crypto SC (with node-stage-secret-ref) so luksOpen is triggered.
342- And Create deployment 2 with volume 2 sc_name=longhorn-crypto node_stage_secret_name=longhorn-crypto
343- And Create deployment 3 with volume 3 sc_name=longhorn-crypto node_stage_secret_name=longhorn-crypto
340+ And Create deployment 2 with volume 2 sc_name=longhorn-crypto node_stage_secret_name=longhorn-crypto node_publish_secret_name=longhorn-crypto
341+
342+ And Create deployment 3 with volume 3 sc_name=longhorn-crypto node_stage_secret_name=longhorn-crypto node_publish_secret_name=longhorn-crypto
343+
344344 And Wait for volume of deployment 2 healthy
345345 And Wait for volume of deployment 3 healthy
346346 Then Assert disk size in instance manager pod for deployment 2 is 100Mi
@@ -791,7 +791,8 @@ Test Encrypted Volume Upgrade
791791 # Deployment 7: Restore from Backup 0 (RWO Filesystem)
792792 When Create volume 7 from backup 0 of deployment 0 volume size=100Mi encrypted=True dataEngine=${DATA_ENGINE }
793793 Then Wait for volume 7 detached
794- And Create deployment 7 with volume 7 sc_name=longhorn-crypto-stable node_stage_secret_name=longhorn-crypto
794+ And Create deployment 7 with volume 7 sc_name=longhorn-crypto-stable node_stage_secret_name=longhorn-crypto node_publish_secret_name=longhorn-crypto
795+
795796 And Wait for volume of deployment 7 healthy
796797 Then Assert disk size in instance manager pod for deployment 7 is 100Mi
797798 And Assert replica file size of deployment 7 is 116Mi
@@ -800,7 +801,8 @@ Test Encrypted Volume Upgrade
800801 # Deployment 8: Restore from Backup 1 (RWX Filesystem)
801802 When Create volume 8 from backup 1 of deployment 1 volume size=100Mi encrypted=True dataEngine=${DATA_ENGINE }
802803 Then Wait for volume 8 detached
803- And Create deployment 8 with volume 8 sc_name=longhorn-crypto-stable node_stage_secret_name=longhorn-crypto
804+ And Create deployment 8 with volume 8 sc_name=longhorn-crypto-stable node_stage_secret_name=longhorn-crypto node_publish_secret_name=longhorn-crypto
805+
804806 And Wait for volume of deployment 8 healthy
805807 Then Assert disk size in instance manager pod for deployment 8 is 100Mi
806808 And Assert replica file size of deployment 8 is 116Mi
0 commit comments