Browse Source

Manila: Fix share_type in glusterfs (NFS) CI

During glusterfs (NFS) CI run, the extra spec "snapshot_support" used
for the default share-type is set to "True" even though the CI tests
the glusterfs backend with directory based share layout scheme that
does not support snapshot. So set the extra_spec to False which would
allow the Manila scheduler to pick up the glusterfs backend as a valid
host.

Change-Id: I7357417774cd16a2c114abd48a7bdb65a9eefc51
Closes-Bug: #1498399
Ramana Raja 3 years ago
parent
commit
2bd73dd2b6
1 changed files with 9 additions and 0 deletions
  1. 9
    0
      manila/pre_test_hook.sh

+ 9
- 0
manila/pre_test_hook.sh View File

@@ -29,6 +29,15 @@ else
29 29
     echo "MANILA_MULTI_BACKEND=False" >> $localrc_path
30 30
 fi
31 31
 
32
+# If the job tests glusterfs (NFS) driver, then create default share_type with
33
+# extra_spec snapshot_support as False. Becasuse the job that tests the
34
+# glusterfs (NFS) driver tests the directory based layout that doesn't support
35
+# snapshots. The job that tests glusterfs (NFS) driver has a name that
36
+# ends with "glusterfs".
37
+if [[ $JOB_NAME =~ manila-tempest-dsvm-glusterfs$ ]]; then
38
+    echo "MANILA_DEFAULT_SHARE_TYPE_EXTRA_SPECS='snapshot_support=False'" >> $localrc_path
39
+fi
40
+
32 41
 # Enabling isolated metadata in Neutron is required because
33 42
 # Tempest creates isolated networks and created vm's in scenario tests don't
34 43
 # have access to Nova Metadata service. This leads to unavailability of

Loading…
Cancel
Save