csi: aws-efs plugin failing with "Volume capability not supported"

[tgross]

In our e2e test for aws-efs (as of #7356's PR), allocations that claim the volume are failing during the pre-run hook with the following task events:

Recent Events:
Time                       Type           Description
2020-03-16T14:48:56-04:00  Setup Failure  failed to setup alloc: pre-run hook "csi_hook" failed: rpc error: code = InvalidArgument desc = Volume capability not supported
2020-03-16T14:48:56-04:00  Received       Task received by client

The volume mount we're using for the read-only use case is as follows. This sort of thing seems to work fine for the EBS plugin so it may be a matter of passing the right flags for plugin registration or volume registration. I want to circle back to this once #7306 and #7338 are done which will make it easier to test correctly.

      volume_mount {
        volume      = "test"
        destination = "${NOMAD_ALLOC_DIR}/test"
        read_only   = true
      }

[tgross]

This turned out to be simple... the EFS plugin doesn't support single-writer/multi-reader so I need to update the volume spec. (This probably should have been obvious given there's no controller.)

[tgross]

Closed by #7387

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.