Several tests require CreateVolume capability

[joejulian]

I'm writing a CSI driver that does not have the CreateVolume capability. This test fails because it tries to CreateVolume before testing anything.

  [FAILED] in [It] - /home/jjulian/dev/go/src/github.com/kubernetes-csi/csi-test/pkg/sanity/controller.go:761 @ 11/01/24 16:39:00.443
  << Timeline

  [FAILED] volume create failed
  Unexpected error:
      <*status.Error | 0xc0005a00e8>: 
      rpc error: code = Unimplemented desc = CreateVolume is not implemented
      {
          s: {
              s: {
                  state: {
                      NoUnkeyedLiterals: {},
                      DoNotCompare: [],
                      DoNotCopy: [],
                      atomicMessageInfo: nil,
                  },
                  sizeCache: 0,
                  unknownFields: nil,
                  Code: 12,
                  Message: "CreateVolume is not implemented",
                  Details: nil,
              },
          },
      }
  occurred
  In [It] at: /home/jjulian/dev/go/src/github.com/kubernetes-csi/csi-test/pkg/sanity/controller.go:761 @ 11/01/24 16:39:00.443

The list is at least:
"should fail when no volume capabilities are provided",
"should return appropriate values",
"should fail when the node does not exist",
"should remove target path",
"should fail when no volume capability is provided",
"should be idempotent",
"should work",

There may be more, but I also have to skip all the "volume does not exist" because the volume may always exist in this driver, so I might not have a complete set.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale