From 6fd0e19ef738599987b58cc9d801097f872fd541 Mon Sep 17 00:00:00 2001
From: Niels de Vos <ndevos@redhat.com>
Date: Wed, 29 Jun 2022 09:37:50 +0200
Subject: [PATCH] e2e: use `exclusive-lock` together with `lock_on_read`

When using `lock_on_read`, the RBD image needs to have the
`exclusive-lock` feature enabled too.

Fixes: #3221
Signed-off-by: Niels de Vos <ndevos@redhat.com>
(cherry picked from commit 2df55a55a3f276ffeaac3dc36450702ce47f60f8)
---
 e2e/rbd.go | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/e2e/rbd.go b/e2e/rbd.go
index 9ca638db2..f0f86a246 100644
--- a/e2e/rbd.go
+++ b/e2e/rbd.go
@@ -3266,8 +3266,9 @@ var _ = Describe("RBD", func() {
 					e2elog.Failf("failed to delete storageclass: %v", err)
 				}
 				err = createRBDStorageClass(f.ClientSet, f, defaultSCName, nil, map[string]string{
-					"mapOptions":   "lock_on_read,queue_depth=1024",
-					"unmapOptions": "force",
+					"imageFeatures": "exclusive-lock",
+					"mapOptions":    "lock_on_read,queue_depth=1024",
+					"unmapOptions":  "force",
 				}, deletePolicy)
 				if err != nil {
 					e2elog.Failf("failed to create storageclass: %v", err)