csi: allow more than 1 writer claim for multi-writer mode

Fixes a bug where CSI volumes with the `MULTI_NODE_MULTI_WRITER` access mode
were using the same logic as `MULTI_NODE_SINGLE_WRITER` to determine whether
the volume had writer claims available for scheduling.

nomad/structs/csi.go

@@ -384,8 +384,13 @@ func (v *CSIVolume) WriteSchedulable() bool {
 // WriteFreeClaims determines if there are any free write claims available
 func (v *CSIVolume) WriteFreeClaims() bool {
 	switch v.AccessMode {
-	case CSIVolumeAccessModeSingleNodeWriter, CSIVolumeAccessModeMultiNodeSingleWriter, CSIVolumeAccessModeMultiNodeMultiWriter:
+	case CSIVolumeAccessModeSingleNodeWriter, CSIVolumeAccessModeMultiNodeSingleWriter:
 		return len(v.WriteAllocs) == 0
+	case CSIVolumeAccessModeMultiNodeMultiWriter:
+		// the CSI spec doesn't allow for setting a max number of writers.
+		// we track node resource exhaustion through v.ResourceExhausted
+		// which is checked in WriteSchedulable
+		return true
 	default:
 		return false
 	}

nomad/structs/csi_test.go

@@ -36,6 +36,11 @@ func TestCSIVolumeClaim(t *testing.T) {
 	vol.ClaimRelease(claim)
 	require.True(t, vol.ReadSchedulable())
 	require.True(t, vol.WriteFreeClaims())
+
+	vol.AccessMode = CSIVolumeAccessModeMultiNodeMultiWriter
+	require.NoError(t, vol.ClaimWrite(claim, alloc))
+	require.NoError(t, vol.ClaimWrite(claim, alloc))
+	require.True(t, vol.WriteFreeClaims())
 }
 
 func TestCSIPluginJobs(t *testing.T) {